Combat Record For silvarizza
Favourite prey Capsule Favourite ship No recent Possible loadout Unknown Pods destroyed 113 Pod kill rate 27.76% First seen 2011.12.05 Estimated skill points 63,849,880 Average time most active 0:00 Region most active UnknownEstimated contribution to corporation killsEstimated contribution to alliance kills
Past 7 Days
Past 7 Days
Points 0.00 Kills 0 Losses 0 ISK Lost 0 ISK Destroyed 0 Damage Inflicted 0 Damage Taken 0 Pods Lost 0 Pods Taken 0
Points 562.39 Kills 407 Losses 31 ISK Lost 1.59B ISK Destroyed 53.03B Damage Inflicted 38M Damage Taken 145K Pods Lost 5 Pods Taken 113
|White Sunji 0.21||Mike31x||7Q-8Z2 0.0||7 Kill|
|silvarizza 4.44||Artuard Envien||Aset 0.4||3 Loss|
|Mementis 181.82||silvarizza||J135809 0.0||2 Kill|
|Evil Broccoli 0.26||Lyra Apfelkuchen||J110316 0.0||4 Kill|
|Abubakar Arjar 0.2||Hisui Shikabane||J153106 0.0||5 Kill|
|Abubakar Arjar 3.22||dkuhf||J153106 0.0||5 Kill|
|Balairus 0.26||silvarizza||J133049 0.0||4 Kill|
|Daddywarcrimes1 2.11||Nuffie Zatoichi||J133049 0.0||2 Kill|
|Balairus 2.77||Belana Below||J133049 0.0||6 Kill|
|lordlucas75 0.73||silvarizza||J133049 0.0||1 Kill|
|White Sunji 0.21||Mike31x||7Q-8Z2 0.0||7|
|Mementis 181.82||silvarizza||J135809 0.0||2|
|Evil Broccoli 0.26||Lyra Apfelkuchen||J110316 0.0||4|
|Abubakar Arjar 0.2||Hisui Shikabane||J153106 0.0||5|
|Abubakar Arjar 3.22||dkuhf||J153106 0.0||5|
|Balairus 0.26||silvarizza||J133049 0.0||4|
|Balairus 2.77||Belana Below||J133049 0.0||6|
|Daddywarcrimes1 2.11||Nuffie Zatoichi||J133049 0.0||2|
|lordlucas75 0.73||silvarizza||J133049 0.0||1|
|lordlucas75 4.76||Nuffie Zatoichi||J133049 0.0||6|
|silvarizza 4.44||Artuard Envien||Aset 0.4||3|
|silvarizza 2.5||Araziah||Otou 0.3||1|
|silvarizza 0.96||Kodizzie||Madirmilire 0.6||3|
|silvarizza 5.16||Ere Colliseru||Luminaire 1.0||4|
|silvarizza 0.38||Panhead4411||Luminaire 1.0||6|
|silvarizza 5.26||DALERON RUFUS||J204221 0.0||1|
|silvarizza 5||Arrius Praetor||ZQ-Z3Y 0.0||1|
|silvarizza 1.16||Arrius Praetor||ZQ-Z3Y 0.0||12|
|silvarizza 0.24||bambidka||J154934 0.0||5|
|silvarizza 2.87||Pavka Sohaj||J154934 0.0||7|
|Ship||Last used||Lost||Kills with||Success Ratio|
|Incursus||June 13, 2014, 04:44:00 am||1||0||0:1|
|Imicus||May 11, 2013, 03:41:00 pm||1||0||0:1|
|Thorax||March 22, 2013, 10:48:00 am||1||23||23:1|
|Dominix||April 23, 2013, 06:12:00 am||1||1||1:1|
|Epithal||December 22, 2011, 02:02:00 am||1||0||0:1|
|Iteron Mark V||April 18, 2013, 10:18:00 pm||2||0||0:1|
|Capsule||March 22, 2013, 10:49:00 am||5||6||6:5|
|Talos||June 06, 2013, 10:45:00 am||1||88||88:1|
|Gallente Shuttle||April 29, 2012, 10:57:00 am||2||0||0:1|
|Minmatar Shuttle||January 09, 2012, 09:36:00 am||1||0||0:1|
|Ares||February 23, 2013, 06:14:00 am||6||33||11:2|
|Enyo||January 30, 2013, 01:15:00 pm||6||41||41:6|
|Viator||January 15, 2012, 08:24:00 am||1||0||0:1|
|Eris||March 06, 2013, 04:24:00 am||2||30||15:1|
|Velator||March 22, 2013, 05:55:00 am||0||3||1:0|
|Atron||March 22, 2013, 10:19:00 am||0||40||1:0|
|Vexor||January 16, 2013, 06:07:10 am||0||2||1:0|
|Celestis||April 24, 2012, 12:14:10 am||0||5||1:0|
|Megathron||March 27, 2013, 04:42:10 am||0||20||1:0|
|Taranis||March 08, 2012, 07:31:10 am||0||12||1:0|
|Deimos||April 18, 2013, 12:57:10 am||0||3||1:0|
|Brutix||June 20, 2014, 10:30:10 am||0||3||1:0|
|Vigilant||June 26, 2012, 12:13:00 pm||0||2||1:0|
|Heretic||June 13, 2013, 11:28:10 am||0||1||1:0|
|Myrmidon||January 26, 2013, 05:57:00 pm||0||1||1:0|
|Orca||January 10, 2013, 12:56:00 pm||0||10||1:0|
|Proteus||June 25, 2013, 11:15:00 pm||0||71||1:0|
|Pilot||Last seen||Kills with|
|P-N5N9 0.0||February 27, 2012, 03:02:10 pm||1||2|
|K212-A 0.0||April 29, 2012, 10:59:00 am||1||2|
|56D-TC 0.0||February 20, 2012, 11:33:10 am||0||2|
|8DL-CP 0.0||November 22, 2012, 12:37:00 am||2||2|
|8YC-AN 0.0||November 22, 2012, 03:22:00 pm||10||1|
|7Q-8Z2 0.0||June 20, 2014, 10:30:10 am||109||6|
|SUR-F7 0.0||November 22, 2012, 12:19:00 pm||6||1|
|ZQ-Z3Y 0.0||January 30, 2013, 01:15:10 pm||1||2|
|Aset 0.4||June 13, 2014, 04:44:00 am||0||1|
|AD-5B8 0.0||May 03, 2012, 01:11:00 pm||0||1|
|Rancer 0.4||January 09, 2012, 09:36:00 am||0||1|
|Otou 0.3||May 11, 2013, 03:41:00 pm||0||1|
|Madirmilire 0.6||April 18, 2013, 10:18:00 pm||0||1|
|KBP7-G 0.0||December 03, 2012, 01:48:00 pm||2||1|
|TN-T7T 0.0||November 13, 2012, 01:32:00 am||1||1|
|Luminaire 1.0||March 22, 2013, 11:32:00 am||6||2|
|J204221 0.0||February 23, 2013, 06:14:00 am||2||1|
|J154934 0.0||January 29, 2013, 08:46:00 am||12||2|
|J113727 0.0||December 28, 2012, 05:10:10 am||3||1|
|Astabih 0.4||April 23, 2012, 03:42:00 am||1||0|
|ARG-3R 0.0||March 29, 2012, 01:35:00 am||1||0|
|E02-IK 0.0||April 29, 2012, 02:36:00 am||1||0|
|VKU-BG 0.0||November 24, 2012, 04:06:00 am||56||0|
|Q2FL-T 0.0||November 12, 2012, 01:14:10 pm||2||0|
|CBL-XP 0.0||January 30, 2013, 12:39:00 pm||1||0|
|Pettinck 0.8||March 22, 2013, 09:35:10 am||42||0|
|Raravath 0.4||February 20, 2013, 12:38:00 pm||1||0|
|J143639 0.0||April 18, 2013, 12:57:10 am||2||0|
|J135809 0.0||June 25, 2013, 11:15:00 pm||1||0|
|J120928 0.0||January 12, 2013, 07:55:00 am||1||0|
|J110316 0.0||June 13, 2013, 11:28:10 am||50||0|
|J122246 0.0||September 27, 2012, 04:04:00 am||1||0|
|J132559 0.0||June 26, 2012, 07:16:00 am||1||0|
|J135910 0.0||March 19, 2013, 09:10:10 am||1||0|
|J145211 0.0||April 06, 2013, 07:24:10 am||2||0|
|J131034 0.0||June 06, 2013, 10:45:00 am||1||0|
|J215944 0.0||April 05, 2013, 12:09:00 am||1||0|
|J133049 0.0||June 10, 2013, 12:22:10 am||5||0|
|J121720 0.0||October 08, 2012, 12:18:00 pm||1||0|
|J170002 0.0||March 07, 2013, 07:26:00 am||1||0|
|J154642 0.0||April 23, 2012, 04:21:00 am||1||0|
|J105409 0.0||October 15, 2012, 10:56:00 am||1||0|
|J104643 0.0||January 25, 2013, 06:31:00 am||5||0|
|J212304 0.0||April 10, 2013, 04:56:00 am||9||0|
|J154634 0.0||October 15, 2012, 12:56:00 pm||1||0|
|J133121 0.0||January 19, 2013, 04:44:10 pm||2||0|
|J100150 0.0||October 08, 2012, 10:55:10 am||3||0|
|J104311 0.0||April 23, 2013, 06:12:00 am||1||0|
|J165020 0.0||June 04, 2013, 06:52:10 am||4||0|
|J155416 0.0||November 05, 2012, 02:55:00 pm||1||0|
|J144732 0.0||January 10, 2013, 12:56:00 pm||16||0|
|J151720 0.0||January 26, 2013, 07:43:10 am||4||0|
|J161815 0.0||March 19, 2013, 11:51:10 am||2||0|
|J130828 0.0||April 17, 2013, 04:08:10 am||2||0|
|J103104 0.0||April 05, 2013, 04:36:10 am||2||0|
|J215935 0.0||April 04, 2013, 02:30:10 am||2||0|
|J133957 0.0||January 09, 2013, 10:32:00 am||3||0|
|J124933 0.0||March 06, 2013, 04:24:00 am||1||0|
|J155200 0.0||April 17, 2013, 04:58:00 am||1||0|
|J154102 0.0||January 10, 2013, 12:11:10 pm||2||0|
|J144120 0.0||December 18, 2012, 09:35:00 am||2||0|
|J123352 0.0||January 09, 2013, 07:04:00 pm||1||0|
|J213429 0.0||June 26, 2012, 12:13:00 pm||1||0|
|J113133 0.0||April 05, 2013, 08:50:10 am||2||0|
|J205517 0.0||March 13, 2013, 04:04:00 am||4||0|
|J212203 0.0||March 29, 2012, 07:06:10 am||3||0|
|J153106 0.0||June 11, 2013, 07:18:10 am||2||0|
Welcome to the oldest and largest killboard for EVE Online! Our ongoing development and maintenance of the killboard is supported by our ETC sales. Buy yours at BattleClinic Deep Space Supply!
Short FAQ1. I get the Please enter your API key, this mail cannot be posted directly error!
If you get an error trying to manually post a killmail, please note: Super Capital ships, POS's, and kills that happened in FD-MLJ (system where PVP is allowed on the test server) require your full API. They cannot be manually posted. This is to improve killboard accuracy.
2. I'm on a killmail for a POS. Why can't I post it?
Your CEO or a director, the enemy CEO or one of their directors, the person who laid the final blow, or the victim must have their full API in the killboard, for a POS to post.
3. I can't post a killmail because it says item "unknown."
Check that the killmail is valid, generated from ingame and not copied from a 3rd party. It could be that CCP have released a patch and have not yet released a static data export to allow fan sites to recognize new items.
4. My ranking history shows a dot. Why doesn't it track my whole history?
The chart only tracks the movement of the top 10,000 entities in EVE. If you're not in the top 10,000, please return to the battlespace and win more fights.
5. Why do I have to register to view killmails?
This is necessary to deter hostile scraping, which consumes bandwidth that we have to pay for and (has) knocked the site offline. The good news is that it's easy to register for the site and we won't ever spam you or sell your email. We've been running for almost 10 years under this promise.
6. I have other concerns that are not addressed in this help tab. Where can I post them?
Here is the board you seek.
BattleClinic helps players Fight Smart®. The killboard's primary purpose is to help you learn more about your enemy. It also provides a combat history for your character(s). If you want more control over your stats and records, consider getting a Griefwatch board for yourself, your corp, or your alliance.
Fog of War
No killboard in existence, not even an "API-Only" killboard, is100% accurate. This is due to the nature of killmails and how they are distributed. BattleClinic (and most independent killboard operators, too) use our extensive experience with the game to make decisions about how we display stats and data, but we all are constrained by the limitations of the data CCP provides. Moreover, meta-gaming and in-game tricks by players contribute to some inaccurate data. We take steps (human and technology-based) and we cooperate with other player-run game sites to keep our data extremely accurate.
Improving Accuracy of Data
You can improve the accuracy of your statistics by entering your full api key. Don't worry, it's safe; your account, your isk, and your stuff cannot be accessed by anyone or any website by using your full api key. Don't believe the rumors and misinformation that exists out there: A full API key cannot be used to obtain control of your account.
We highly recommend that your corp CEO post their full API key (it's safe to do that here!) so that all of your corp's kills will show on the killboard.
Ranking and Points
BattleClinic uses a proprietary system to award points to kills (and to award negative points for losses). We do not disclose the formula, but we can tell you that skillful combat techniques are rewarded. In other words, you can't climb the ranks very quickly by sitting outside your POS and shooting Velators for a month.
Your ranking is based on your points compared to the points earned or lost by other players at a specific point in time. Due to the volume of killmails we process, we update standings weekly. Note that tens of thousands of other players are involved in combat as well as you; therefore somewhat significant swings in rankings can occur. For example, fleet fights can generate a thousand killmails or more. If several large fights occur within a short time period, they can statistically impact player rankings. In short, your ranking is not directly influence-able, since you're competing with tens of thousands of other players.
BattleClinic only tracks the ranking history of the top ten thousand pilots in EVE-Online. If you don't have a ranking history displayed, you're currently not in the top 10k.
ISK Values for Ships and Modules
We provide estimated values for the ships and modules that are destroyed in combat. These values are drawn from other community fansites who monitor the EVE Online markets and graciously share this information. BattleClinic has no control over these values.
In certain circumstances, BattleClinic makes some assumptions when assigning ISK values. For example, CCP does not differentiate BPOs from BPCs inside a killmail or via the API thread. Therefore, we display the ISK value for a BPO, even if the item destroyed was, in reality, a BPC. We revisit these assumptions from time to time and try to find ways to improve results.
Combat Record Tags
BattleClinic displays combat tags based on our analysis of your activity. These tags appear and disappear depending on your actions over time. These tags are not awards and are not permanent. They highlight recent noteworthy achievements.
Top 10k Pilot - Appears when your point total places you in the top 10,000 pilots in all of EVE-Online
Damage Dealer - Appears when your 7-day damage dealt to damage received ratio is significant.
Empire Dweller - Appears when your most recent final blows have occurred in Empire space (0.5 or above). Note that some pilots make references to "carebears" when discussing players who are based in Empire space.
LoSec Roamer - Appears when your most recent final blows have occurred in Low Security space (0.1 to 0.4). Roaming pirates are common in LoSec.
0.0 Pioneer - Appears when your most recent final blows have occurred in 0.0 space. Most Alliances are typically found in "nullsec" and most typically engage in taming (or contributing to) the lawless wilderness of 0.0.
Loss Mail Record Tags
These tags are not awards and are not permanent. They highlight recent noteworthy achievements.
Nemesis: Lights up on your loss record when the same pilot gets the final blow on you three or more times within 7 days.
100% Destruction: Lights up when all of your ship's modules are destroyed.
Empire Kill: Lights up when the kill occurs within Empire space.
Solo Kill: Lights up when the pilot who killed you did so without any assistance.
Removing Your Character from the Killboard
Occasionally BattleClinic receives requests to remove characters from the killboard, especially those with a losing record. Unfortunately this is an impossible task because one pilot's loss is another's kill. In addition, other killboards have feeds which could restore your character's appearance on BattleClinic. If you want a better showing on any killboard, achieve success in the battlespace.
Characters with Prior History
If you purchased your character from someone else, or you create a new character and discover that the name had been used previously, you may want the prior record removed. We understand: you'd like a 'clean slate' since it's your character now. Unfortunately this is not possible, because those previous kills and losses were legitimate, and are part of someone else's stats. There's no getting around the universal truth that all relationships come with prior baggage.