Everyshore Intelligence Network

Calendar

October 2025
Mo
Tu
We
Th
Fr
Sa
Su
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
November 2025
Mo
Tu
We
Th
Fr
Sa
Su
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Mya

Mya – 2025-10-25

EIN-Advisory: MYA — Elevated Danger / Heavy Fleet Activity (Everyshore Region)

Status: Low-Sec (expected PvP) — Assessment Level: ELEVATED DANGER
Local Threat Warning: HIGH — concentrated spikes (Tue/Thu UTC); persistent small‑gang threat remains

Executive Summary

  • Mya experienced two high‑intensity fleet escalations during 2025-10-19 → 2025-10-25 that shift the system from routine low‑sec risk to an active high‑risk theatre. The largest events occurred Tuesday 21 Oct (20:00–21:00 UTC) and Thursday 23 Oct (13:00–14:00 UTC).
  • Two dominant hostile fleet threads are operating in-system (“Blops Breakers” and “Blops Counter‑Fleet”). Multiple Black Ops battleships, Blops‑capable cruisers, and force auxiliaries were destroyed during the spikes — indicating capital‑grade capability and objective‑based warfare.
  • Persistent small‑gang and solo hunters continue targeting miners, frigates, and lightly defended ships outside peak fleet times.

What happened (key timeline)

  • Sun 19 Oct 08:00–09:00 UTC — small‑gang activity; isolated kill.
  • Mon 20 Oct — scattered kills vs industrials and frigates across three windows.
  • Tue 21 Oct 20:00–21:00 UTC — CRITICAL: coordinated fleet engagement; 23 kills including multiple Black Ops battleships, force auxiliaries, and high‑value capitals.
  • Wed 22 Oct 17:00–18:00 UTC — isolated opportunistic kill (Venture).
  • Thu 23 Oct 13:00–14:00 UTC — CRITICAL: secondary concentrated fleet action (17 kills). Several destroyed items listed with victim: null (deployables/structures/objectives).
  • Fri 24 / Sat 25 Oct — low‑level opportunistic/small‑gang activity.

Identified hostile threads (primary actors / profiles)

  • The Blops Breakers (Highest threat — Thread Level 5.0)

    • Profile: Heavy escalation fleet, covert jump deployment and focused target prioritization.
    • Reported ships: Moros Navy Issue, Machariel, Bhaalgorn, Zirnitra, Nyx.
    • Reported characters involved: Ilyesledz, Optimiser, Legionare Legion, Mapache Doom, Kalaratiri.
    • Behavior: Targeted Black Ops battleships, mobile cyno inhibitors, logistics and force auxiliaries. Avoid all contact.

  • The Blops Counter‑Fleet (Extreme danger — Thread Level 4.5)

    • Profile: Large response/retaliation fleet with objective removal/counter‑operations.
    • Reported ships: Naglfar (Dread), Zirnitra, Widow, Phoenix Navy Issue, Basilisk, Huginn.
    • Reported characters involved: Mr Bio, Kurt Harry Spett, Paquito, Karl Rudolf Horse, Athena Blackwell.
    • Behavior: Heavy interdiction, electronic warfare and structure/deployable kills.

  • T3 Cruiser Assassins / Solo Roamers (Thread Level ~3.0)

    • Example: Proteus operator (Michel Ferran). High risk to solo pilots and unescorted cruisers/industrials.

  • Light Hunters / Small‑Gang (Thread Level 2.5 and below)

    • Ships observed: Astero, Hecate, Thrasher Fleet Issue; recurring attacks on Mackinaw, Venture and other miners/haulers.

Operational Risk Guidance (rooted in observed data)

  • Avoid transit and operations in Mya unless you are explicitly prepared for capital/black‑ops engagement. The presence of capital and Blops fleets makes incidental contact potentially catastrophic.
  • Do NOT operate Black Ops battleships, Force Auxiliaries, or other high‑value assets in or near Mya without overwhelming escort and clear control of the area. Recent losses include such hulls; risk is immediate and verified.
  • Schedule any necessary operations far outside the documented peak windows. Analysts recommend off‑hours such as 00:00–04:00 UTC, but proceed with extreme caution — opportunistic small‑gang hunters remain active at all times.
  • Treat any fleet presence as potentially catastrophic. If you detect a large fleet entering Mya, assume Threat Level 5.0 until proven otherwise; disengage and extract.
  • Light and unescorted ships (miners, exploration frigates, industrials) are repeatedly targeted. If you must transit, prefer fast, warp‑capable ships with warp‑disruptor/point countermeasures or travel in adequately sized escort groups.
  • Expect objective‑based warfare (deployable/structure destruction). The presence of many victim:null entries indicates fights over objectives or structures; operations around known deployables are especially dangerous.

Tactical considerations for commanders

  • Do not rely on random local safety; the two main threads are organized and possess jump/Blops capability. Plan convoys and operations with this capability in mind.
  • Use scouts and long‑range observers to detect and avoid covert jump bridges and cynos; a large sudden spike in player count or capital signatures usually precedes the catastrophic windows observed.
  • If conducting recon or harassment, avoid exposing logistics and force auxiliaries inside the system unless supported by superior force.

Final assessment
Mya is currently an active theatre with organized, high‑resource belligerents engaging in fleet and objective warfare. The system is unsuitable for routine operations by lightly‑equipped pilots. Avoidance and careful timing are the primary mitigations available short‑term; any presence should be limited to operations that accept high probability of loss.

EIN will continue documenting activity frequency and threat patterns.

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.

More

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.

More

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.

More

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.

More

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.

More

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.

More

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.

More

Recent Monthly Reports