Everyshore Intelligence Network

Profile: Optimiser (Character ID: 2118069486)

Corporation: Outback Steakhouse of Pancakes (ID 98557229)
Alliance: Deepwater Hooligans (ID 99009927)

Summary

• Combat record: 24 kills, 1 death, 0 solo kills. Last kill: 2025-10-24T02:32:32Z. Last death: 2025-10-17T03:42:51Z.
• Behavioral signature: Fleet-oriented heavy-ship pilot (low death rate, no solo kills). Predominantly operates capital/dread class and heavy subcapital vessels. Concentrated activity in Everyshore (Mya) with extended operations into Heimatar, Metropolis and Pochven.

Combat history highlights

• Total engagements recorded: 24 kills across multiple systems and regions; only one recorded death (single-event, clustered with multiple enemy pilots).
• Top victims are distributed across several alliances (Shadow Cartel, Drifter., Northern Coalition./Negative Feedback etc.), each with single kills — indicates opportunistic targeting rather than sustained vendettas in those cases.
• Top killers: a coordinated strike by members of Vyraj. (characters D0MINUS, EmperorVeles, Kurunto, Ryvian) — all listed as having killed Optimiser at the same timestamp (2025-10-17T03:42:51Z), indicating a coordinated engagement or gang action that caused his sole death.

Preferred ships and implied role

• Moros Navy Issue — useCount: 17; lastUsed: 2025-10-21T20:57:19Z
  • Primary platform. Indicates regular use of a dreadnought-class siege role (capital-level firepower and structure/ship siege focus). High repeat usage suggests Optimiser is a designated capital pilot in fleet ops and/or structure/battleline engagements.
• Redeemer — useCount: 5; lastUsed: 2025-10-24T02:32:32Z
  • Secondary heavy ship usage; consistent with participation in subcapital/assault roles (supporting or leading small-to-medium gang actions when not in dreadnought).
• Kronos — useCount: 3; lastUsed: 2025-10-17T03:42:51Z
  • Tertiary heavy-battleship/marauder-type presence. Presence of multiple heavy-ship classes shows flexibility to shift between capital and heavy subcapital commitments.

Systems of activity (pattern)

• Mya (Everyshore) — 11 kills; last activity there at 2025-10-21T20:57:19Z. Primary hunting/operation ground. Everyshore appears to be Optimiser’s local area of operations.
• Siseide (Heimatar) — 6 kills; last at 2025-10-02T01:24:39Z. Secondary operating ground with repeated activity.
• Uisper (Metropolis) — 5 kills; last at 2025-10-24T02:32:32Z. Active in nearby metropolitan systems, likely projecting force regionally.
• Ala (Pochven) — 2 kills; last at 2025-10-17T03:41:50Z. Occasional forays into Pochven space.

Temporal pattern / activity windows (UTC)

• Activity clustered in late evening through early morning UTC. Notable timestamps:
  • 20:57:19Z (Moros use in Mya) — late-evening operation.
  • 01:24:39Z (Siseide) — post-midnight operations.
  • 02:32:32Z (kill in Uisper) — early morning.
  • 03:41–03:42Z (death and other activity) — early-morning cluster that produced his only death.
• Inferred primary activity window: approximately 20:00–04:00 UTC (consistent with peak fleet operations crossing prime-time zones).

Possible grudges and relationships

• Vyraj. (alliance) — high-probability grudge/retaliation vector: members D0MINUS, EmperorVeles, Kurunto, Ryvian are credited with Optimiser’s only recorded death at the same timestamp (2025-10-17T03:42:51Z). This looks like a coordinated attack that could have triggered ongoing animosity between Optimiser’s corp/alliance and Vyraj. or its local cells.
• Shadow Cartel — appears as a victim in topVictims list (AnarkiTheStorm, Bear Gilead). Multiple Shadow Cartel contacts suggest prior conflict or contestation in overlapping operational space.
• Know-Nothings / Best Logi Pilot — same character appears under multiple alliance affiliations as a victim, indicating repeated engagements with that pilot or their logistics role; may have a specific grudge or tactical focus on logistics targets.
• Other named entities (BadmanLarry Capsuleer / SHRED., Negative Feedback, Northern Coalition.) are single-victim entries — lower-confidence grudges but potential for opportunistic conflicts.

Tactics & behavior inference

• Fleet-first operator: 0 solo kills and heavy use of capital suggest Optimiser is embedded in organized fleet structures and relies on fleet logistics/escort for survival and strike capability.
• Capital-level focus: dominant use of Moros Navy Issue implies Optimiser operates in siege/structure-busting or capital-battle roles rather than small-gang roam PvP. Repeated Moros use indicates seat of value and experience in capital ops.
• Flexibility: occasional Redeemer and Kronos use shows he can field heavy subcap assets when capital deployment is unnecessary or unavailable.
• Survivability: 24:1 kill:death ratio indicates conservative engagement selection, strong fleet support, or operational tradecraft that minimizes isolated exposure. The single death was a coordinated multi-pilot strike — vulnerability appears highest when caught without adequate support or in contested pockets.

Intelligence assessment / notable vulnerabilities

• Single death event clustered against Vyraj. actors shows a successful coordinated counter against Optimiser — suggests that when properly targeted and overwhelmed by enemy coordination, Optimiser’s capital can be neutralized.
• Concentration in Mya (Everyshore) creates a predictable operational signature; repeated presence there increases the risk of deliberate counter-actions by enemies operating in the same system.

Appendix — key datapoints

• Kills: 24 | Deaths: 1 | Solo kills: 0
• Last kill: 2025-10-24T02:32:32Z (Uisper, Metropolis)
• Last death: 2025-10-17T03:42:51Z (cluster kill by Vyraj. pilots)
• Top ships: Moros Navy Issue (17), Redeemer (5), Kronos (3)
• Top systems: Mya (Everyshore) 11 kills; Siseide (Heimatar) 6; Uisper (Metropolis) 5; Ala (Pochven) 2

End of profile.