Everyshore Intelligence Network

EIN Advisory — Groothese (Everyshore) — HIGH THREAT (4.2/5.0)

Period covered: 2025-11-09 → 2025-11-15
System type: Low-Sec (contested, chokepoint-style activity)

Summary

• Groothese is currently a highly contested low-sec system with sustained, organized PvP activity. Analysis rates the system HIGH THREAT (4.2/5.0).
• Activity is driven by multiple coordinated small-gangs and at least one extremely potent solo Battleship pilot. Targets include T3 Cruisers, Black Ops Battleships, medium/heavy PvP hulls and unescorted industrial/exploration ships.
• The environment favors prepared aggression: mix of long-range tackle/recon, webbing, HAC damage platforms, and high-single-target battleship firepower.

Top identified threat threads (highest risk first)

1. Thread 2 — Edgar Berdnikow (Rattlesnake) — Thread-Level 5.0
   • Solo Rattlesnake destroyed multiple T3 cruisers and a Widow Black Ops in a single engagement. Treat this as a guaranteed-death threat for single or small-group subcap forces unless countered by capital-class response or overwhelming superior numbers executing focused heavy E-War.
2. Thread 1 — HAC/Recon Gang (Alexis glavor, Sick Artley, Jason Ozran) — Thread-Level 4.7
   • Small, highly coordinated gang: Vigilant + Lachesis + HACs (Vagabond/Legion) with occasional battleship support. They specialize in web+tackle + DPS bursts—very effective against non-logistic fleets and lone pilots.
3. Thread 4 — Solo heavy-battleship (V1ctorovich: Praxis/Raven) — Thread-Level 4.0
   • High-skill solo battleship pilots have successfully engaged T3s and battlecruisers; capable of quick, decisive kills.
4. Thread 5 — Peter Powers (Nighthawk Command Ship) — Thread-Level 4.0
   • Nighthawk observed targeting mobile deployables (MTUs, MMJUs, Cynos). Presence signals organized clean-up/disruption operations and additional fleet support.
5. Thread 6 — Multi-Drake Navy Issue fleet — Thread-Level 3.8
   • Faction BCs with high burst DPS used to rapidly eliminate E-War platforms (e.g., Falcon). Dangerous for EWar/Recon ships and small gangs.
6. Thread 3 — Gnosis duo (Miner McBride, Aladar Krahn) — Thread-Level 3.5
   • Persistent C-BC threat to fragiles and small ships; moderate danger to solo pilots.

Temporal risk windows (UTC)

• Highest-risk peaks:
  • Sunday 17:00–23:00 (prime Western / early EU evening) — heavy Thread 1 activity
  • Saturday 08:00–11:00 (EU / early RU window) — multiple T3s and Black Ops killed by Rattlesnake activity
  • Tuesday 00:00–05:00 (late West / early Asia) — volatile spike including Black Ops/Battleship engagements
• Other notable activity: Monday mid-evening and Friday mid-day with localized skirmishes.

Recent notable events (indicative only)

• Solo Rattlesnake destroyed multiple T3 cruisers and a Widow Black Ops at 2025-11-15 09:43 UTC.
• HAC+Recon gang repeatedly eliminated Drakes, Herons, and an industrial Porpoise on 2025-11-09 evening.
• Nighthawk engaged and removed mobile deployables on 2025-11-15; deployables are actively targeted.

Operational recommendations (rooted in observed patterns)

• Avoid Groothese during peak windows above. If you must transit, choose out-of-peak times.
• Do NOT operate high-value T3 Cruisers or Black Ops in Groothese alone or in small unsupportive gangs. The Rattlesnake and solo battleship actors have demonstrated the ability to kill high-performance hulls quickly.
• Industrial/exploration traffic (Porpoise, Epithal, Heron, Imicus, shuttles) is actively hunted—do not run industry or indy ops without heavy escort or during peak times.
• Deployable safety: Nighthawk-class actors have targeted MTUs, MMJUs and Cynos. Store or relocate fragile deployables outside high-risk windows; avoid leaving MTUs unguarded.
• Countering Thread 1-style gangs: expect long-range point/damp from Lachesis + strong webbing from Vigilant + HAC DPS. Effective mitigations include dedicated logistics, coherent fleet E-War/point control, or avoiding engagement entirely.
• Countering the Rattlesnake solo (Thread 2): analysis indicates the only reliable counters are dedicated capital intervention or overwhelming numbers focused on heavy electronic warfare. Small numbers of subcaps without concentrated EW/logistics are at extreme risk.
• Recon and scouts: use cloaky scouts and warp-out disciplines. Assume rapid collapse by local organized elements and plan instant disengage routes. Do not rely on isolated gate camping; threads operate in coordinated, mobile gangs.
• If operating combat fleets: include a prepared plan for long-range tackle and command ship presence (HEAVY missile/command bonuses seen) and include anti-tackle measures and logistics.

Tactical dos and don'ts (quick)

• Do: travel in numbers, bring logistics, bring ECM/ewar counters when possible, and remove deployables at observed Nighthawk times. Use cloaks/aligns for transit.
• Don't: solo-run T3s or Black Ops into Groothese during identified peaks; leave MTUs or MMJUs unguarded; assume single pilot safety.

Final assessment

• Groothese is contested and dangerous across multiple time zones with persistent, organized threat actors. Casual and solo operations carry high loss probability. Treat the system as hostile until evidence of reduced activity or presence of substantial allied force exists.

Everyshore Intel Network will continue monitoring systemic shifts; current advisory is strictly based on observed actor behavior and kill record for 2025-11-09 → 2025-11-15.