Everyshore Intelligence Network

EIN-Advisory: Groothese — Elevated Predatory Activity; Avoid Peak Windows

Report Date: 2025-11-17
Analyst: Everyshore Intel Network

Overview

• Groothese is showing sustained, high-intensity predatory behavior between 2025-11-14 and 2025-11-17. Although listed with a high-security designation, observed activity and tactics resemble low-sec/roaming behavior and present clear danger to solo and lightly fitted pilots.
• Current assessed system threat: 3.5 / 5.0 (elevated). Certain time windows spike to 4.5 / 5.0 during localized clashes.

Recent pattern (observed)

• Friday (14 Nov) ~15:00 UTC — Mid-day ganking wave: rapid opportunistic kills (Heron NI, Corax, Arbitrator). Threat ~3.0
• Friday (14 Nov) ~17:30 UTC — Targeted Mobile Cyno/structure removals. Predator using Nighthawk (Command Ship). Threat ~2.5
• Saturday (15 Nov) 09:30–10:45 UTC — Intense localized conflict: multi-kill engagement involving Battleship vs Strategic Cruisers and multiple Mobile Modules destroyed. Highest volatility. Threat ~4.5 (extreme). Main parties observed: Peter Powers and Edgar Berdnikow and associates.
• Sunday (16 Nov) ~23:00 UTC — Opportunistic late-night gank by Loki. Threat ~3.0
• Monday (17 Nov) ~03:30–03:46 UTC — Deep-night coordinated small-gang ganks: Cruisers and HACs targeted by Tengu/Loki/Gnosis compositions. Threat ~3.5

Known active predator profiles (top threats)

• Edgar Berdnikow — Rattlesnake (Battleship). Observed as most dangerous single actor during Saturday clash. Threat 4.8/5.0.
• Peter Powers — Nighthawk (Command Ship). Involved in structure/cynosural attacks and the Saturday fight. Threat 4.0/5.0.
• Organized Tengu/Gnosis gang — (Aladar Krahn, Cadhla Dioltas, Kayla Starchild, Miner McBride). Coordinated small-gang ganking with Strategic Cruisers. Threat 3.5/5.0.
• Hunter Dredd — Loki (Strategic Cruiser). Sporadic but skilled opportunist. Threat 3.0/5.0.
• Kayla Starchild — Tengu (Strategic Cruiser). Dangerous in group contexts. Threat 3.0/5.0.
• Note: A Widow (Black Ops) was present and destroyed during the Saturday clash — indicates high-capability forces were engaged in the local war.

Operational impact / risk summary

• Solo explorers, low-skill frigates and cruisers, haulers, and pilots deploying mobile modules are at the highest risk.
• Mobile Cynos and deployed mobile structures have been actively targeted and destroyed.
• High risk of collateral damage during return of the Saturday morning group; non-participants risk being caught in crossfire or misidentified.

Tactical recommendations (rooted in observed behavior)

• Avoidance windows:
  • Do not undock solo or run vulnerable ops in-system during:
    • Mid-day / afternoon spikes: ~14:00–18:00 UTC (Fri pattern observed)
    • Saturday high-risk window: ~09:30–10:45 UTC (observed intense confrontation)
    • Deep-night / early-morning: ~03:00–04:00 UTC (coordinated ganking)
• If you must operate in Groothese during risky hours:
  • Use fast, aligned ships or ships with a cloak (Covert Ops) and pre-set safe bookmarks. Do not loiter.
  • Avoid flying obvious soft targets (unfitted exploration frigs, unarmed cruisers, lightly tanked mission ships).
  • For missioning/ratting, consider switching to combat-capable ships with strong buffer/tank and drones, or operate with trusted wingmates.
  • Hauling/transport: postpone non-urgent moves. If critical, use shuttles/coveted frigates through the window, avoid cargo scanners, and align-to-station undock behavior.
  • Mobile module deployment: avoid deploying mobile cynos or structures unless you have a combat-ready escort. Mobile Cynos have been specifically hunted.
• If engaged or targeted:
  • Align and warp to a pre-set bookmark or station; evasive micro-warp + insta-warp out if possible.
  • Use local map awareness: Strategic Cruisers (Tengu/Loki) and Gnosis compositions favor burst DPS and webbing/tackle — fight only if you have a clear advantage.
  • Expect well-funded opponents in Rattlesnake/Black Ops/Command platforms during Saturday-level clashes — disengage unless fleet backup is available.
• Fleet/Group considerations:
  • If you plan to bring a fleet, be aware the Saturday engagement involved Battleships and Black Ops — escalate force only with full intel and numbers sufficient to counter heavy fittings.

Short checklist before entering Groothese

• Check current UTC time against the known high-activity windows above.
• Pre-fit warp core stabs, align, and have a safe bookmark.
• Avoid deploying mobile modules alone; keep expensive, slow targets docked during peak hours.
• Prefer fast, cloaky, or combat-capable fits for solo ops.

Conclusion

• Groothese is currently unstable: pockets of organized small-gang ganking operate alongside episodic, high-end localized warfare. Treat the system like contested low-sec despite its high-sec designation. Exercise strict caution, avoid the identified high-activity windows, and do not expose high-value or vulnerable ships without escorts or strong contingency plans.

Everyshore Intel Network — EIN-Advisory complete.