Calendar

Mya

Mya – 2025-11-09

EIN-Advisory: Mya — High-Risk Low-Sec (System Threat Level 4.0) — Avoid EVE Prime Time Slots

Date: 2025-11-09
System: Mya (Everyshore) — 41 kills recorded (Data window: 2025-11-02 → 2025-11-09)

Summary

  • Mya is currently a high-risk low-sec system with organized fleet warfare. Intelligence shows concentrated, coordinated operations by Strategic Cruiser-led groups and Faction Battleship forces, with a sharp escalation on 6–7 Nov.
  • Overall Threat Level: 4.0 (High). Expect highly skilled pilots, EWAR and tackle, and occasional capital escalation.

Key Observations (grounded in analyst data)

  • Peak activity window: 16:00–18:00 UTC (consistently busiest, including the large spikes on Thu 6 Nov and Fri 7 Nov). Most fleet engagements and kills occurred during this period.
  • Main fleet profiles observed:
    • Loki/Tengu-led Strategic Cruiser fleets, supported by Force Recon (Rapier, Arazu) — heavy EWAR and coordinated tackle (Loki appears in ~25 of 41 kills).
    • Barghest-led Faction Battleship groups, supported by Huginn combat recon — direct opposition to the Loki-led groups in several major skirmishes.
    • Capital escalation present on 6 Nov: Zirnitra, Naglfar, and a Minokawa were involved in a single high-profile engagement — indicates willingness to bring dread/force auxiliary assets into Mya.
  • Opportunistic activity: Solo ganks on haulers/industrials and low-cost frigate skirmishes continue outside peak hours; Dominix/Deimos-class ships and battlecruisers have been used successfully against lone industrials and MTUs.
  • Capsule deaths are high; pilots have been unable to escape during many engagements.

Identified Risks

  • Coordinated fleet combat (Strategic Cruiser vs Barghest/BB fleets) — high lethality, dedicated EWAR/tackle, and frequent focused targeting of recon/logi/support assets.
  • Capital involvement raises the risk of sustained sieges and loss of infrastructure/force auxiliaries.
  • Single-ship transit risk for haulers and miners remains elevated outside peak hours due to opportunistic high-DPS hunters.

Recommended Actions (Operational Advisories)

  • Avoid transiting Mya during peak hours (16:00–18:00 UTC), and especially avoid it on Thursdays/Fridays given recent spikes (6–7 Nov).
  • Do NOT move high-value non-combat ships (haulers, freighters, capitals, force auxiliaries) through Mya without dedicated, combat-capable fleet support and scouts.
  • If you must transit:
    • Schedule movements outside the identified peak window.
    • Use fast, hard-to-tackle ships (interceptors/Covert Ops if mission permits) or ship fittings optimized for align/warp-out speed and interdiction resistance.
    • Employ local situational precautions: approach gates/items aligned, have an exit plan (pre-aligned safes), and assume EWAR/tackle will be present.
  • Industrial ops (mining/MTUs) should be limited or temporally shifted; unescorted barges and MTUs are attractive targets for single-ship hunters.
  • Recon/logi/ewar pilots operating in or near Mya should be aware they are high-priority targets during fleet clashes — bring countermeasures and avoid isolation.

Who is engaged

  • Large fleet clashes involve Loki-led Strategic Cruiser groups vs Barghest-led Faction Battleship groups. The specific corps/alliances involved are not identified in this dataset; treat the actors as capable, organized adversaries who have frequently operated together in the system.

Closing
Mya has moved from opportunistic low-sec activity to organized fleet warfare with capital risk. Plan operations around the 16:00–18:00 UTC danger window, avoid solo high-value transits, and treat the system as contested until further stabilization is observed.

Recent Advisories

Mya – 2025-11-18

TL 4.2

Mya (Everyshore, Low-Sec) is presently a high-risk system with a sustained, organized hunting force targeting fragile, stealth, and industrial ships. Peak danger windows are UTC 08:00–10:00 and 17:00–21:00, during which an organized hunter cohort and jump-capable assets operate.

Mya – 2025-11-17

TL 4.2

Mya is a hostile patrol zone with active, persistent hunters preying on miners and explorers. The primary threats are Ronen Uitra and Boruet Annages, with a Panther black-ops battleship increasing the risk of coordinated hotdrops.

Mya – 2025-11-16

TL 4.2

Mya is an active hunting ground in Everyshore's Low-Sec where repeated cloaky and advanced PvP hulls interdict and kill unescorted miners, explorers, and small industrial ships. Threat level is high (4.0) with named actors using covert platforms such as Cenotaph, Manticore, Loki, and Hecate, making transit and routine operations in Mya high risk and requiring escorts and vigilance.

Mya – 2025-11-15

TL 4.2

Mya remains an elevated-threat low-sec hunting ground dominated by repeat offenders, with targeted ambushes against exploration and resource vessels and agile, high-skill skirmishes. Primary repeat offenders Boruet Annages and Ronen Uitra deploy heavy hulls (Maelstrom, Cenotaph, Cerberus) and tactical/strategic hulls (Hecate, Loki) along with covert assets and stealth tactics, making solo or lightly defended transit hazardous.

Mya – 2025-11-14

TL 4.2

System Mya is currently a severe volatility hotspot in Low-Sec, highlighted by a confirmed Loki-heavy fleet action that destroyed a Barghest wing and raised the risk of engagement system-wide. Ongoing threats include a persistent solo Tengu pilot named Aladar Krahn and frequent small-gang interdictions by various groups, making peak-window presence exceptionally dangerous.

Mya – 2025-11-13

TL 4.2

MYA (Everyshore) in Low-Sec is an active combat locus with coordinated Loki/Tengu fleets and capital presence driving high-risk conditions, especially during the 16:00–18:00 UTC window on Nov 6–9, 2025. Key threats are Loki Fleet, Barghest Fleet, and a Dreadnought Contingent, backed by recon/E-war support and capital escalation.

Mya – 2025-11-12

TL 4.2

Mya is a contested Low-Sec system experiencing sustained, coordinated fleet warfare with capital escalation observed. Analysts warn unaligned pilots and non-combat traffic to avoid the system during the 16:00–18:00 UTC peak window, especially on Thursdays and Fridays.

Recent Monthly Reports