5.00
Spec 593357629
Sep 9, 2020
Jun 1, 2003(22y)
Jun 1, 2026(1d)
Combat
Kills947
Losses500
Efficiency65%
ISK
Destroyed676.97b
Lost32.46b
ISK Eff.95%
Solo
Solo Kills36
Solo Ratio4%
Final Blows125
Points947
Other
NPC Losses23
NPC Loss Ratio5%
Avg Kills/Day0.11
ActivityInactive
Gallente
Gallente
5.00
Spec 593357629
Last Active
Sep 9, 2020
Birthday
Jun 1, 2003 (22 years old)
Next Birthday
Jun 1, 2026 (1 days)
Combat
Kills947
Losses500
Efficiency65%
Danger Ratio95%
ISK
Destroyed676.97b
Lost32.46b
ISK Efficiency95%
Balance+644.52b
Solo
Solo Kills36
Solo Ratio4%
Final Blows125
Points947
Other
NPC Losses23
NPC Loss Ratio5%
Avg Kills/Day0.11
ActivityInactive
No data available
Bio
CONCORD Response Times
The CONCORD response time depends on the displayed security status (not the real sec) of the system and the status of CONCORD presence in the system. It's possible CONCORD still has to spawn in the system, has already spawned elsewhere in the system, or is present on grid.
It seems the lock time of the CONCORD ships does not depend on the signature radius of the offender's ship. The following table gives the time in seconds between the offending action and the first felt action of a CONCORD ship when CONCORD has just spawned in a system.
0.5: Roughly 19 seconds
0.6: Roughly 14 seconds
0.7 : Roughly 10 seconds
0.8 : Roughly 7 seconds
0.9 and 1.0: Roughly 6 seconds
When CONCORD is already on grid, the response time is severely reduced. There are no hard numbers on that yet but it looks like as if the response time drops to 2 seconds in 1.0 to about 8 seconds in 0.6 and 9 seconds in 0.5.
When CONCORD has already spawned elsewhere in the system but isn't on grid, the response time is significantly increased. In this case it will take about 22 seconds them to arrive and start firing in a 0.6 system.
A Thrasher has a cycle time of 7 seconds, and does about 1000 damage per volley. So for a ship that costs less than a 1 million ISK you can be suicide ganked for 1000-2000 EHP in a 0.5 security system where CONCORD still has to spawn. The same setup in 0.9 would only do 1000 EHP of damage.
If CONCORD has already spawned in the system and is not on grid, it's possible the Thrasher can do 3000 EHP damage in a 0.6 system.
[23:44:11] Vehlin > blue drink is 5 parts vodka 3 parts peach schnapps 2 parts blue curacao and 10 parts lemonade
The CONCORD response time depends on the displayed security status (not the real sec) of the system and the status of CONCORD presence in the system. It's possible CONCORD still has to spawn in the system, has already spawned elsewhere in the system, or is present on grid.
It seems the lock time of the CONCORD ships does not depend on the signature radius of the offender's ship. The following table gives the time in seconds between the offending action and the first felt action of a CONCORD ship when CONCORD has just spawned in a system.
0.5: Roughly 19 seconds
0.6: Roughly 14 seconds
0.7 : Roughly 10 seconds
0.8 : Roughly 7 seconds
0.9 and 1.0: Roughly 6 seconds
When CONCORD is already on grid, the response time is severely reduced. There are no hard numbers on that yet but it looks like as if the response time drops to 2 seconds in 1.0 to about 8 seconds in 0.6 and 9 seconds in 0.5.
When CONCORD has already spawned elsewhere in the system but isn't on grid, the response time is significantly increased. In this case it will take about 22 seconds them to arrive and start firing in a 0.6 system.
A Thrasher has a cycle time of 7 seconds, and does about 1000 damage per volley. So for a ship that costs less than a 1 million ISK you can be suicide ganked for 1000-2000 EHP in a 0.5 security system where CONCORD still has to spawn. The same setup in 0.9 would only do 1000 EHP of damage.
If CONCORD has already spawned in the system and is not on grid, it's possible the Thrasher can do 3000 EHP damage in a 0.6 system.
[23:44:11] Vehlin > blue drink is 5 parts vodka 3 parts peach schnapps 2 parts blue curacao and 10 parts lemonade
Dashboard
Stats
Kills0
Losses0
Efficiency0%
ISK Destroyed0
ISK Lost0
ISK Efficiency0%
Solo Kills0
Solo Losses0
NPC Losses0
Blob Factor0
Active TimezoneUSTZ
Final Blows0
Points0
Activity Heat Map (EVE Time)
00
0
01
0
02
0
03
0
04
0
05
0
06
0
07
0
08
0
09
0
10
0
11
0
12
0
13
0
14
0
15
0
16
0
17
0
18
0
19
0
20
0
21
0
22
0
23
0
Intel Profile
PlaystyleSolo (0 kills)
Avg Fleet: -
Groups Flown With
Top Fleet Partners
