Mya – 2025-11-12
Date range: 2025-11-05 to 2025-11-11 (analyst report)
Executive Summary
- System: Mya (Low‑Sec / contested)
- Risk posture: High to Extreme. Analyst data classifies unaligned/solo transit risk at real_thread 4.5 (Extreme) during weekday late‑afternoon (16:00–18:00 UTC). Roaming gangs keep risk elevated outside peak windows.
- Nature of conflict: Sustained, coordinated fleet warfare — large Loki/Tengu strategic cruiser formations vs. Mordu’s Legion Barghest battleship groups. Capital escalation (dreadnoughts, FAX) observed during major clashes.
- Short guidance: Non‑combat and lightly fitted ships should avoid Mya. Transits through the system should be scheduled outside the 16:00–18:00 UTC window where possible, and only attempted with appropriate fittings, scouts, or in strong, prepared fleets.
Observed Pattern / Timings
- Consistent peak activity: Weekday late New Eden afternoon (EVE prime time) — strongest spikes Thursday and Friday in this reporting period.
- High‑risk windows observed:
- Thursday 16:13–16:45 UTC — major Barghest vs Loki engagement with capital escalation.
- Friday 17:19–17:33 UTC — major peak, many strategic cruiser losses.
- Daily smaller spikes and roaming gangs outside prime time; isolated ganks recorded mornings and late evenings.
- Overnight and early‑morning hours are comparatively quieter but opportunistic cloaky and bomber activity was recorded (e.g., stealth bomber activity on Nov 9).
Primary Threat Actors (as reported)
- Group Alpha — Barghest‑centred force (Mordu’s Legion doctrine): Barghest missile battleships supported by Huginn (combat recon) and Claymore (command ships). Associated pilots included: Roset Tali, Fat Zero, Essew Kadoko, Winston 4Head, x1SHOTx3KILLSx.
- Group Beta — Strategic Cruiser force: Loki and Tengu heavy use, supported by recon and E‑War (Arazu, Rapier, Helios, Kitsune, Keres). Associated pilots included: Cynric Finn, Lareliel, Daverosh Saissore, Lieutenant commander, Olaf Ronuken.
- Unknown/independent elements: Dreadnought (Zirnitra) and capitals (Minokawa, Naglfar, Revelation NI) have appeared in escalations — presence of capitals indicates willingness to press engagements to high escalation levels.
Threat Levels by Ship Class (real_thread guidance)
- Capitals / FAX: 5.0 — Presence of capitals equates to guaranteed extreme danger; avoid if spotted.
- Strategic Cruisers (Loki/Tengu): 4.5 — Core offensive threat; cloaky/versatile and present in numbers.
- Barghest Battleships: 4.5 — Long‑range missile packs; mainline enemy doctrine.
- Recon / E‑War (Arazu, Huginn, Rapier, Kitsune, Keres): 4.0 — Actively hunted and used to fix/neutralize targets; vulnerable but highly consequential if present.
- CovOps / Stealth Bombers (Helios, Manticore, Purifier): 3.5 — Scouting, surprise strikes, specialty threat to logistics/scouts.
- Industrial / Harvesters (Retrievers, Nereus): 1.5–3.0 — High value targets for opportunists during low vigilance; avoid altogether during peak.
Actionable Advisory (for unaligned pilots and non‑combat transit)
- Avoid transiting Mya during 16:00–18:00 UTC (UTC) on weekdays if at all possible. Thursday and Friday showed the highest escalation frequency.
- Non‑combat ships (haulers, miners, industry, logistic/remote rep ships): do not enter Mya during peak hours. Consider alternate routes or ban routes that pass through Mya.
- If you must transit:
- Use fastest align/warp ships (interceptors or similarly fast hulls) and fit to minimize warp time; expect warp disruption from recon/E‑war.
- Cloak or stay docked in citadels if enemy fleets are present. Do not loiter in system.
- Avoid bridging or cyno‑jumping into the system when fleets are present — capital escalation has been recorded.
- Recon and scouts: extreme caution. Arazu/Huginn/others are routinely used to pin targets; expect counter‑recon and hunters.
- Fleet pilots: expect structured dogfights between Barghest formations and Loki/Tengu fleets. Capital support has been used; plan contingencies for heavy escalation (dreads / FAX).
Actionable Advisory (for combat/intervention forces)
- If planning operations, synchronize with the observed late‑afternoon activity window for maximum contact, but be prepared for capital escalations and strong E‑war.
- Prioritize counter‑E‑war modules, remote logistics, and cap management — both groups fielded heavy recon/E‑war and logistics support.
Final Notes
- Mya is an active, contested killzone — the analytic picture shows repeated, coordinated fleet engagements rather than random ganking. Unaligned pilots and non‑combat traffic are exposed to high risk, especially during weekday late afternoons (16:00–18:00 UTC UTC).
- All timings and threat characterizations above are derived from the analyst report covering 2025-11-05 to 2025-11-11.
EIN — Everyshore Intel Network