ROUTE EVIDENCE
Inspect the gates ahead.
Reported losses along your route. Both sides of every jump.
starts with evidence.
Demonstration. Real map, synthetic loss reports. These results are not current travel intelligence.
Plot your journey
No account neededYOUR JOURNEY
No reported kills doesn't mean the route is safe.
Your next route, in focus.
Choose two systems to see the gates you will use
and the losses reported near each end.
READ THE SIGNAL
Evidence, with its limits.
Reports describe losses that have already happened. A newly formed camp may have no reported victims.
What do the labels mean?
Gate camp: kills near this gate in the past hour — at least one ship or pod was reported destroyed within 100 km of this gate in the last 60 minutes, with at least one player among the attackers. One kill is enough. Each kill counts for exactly 60 minutes after it happened, then drops off on its own, even without a refresh.
No current losses reported — no such kill was reported near this gate in the last 60 minutes. That is not a guarantee the gate is clear.
No current losses in available data — the same, but collection was incomplete (see the notice above the route), so a kill may be missing.
Out of date — refresh to check this gate — the result is more than two minutes old or the last refresh failed. Kills already shown still count down and drop off on time.
Warning timing uncertain — refresh — a kill is right at its 60-minute limit; refresh for a clear answer.
Data incomplete — collection coverage, freshness or classification is not good enough to treat a quiet gate as quiet. Reported kills are still shown. History counts use the selected 1, 2 or 6 hours and never extend the 60-minute gate camp label.
Where does the information come from?
Public kill reports from zKillboard, through its R2Z2 feed. Local routing uses CCP's Static Data Export. Gatecheck makes no direct ESI requests during normal operation.
Losses are matched to the nearest gate within 100 km using the victim's position. Public reports may arrive late or never be published.
This view requires a valid player attacker. Reports with only NPC attackers, or structures with no player attacker, are excluded. Invalid attacker data instead makes coverage incomplete. Evidence ages describe the dated server observation. Current warnings expire independently even without refresh; after two minutes the collection snapshot is also marked stale. Accepted future-dated reports are stored but cannot contribute before their destruction time. Receipt-clamped times are diagnostic only. Reported smartbomb participation and final-blow weapons are descriptive; missing weapon data never establishes absence of smartbombs.
Map information will appear when the local dataset is available.
What is outside the coverage?
No wormhole connections, filaments, jump drives, Ansiblex, shipcasters, Pochven, Jove regions, or Zarzakh routing. Temporary access restrictions and events are not tracked. Routes may differ from the in-game planner.
This page needs no character login and stores no journey history in your browser. Route requests are sent to this server; infrastructure logging depends on the operator's configuration.