Mya – 2025-10-28
Date: 2025-10-27
Region: Everyshore (Low-Sec)
Threat Level: 4.5 — Critical Engagement Zone
Executive Summary
Mya has been the scene of two large, coordinated fleet operations in the past week. On 21 Oct a Machariel + Moros Navy Issue heavy hunter force executed a focused anti-Black-Ops/capital operation that eliminated multiple Redeemers and supporting assets. On 23 Oct a separate, large capital-centric response — led by Widows supported by Naglfar, Zirnitra and Phoenix NI-class capitals — re-engaged the system and contested capital mobility and cynos. These were not casual roams: both events show high organization and committed capital presence. Transit and unescorted operations in Mya are extremely hazardous.
Key Findings
- Two distinct, large-scale fleet actions (Oct 21 and Oct 23) indicate the system is an active flashpoint for capital and Black Ops hunting.
- Primary tactics observed:
- Fleet A (Oct 21): Machariel + Moros NI composition focusing on hunting Redeemer Black Ops and support ships.
- Fleet B (Oct 23): Widow-led Black Ops/capital fleet with Naglfar, Zirnitra, Phoenix NI — focused on area denial and counter-capitals.
- Timing pattern: Most activity concentrated on Tuesday 20:00–21:00 UTC and Thursday 13:00–14:00 UTC. These are notably high-risk windows.
- Low-risk, small-ship kills occurred sporadically (frig/cruiser losses) outside the major events, but the dominant danger remains large coordinated fleets and capitals.
- Cynos/jump vectors are active and targeted — there is strong evidence that covert-capital movement (Black Ops cynos, jump bridges) is in play.
Main Forces
- Identified combatants are highly organized but unattributed to known alliances in the available data. For clarity they are referenced here as:
- Fleet A (Aggressor): Machariel / Moros NI heavy hunter formation (Oct 21).
- Fleet B (Counter-Aggressor): Widow / Naglfar / Zirnitra / Phoenix NI capital formation (Oct 23).
Highest-Activity Individuals (Profiled)
Top participating characters observed in the major engagements:
- Optimiser — Moros Navy Issue (Fleet A)
- Legionare Legion — Moros Navy Issue (Fleet A)
- Mr Bio — Zirnitra (Fleet B)
- Ilyesledz — Moros Navy Issue (Fleet A)
- Kurt Harry Spett — Naglfar (Fleet B)
- Karl Rudolf Horse — Phoenix Navy Issue (Fleet B)
These names represent repeated, high-value participation during the Oct 21 and Oct 23 operations.
Threat Assessment
- System status: Low-Sec but behaving like a contested capital battlefield.
- Immediate risk: Capital- and Black Ops-level interdiction, cyno insertions, and interdictor/web wings present. Assume quick escalation to capital engagement.
- Recommended threat metric: 4.5 / 5.0 — exceptional caution required, unescorted or high-value ships are highly vulnerable.
Operational Guidance / Recommendations
- Avoid Mya if possible, especially on Tuesday 20:00–21:00 UTC and Thursday 13:00–14:00 UTC.
- Do not transit unarmed or unsupported — heavy losses are likely for solitary pilots and small gangs during major events.
- If you must operate in/through Mya:
- Travel with equivalent numbers or with a proper scout and fleet support. Capitals and Black Ops operate here; sub-capital fleets alone are at a severe disadvantage.
- Minimize on-grid time in any undocked operation. Pre-align to warp outs and maintain safe bookmarks at multiple distances.
- Assume covert cynos and jump-bridge activity; avoid carrying expensive cargo or capital-capable cynos into the system.
- Use increased situational awareness: check d-scan frequently, watch for cyno activity, and be wary of sudden large local spikes.
- Harass only with prepared counter-capital support; lone cloaky or Black Ops deployments are likely targeted by dedicated anti-cloak hunter forces.
- Cargo and high-value ships: Delay movement until the system cools, or reroute through alternative low-sec gateways — the risk of a capital engagement is too high for insured freighters and high-value escorts.
Final Note
Mya is currently a concentrated arena for organized capital and Black Ops warfare, not typical low-sec roaming. Treat all activity as potentially coordinated, and plan operations accordingly. This advisory is based solely on the provided analysis of recent fleet actions and observed participant profiles.