Gallente
Gallente
5.00
Spec 593357629
Last Active:
20 days ago
Birthday:
Jun 1, 2003 (22 years old)
Next Birthday:
Jun 1, 2026 (263 days remaining)
Combat Metrics
Kills
946
Losses
496
Efficiency
65.6%
Danger Ratio
57.9%
ISK Metrics
ISK Killed
678.22B ISK
ISK Lost
32.67B ISK
ISK Efficiency
95.4%
ISK Balance
645.56B ISK
Solo Activity
Solo Kills
36
Solo Losses
183
Solo Kill Ratio
3.8%
Solo Efficiency
16.4%
Other Metrics
NPC Losses
23
NPC Loss Ratio
4.6
Avg. Kills/Day
0.1
Activity
Very High
Character Biography
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