Everyshore Intelligence Network

Hunter Dredd — Everyshore Intel Profile

Executive Overview

Hunter Dredd is an aggressive combat pilot flying with the corporation Dark Chapter inside the Transgress alliance, with 50 recorded kills and zero recorded deaths in the provided dataset. His engagement style is solo-leaning, registering 33 solo kills out of 50 total (66%), indicating a strong preference for independent action rather than fleet-reliant operations. The most recent recorded kill is timestamped 2025-11-17 11:49 UTC, and multiple linked ship and system timestamps place activity in mid-November 2025. This dataset shows sustained offensive output concentrated in a handful of systems and against recurring targets, but offers no direct evidence of corporate orders or formal fleet doctrine. There are no entries in topKillers, so there is no recorded response or repeated opposition against him in this data. Any broader conclusions about strategic objectives, command relationships, or out-of-band logistics are Insufficient data.

Operating Pattern

Hunter’s actions are heavily concentrated in a small set of systems, with a clear highest-volume locus. Activity by kill volume, ordered high to low, is:

• Bherdasopt (Genesis) — 22 kills, last activity 2025-10-20 11:39 UTC
• Alachene (Everyshore) — 13 kills, last activity 2025-11-16 14:11 UTC
• Elarel (Everyshore) — 8 kills, last activity 2025-11-17 11:49 UTC
• Gerper (Everyshore) — 3 kills, last activity 2025-10-30 04:57 UTC
• Groothese (Everyshore) — 2 kills, last activity 2025-11-16 23:18 UTC

The geographic footprint is split between Genesis (a single high-volume system) and Everyshore (multiple systems), suggesting either trans-regional operations or a shift of focus over time. When all recorded timestamps are compiled, Hunter’s activity clusters into discernible UTC windows. The primary dense window is approximately 10:00–13:00 UTC, anchored by repeated events at ~11:39–11:49 UTC; a secondary, smaller window appears around 22:00–00:00 UTC, anchored by a late event at 23:18 UTC. Active in the last 14 days.

Ships & Tactics

Hunter’s ship usage is heavily concentrated in two hulls, with one dominant platform and a secondary cruiser. The top hulls by use count are:

• Loki — Strategic Cruiser, 44 uses, last used 2025-11-17 11:49 UTC
• Orthrus — Cruiser, 7 uses, last used 2025-11-13 08:49 UTC

Insufficient data for a third top hull. The overwhelming reliance on the Loki (44 of 50 recorded kills associated with its use) implies a consistent doctrine around the Strategic Cruiser’s capabilities and fit choices, as opposed to a diverse multi-hull approach. The Orthrus appears as a secondary tool, used far less frequently and last recorded several days prior to the latest Loki activity. From pure usage counts, Hunter favors a narrow, repeatable ship loadout rather than experimentation across many classes. Any specific modules, fittings, or role specializations beyond hull identity are Insufficient data.

Targets

Hunter demonstrates focused targeting behavior with several repeat victims. The top individual victim is KaviengScout of SAVE EVE-Stop Demolition Bases (no alliance listed) with 13 recorded kills. Sergiolino of G.T.U. follows with 6 kills. Additional repeated victims include Franklin morning star of ARC Security (3 kills) — noted as belonging to the alliance I Showed You My Probes... Please Respond... — and Parces of Center for Advanced Studies (3 kills). Cree Canderou of University of Caille appears twice. These numbers show sustained pressure on a small set of characters and corporations rather than a broad, evenly distributed victim set. One-off or lower-frequency victims are present but do not materially change the picture of targeted harassment or campaigning against specific corp actors. Any motive connecting these attacks to wider political or economic objectives is Insufficient data.

Losses, Gaps & Confidence

There are zero recorded deaths for Hunter in this dataset and no entries in topKillers, so his loss profile and survivability under sustained counteraction are Insufficient data. The dataset contains 50 total events and yields a High confidence rating in the described patterns based solely on the provided information.