5.02
Dyantar
Dec 18, 2018
Jan 18, 2010(16y)
Jan 18, 2027(222d)
Combat
Kills2
Losses18
Efficiency10%
ISK
Destroyed338.50m
Lost6.70b
ISK Eff.5%
Solo
Solo Kills1
Solo Ratio50%
Final Blows1
Points2
Other
NPC Losses3
NPC Loss Ratio17%
Avg Kills/Day0.00
ActivityInactive
Caldari
Deteis
5.02
Dyantar
Last Active
Dec 18, 2018
Birthday
Jan 18, 2010 (16 years old)
Next Birthday
Jan 18, 2027 (222 days)
Combat
Kills2
Losses18
Efficiency10%
Danger Ratio83%
ISK
Destroyed338.50m
Lost6.70b
ISK Efficiency5%
Balance-6365742649
Solo
Solo Kills1
Solo Ratio50%
Final Blows1
Points2
Other
NPC Losses3
NPC Loss Ratio17%
Avg Kills/Day0.00
ActivityInactive
No data available
Bio
Old School Corner is Relaxed and Polite English Channel for Mature Audience. Please Avoid Drama, Religion and Politics Topics. Talking is not required. This channel is here to stay.
No Corporate Recruitment or Selling Anything.
۞ ΞνΞ ΘΠLІΠΞ ۞
Desinformation is the root of all evil.
EVE UNIVERSITY
CONCORD ACTS IF:
Aggressing a player who is not a legal target in high-secRemote repairing NPC ShipsActivating any Remote Assistance module on a player with the Criminal flag. This includes ECCM, tracking enhancers, and remote repair modules. Attacking CONCORD & Faction Police vessels, as well as some NPCs
Having a criminal flag and jumping into High Security Space. Shooting another player's loot (yellow wreck) while in high sec - See the Wreck Ownership support article for details. Shooting structures (Upwell Structures, Starbases, etc) unless engaged in a war with the structure owner.
Security Status: Response Time:
0.5: Roughly 19 seconds (up to 32)
0.6: Roughly 14 seconds (up to 27)
0.7: Roughly 10 seconds (up to 22)
0.8: Roughly 7 seconds (up to 17)
0.9 and 1.0: Roughly 6 seconds (up to 12)
When CONCORD is already on grid, the response time is severely reduced. The response time appears to drop between 2 seconds in 1.0 security to about 8 seconds in 0.6 and 9 seconds in 0.5.
When CONCORD has already spawned elsewhere in the system but is not yet on grid, the response time is significantly increased. In this case, it will take about 19 seconds for them to arrive and start firing in a 0.6 system, and 24 seconds in a 0.5 system.
If CONCORD has already spawned in the system and is not on grid, it's possible for a Minmatar Thrasher to do 3,000 EHP damage in a 0.6 system.
All methods of delaying CONCORD's response are considered an exploit by CCP. However, the technique of "pulling", which is the act of moving CONCORD from one location to another, is not considered a delay of CONCORD.
No Corporate Recruitment or Selling Anything.
۞ ΞνΞ ΘΠLІΠΞ ۞
Desinformation is the root of all evil.
EVE UNIVERSITY
CONCORD ACTS IF:
Aggressing a player who is not a legal target in high-secRemote repairing NPC ShipsActivating any Remote Assistance module on a player with the Criminal flag. This includes ECCM, tracking enhancers, and remote repair modules. Attacking CONCORD & Faction Police vessels, as well as some NPCs
Having a criminal flag and jumping into High Security Space. Shooting another player's loot (yellow wreck) while in high sec - See the Wreck Ownership support article for details. Shooting structures (Upwell Structures, Starbases, etc) unless engaged in a war with the structure owner.
Security Status: Response Time:
0.5: Roughly 19 seconds (up to 32)
0.6: Roughly 14 seconds (up to 27)
0.7: Roughly 10 seconds (up to 22)
0.8: Roughly 7 seconds (up to 17)
0.9 and 1.0: Roughly 6 seconds (up to 12)
When CONCORD is already on grid, the response time is severely reduced. The response time appears to drop between 2 seconds in 1.0 security to about 8 seconds in 0.6 and 9 seconds in 0.5.
When CONCORD has already spawned elsewhere in the system but is not yet on grid, the response time is significantly increased. In this case, it will take about 19 seconds for them to arrive and start firing in a 0.6 system, and 24 seconds in a 0.5 system.
If CONCORD has already spawned in the system and is not on grid, it's possible for a Minmatar Thrasher to do 3,000 EHP damage in a 0.6 system.
All methods of delaying CONCORD's response are considered an exploit by CCP. However, the technique of "pulling", which is the act of moving CONCORD from one location to another, is not considered a delay of CONCORD.
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: -