Combat Record For Leolas
Favourite prey Capsule Favourite ship No recent Possible loadout Unknown Pods destroyed 4 Pod kill rate 6.35% First seen 2008.07.20 Estimated skill points 128,067,307 Average time most active 0:00 Region most active UnknownEstimated contribution to corporation 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 43.29 Kills 63 Losses 44 ISK Lost 4.31B ISK Destroyed 7.91B Damage Inflicted 674K Damage Taken 1M Pods Lost 2 Pods Taken 4
|Leolas 4.36||SuiMe So||Seyllin 0.4||1 Loss|
|Leolas 8||Regan Johnson||FD53-H 0.0||1 Loss|
|Leolas 16.04||Owen Drakkar||Heild 0.3||1 Loss|
|Gyokerke 20||Leolas||Mormelot 0.2||1 Kill|
|Leolas 8||kaldarinka||Decon 0.4||2 Loss|
|Leolas 9.22||Tjakkurinn||Basgerin 0.4||2 Loss|
|Sizemore Gnaaa 20||Leolas||Decon 0.4||1 Kill|
|Leolas 25||Sizemore Gnaaa||Decon 0.4||1 Loss|
|Leolas 20||The Lordship||Dodixie 0.9||1 Loss|
|badluk iffucrossme 7.45||Eardrick||Alachene 0.3||2 Kill|
|Gyokerke 20||Leolas||Mormelot 0.2||1|
|Sizemore Gnaaa 20||Leolas||Decon 0.4||1|
|badluk iffucrossme 7.45||Eardrick||Alachene 0.3||2|
|XkalistiX 4.62||JerichoSteele||Auvergne 0.9||4|
|The Lordship 5.06||Leolas||Auvergne 0.9||5|
|iNsAn3 2.76||Eardrick||Auvergne 0.9||3|
|The Lordship 7.44||Leolas||Botane 0.9||3|
|Spaceman Keith 5.4||Habidakus||Sharuveil 0.4||3|
|Skuller 12.5||Leolas||Alillere 0.8||1|
|Melkhaz 10||Cyric Lamphada||Hirri 0.3||2|
|Leolas 4.36||SuiMe So||Seyllin 0.4||1|
|Leolas 8||Regan Johnson||FD53-H 0.0||1|
|Leolas 16.04||Owen Drakkar||Heild 0.3||1|
|Leolas 8||kaldarinka||Decon 0.4||2|
|Leolas 9.22||Tjakkurinn||Basgerin 0.4||2|
|Leolas 25||Sizemore Gnaaa||Decon 0.4||1|
|Leolas 20||The Lordship||Dodixie 0.9||1|
|Leolas 12||Anya Klibor||Dodixie 0.9||1|
|Leolas 11.58||The Lordship||Dodixie 0.9||2|
|Leolas 15||The Lordship||Oursulaert 0.9||1|
|Ship||Last used||Lost||Kills with||Success Ratio|
|Incursus||February 04, 2013, 09:10:00 pm||1||0||0:1|
|Velator||November 09, 2008, 04:01:00 pm||1||0||0:1|
|Vexor||January 29, 2013, 10:05:00 am||7||16||16:7|
|Thorax||February 25, 2013, 07:21:00 pm||2||10||5:1|
|Celestis||October 27, 2011, 12:55:00 pm||1||1||1:1|
|Megathron||October 29, 2011, 02:01:00 pm||5||11||11:5|
|Dominix||September 29, 2011, 05:26:00 pm||4||4||1:1|
|Capsule||October 26, 2011, 12:21:10 pm||2||0||0:1|
|Brutix||November 15, 2011, 12:29:00 am||6||6||1:1|
|Hyperion||November 14, 2011, 10:57:00 pm||9||13||13:9|
|Myrmidon||November 16, 2011, 07:03:00 pm||4||1||1:4|
|Algos||March 26, 2013, 12:25:00 am||2||0||0:1|
|Moros||November 24, 2008, 03:05:00 pm||0||1||1:0|
|Pilot||Last seen||Kills with|
|H-5GUI 0.0||October 10, 2009, 02:21:00 am||0||1|
|HED-GP 0.0||July 20, 2008, 01:04:00 am||0||1|
|Hagilur 0.4||August 24, 2009, 11:15:00 pm||1||2|
|Eszur 0.2||September 29, 2011, 01:16:00 am||1||1|
|Heild 0.3||February 04, 2013, 09:10:00 pm||0||1|
|EOA-ZC 0.0||August 09, 2009, 01:01:00 am||0||1|
|Decon 0.4||January 29, 2013, 10:05:00 am||10||3|
|Sharuveil 0.4||October 27, 2011, 09:08:00 pm||1||1|
|Auvergne 0.9||November 14, 2011, 03:03:00 pm||6||2|
|Dodixie 0.9||November 17, 2011, 10:07:00 am||5||5|
|Foves 0.6||October 29, 2011, 02:01:00 pm||0||1|
|Basgerin 0.4||January 28, 2013, 03:48:00 pm||5||2|
|Archee 0.4||September 29, 2011, 03:03:00 pm||1||1|
|Adrallezoen 0.5||August 22, 2011, 07:22:00 pm||0||1|
|Alillere 0.8||October 27, 2011, 12:55:00 pm||1||1|
|Mirilene 0.8||October 26, 2011, 12:21:10 pm||0||2|
|Caretyn 0.8||September 24, 2011, 06:24:00 pm||1||1|
|Mya 0.4||November 30, 2008, 05:16:00 pm||0||1|
|Ethernity 0.9||December 09, 2008, 02:03:00 am||0||1|
|Elarel 0.4||August 21, 2011, 11:50:00 am||0||2|
|Y9G-KS 0.0||August 17, 2009, 02:12:00 am||1||1|
|Ostingele 0.2||October 11, 2011, 11:14:00 pm||3||1|
|XT-R36 0.0||August 14, 2009, 01:08:10 am||0||1|
|QXW-PV 0.0||August 14, 2009, 01:05:00 am||0||1|
|FD53-H 0.0||February 25, 2013, 07:21:00 pm||0||1|
|Oursulaert 0.9||November 13, 2011, 11:54:00 pm||0||1|
|Heydieles 0.3||October 11, 2011, 02:44:00 am||0||1|
|Old Man Star 0.3||June 20, 2011, 08:33:00 am||0||1|
|Seyllin 0.4||March 26, 2013, 12:25:00 am||3||2|
|Masalle 0.8||November 10, 2008, 03:48:00 pm||5||3|
|TFA0-U 0.0||August 13, 2009, 11:38:00 pm||1||0|
|Botane 0.9||November 14, 2011, 02:51:00 pm||1||0|
|Fricoure 0.8||September 25, 2011, 08:38:10 pm||4||0|
|Alachene 0.3||November 16, 2011, 07:03:00 pm||2||0|
|Groothese 0.3||November 27, 2008, 04:22:00 pm||1||0|
|Mormelot 0.2||January 31, 2013, 07:03:00 pm||1||0|
|Hebisa 0.9||July 07, 2011, 11:45:00 am||1||0|
|Alsavoinon 0.3||August 13, 2009, 01:15:00 am||1||0|
|DY-F70 0.0||August 14, 2009, 12:49:00 am||1||0|
|F7C-H0 0.0||August 13, 2009, 12:59:00 am||2||0|
|Adirain 0.4||June 24, 2009, 08:55:00 am||1||0|
|Hirri 0.3||October 11, 2011, 01:58:00 am||2||0|
|J121323 0.0||June 28, 2009, 10:40:00 am||1||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.