Last ActiveMar 26, 2013
BirthdayMar 14, 2013 (13 years old)
Next BirthdayMar 14, 2027 (148 days)
Combat
Kills0
Losses2
Efficiency0%
Danger Ratio100%
ISK
Destroyed0
Lost5.34m
ISK Efficiency0%
Balance-5335148
Solo
Solo Kills0
Solo Ratio0%
Final Blows0
Combat Points0
Other
NPC Losses0
NPC Loss Ratio0%
Avg Kills/Day0.00
ActivityInactive
Loading valuable kills…
Ship ClassesLoading…
Bio
The CONCORD Response Time depends basically on the displayed security status (not the real sec) of the system and whether they are already on grid or not. 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.
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 and to about 9 seconds in 0.5 and 0.6.
A thrasher has a cycle time of 7 seconds, and does about 1000dmg per volley. So for less than a 1mil you can be suicide ganked for 1000-2000 EHP in a 0.5 security system. The same setup in 0.9 would only do 1000 EHP of damage.
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 and to about 9 seconds in 0.5 and 0.6.
A thrasher has a cycle time of 7 seconds, and does about 1000dmg per volley. So for less than a 1mil you can be suicide ganked for 1000-2000 EHP in a 0.5 security system. The same setup in 0.9 would only do 1000 EHP of damage.
Dashboard
Stats
No activity in the selected period
Loading intel…