Everyshore Intelligence Network

Ironman journey

Ironman journey

Corp: Ironman Inc.

Ships: Algos

Profile last Updated at: 2025-10-16T12:26:57.416Z

Notes

Profile: Ironman journey
  • Character ID: 2122964211
  • Character Name: Ironman journey
  • Corporation: Ironman Inc. (ID 98460531)
  • Alliance: None recorded
  • Profile confidence: limited (single recorded engagement)

Executive summary

Ironman journey is an independent capsuleer tied to a small, likely solo/small-gang oriented corp (Ironman Inc.). The character has one recorded PvP engagement: a solo kill on 2025-10-10T20:30:23Z in Groothese (Everyshore) using an Algos. No recorded deaths. From the sparse record, Ironman journey appears to favor solo or small-scale PvP in Everyshore, and may hold a grudge against the slain pilot or their corporation (Aether Gate).

Confidence: Low — conclusions are extrapolated from a single recorded event.

Combat record (raw)

  • Total kills: 1
  • Total deaths: 0
  • Solo kills: 1
  • Last kill: 2025-10-10T20:30:23Z (UTC)
  • Last death: none recorded
  • Top victim: Bearman in Space (char ID 2123790441), corp Aether Gate (98813512) — 1 kill
  • Top ship used: Algos (shipId 32872) — last used 2025-10-10T20:30:23Z — use count: 1
  • Top system: Groothese, Everyshore — 1 kill (last at 2025-10-10T20:30:23Z)

Affiliations & likely social posture

  • Corporation-only member, no alliance attachment → likely independent operator or small-corporation pilot rather than alliance fleet regular.
  • Small corp environment suggests flexibility (solo-roaming, gatecamping, or small-gang ops) and limited access to large alliance logistics/intel.
  • No recorded alliances or multiple kills → probably not deeply enmeshed in regional diplomacy yet.

Confidence: Medium (based on corp/alliance fields and single-event record).

Possible grudges & rivalries

  • Primary candidate: Bearman in Space (Aether Gate) and by extension Aether Gate corp. The single recorded kill makes Bearman the immediate possible target of any retaliation/grudge.
  • Secondary: any local actors in Groothese or Everyshore who were aware of/affected by the engagement.
  • Note: with only one kill, this may have been opportunistic rather than part of an established feud — treat grudge inference as low-confidence.

Confidence: Low–Medium.

Preferred ships, fittings & tactics (inferred)

  • Preferred ship (from record): Algos (one recorded use).
  • Tactical profile (inferred): the Algos is commonly employed for agile, high-damage small-gang or solo PvP. Inferences:
    • Likely prefers solo engagement or small-gang brawling/harassment.
    • Possible fitting emphasis on mid-to-close-range offense and mobility rather than heavy long-term tanking (typical of Algos usage).
    • May favor hit-and-run, gank, or drone/short-range brawl styles depending on exact fit.

Confidence: Low (single datapoint). Specific fit and modules unknown.

Systems & geography of activity

  • Recorded system: Groothese (Everyshore) — sole activity logged there.
  • Regional focus: Everyshore (at least on the date of the recorded kill).
  • Operational inference: likely roams locally in Everyshore and Groothese vicinity or transits these routes regularly.

Confidence: Low (single event).

Temporal activity patterns

  • Known activity timestamp: 2025-10-10T20:30:23Z (UTC) — evening UTC.
  • Inferred active window: around 20:00–21:00 UTC based on the single timestamp.
  • Caveat: one timestamp is insufficient to establish reliable routine; further data required to confirm recurring play hours.

Confidence: Very low.

Threat / capability assessment

  • Offensive capability: demonstrated ability to score a solo kill. The use of an Algos suggests capability in small-scale PvP and a propensity for agile combat.
  • Survivability: zero recorded deaths — indicates either cautious play, luck, or low exposure so far.
  • Scale: likely a low-volume PvP actor for now (single recorded kill). Potential to escalate if recruiting or joining alliances.

Confidence: Low–Medium.

Data gaps & recommended follow-up (for intel priorities)

  • Frequency of activity (multiple timestamps needed).
  • Additional ship types and fits used by the character.
  • Corp/comms activity for Ironman Inc. (to determine whether pilot is solo or part of organized corp operations).
  • Any killmail metadata (gang size, modules fitted) to refine tactical profile.
  • Local intel from Groothese/Everyshore to determine whether the kill was opportunistic or part of a pattern.

(Delivery of follow-up is outside this profile; these are noted as gaps.)

Final assessment

Ironman journey is an independent capsuleer with a single confirmed solo kill in Groothese (Everyshore) on 2025-10-10 at ~20:30 UTC using an Algos. The character exhibits early signs of solo/small-gang PvP behavior and may have a nascent rivalry with Bearman in Space / Aether Gate. Current conclusions are tentative due to the extremely limited dataset; additional observations are required to refine this profile.