Everyshore Intelligence Network

Adeel Double-Strike: Thorax Podded in Coordinated Garmur/Vexor Ambush

Date: 2025-10-20
Analyst: [Your Analyst ID]
System: Adeel (Everyshore)
Incident Time (UTC): 2025-10-19 ~22:30

Executive summary

• A single, highly effective coordinated ambush occurred in Adeel on 2025-10-19 at ~22:30 UTC.
• Attackers (Cadhla Dioltas in a Garmur and Captian Realm in a Vexor) executed a two-stage elimination: ship kill (Thorax) followed immediately by a pod kill.
• Current system threat level: 3.5/5 — Moderate to High Danger. The event indicates active, professional hunters operating in the system during weekend peak hours.

What happened (concise timeline)

• A solo Thorax was engaged at ~22:30 UTC.
• Garmur (high mobility frigate) provided initial engagement/control (tackle/utility).
• Vexor (cruiser) applied primary DPS to rapidly kill the Thorax.
• Attackers followed up to successfully destroy the capsule (pod), indicating a focused pilot-targeting approach rather than merely seeking a ship kill.

Threat profile

• Primary actors observed: Cadhla Dioltas (Garmur) & Captian Realm (Vexor). No alliance affiliation established from available data.
• Tactics: classic frigate-tackle + cruiser-DPS pairing. Fast application of tackle allowed the cruiser to land sustained damage; attackers committed to a pod kill.
• Temporal pattern: Sunday evening peak (22:30 UTC). Hunters may exploit higher player traffic windows.

Immediate advisory for capsuleers operating in Adeel (actionable, data-rooted)

1. Avoid solo cruiser transit during peak weekend/evening hours (UTC evenings, e.g., Sundays ~22:30 UTC). The observed threat specifically targeted a solo cruiser and its pilot.
2. Treat Adeel as actively hunted while transiting. Expect coordinated two-ship tactics (tackle frigate + DPS cruiser). Assume podging/podding is an objective, not just shipkill.
3. Prefer group transits or at least two-ship pairs. A single tackle frig can neutralize a solo cruiser long enough for a cruiser to apply lethal DPS; buddies increase survival and counter-tackle options.
4. Use scouts and cloaky/transit counters where available. Cloaky frigates or an off-grid scout reduce chances of surprised approach and allow earlier detection of hunter signatures.
5. If you must run solo: maximize chances to escape. Travel in hulls that align quickly or can kite; pre-align to a safe, maintain awareness (scan/d-scan and speed management), and keep an escape plan (warp-out vectors, safes). Consider defensive options that increase time-to-kill (propulsion modules, range control, or warp-core stabilizer choices as tradeoffs).
6. Assume capsule vulnerability. If engaged and survival of the pod is a priority, factor that into your engagement decision-making (avoid prolonged scrambles/close-range fights when pod loss is unacceptable).
7. Log activity windows and reroute when possible. If you see repeated activity at the same time on subsequent weekends, treat those windows as high-risk.

Operational note for local movement planning

• The observed duo favors quick, decisive engagements; they are effective against typical solo cruiser fits. Transit plans should either avoid peak hours or add escorts with tackle denial and remote support. Lowsec transit always carries risk; this event demonstrates active, skilled hunters operating on weekend evenings in Everyshore.

EIN assessment

• Single-event data but high coordination and pod kill elevates systemic risk in Adeel during identified time windows. Continued vigilance recommended until repeat pattern is disproven by additional data.

End of advisory — Everyshore Intel Network (EIN)