Everyshore Intelligence Network

Ena Yleto Yanumano

Ena Yleto Yanumano

Corp: Ironman Inc.

Ships: Loki, Panther

Profile last Updated at: 2025-09-27T12:26:34.353Z

Notes

Ena Yleto Yanumano — Everyshore Intelligence Profile

Overview

  • Character: Ena Yleto Yanumano (ID 2121928256)
  • Corporation: Ironman Inc. (ID 98460531) — no alliance listed
  • Region of activity: Everyshore
  • Combat record (sample size small): 2 kills, 1 death

Combat Record Summary

  • Total kills: 2
  • Total deaths: 1
  • Last recorded kill: 2025-09-26T13:41:51Z (Everyshore — Elarel)
  • Last recorded death: 2025-09-21T08:13:06Z (killer: DimanLin)

Top victims (by character)

  • DimanLin (ID 317143011) — appears twice as a victim (recorded under different corporations)
  • Tauras Elarik (ID 2113896510) — one victim

Top killer(s)

  • DimanLin — recorded as killer of Ena (single recorded death). Data shows the same character listed across different corp contexts.

Top systems (kills)

  • Elarel (Everyshore) — last recorded: 2025-09-26T13:41:51Z
  • Groothese (Everyshore) — last recorded: 2025-09-21T08:54:45Z

Top ships used

  • Loki — useCount 2 (last used 2025-09-26T13:41:51Z)
  • Panther — useCount 1 (last used 2025-09-21T08:54:45Z)

Kill/death ratio (sample): 2:1 — low sample size, interpret cautiously.

Recent Timeline (noted interactions)

  • 2025-09-21, 08:13 UTC — Ena recorded death; killer logged as DimanLin.
  • 2025-09-21, 08:54 UTC — Ena recorded a kill in Groothese while listed as using a Panther.
  • 2025-09-26, 13:41 UTC — Ena recorded a kill in Elarel while using a Loki (most recent activity).

The sequence shows Ena was killed and later re-engaged the same day, indicating quick resumption of PvP activity.

Preferred Ships & Implications

  • Loki (2 uses) — most frequently used ship in the dataset. Suggests:
    • Preference for a flexible, high-skill hull (strategic/T3-class behavior).
    • Likely fitted for solo or small-gang PvP with adaptable modules and covert/stealth movement options.
  • Panther (1 use) — single recorded use tied to a kill on 2025-09-21. Indicates willingness to operate in at least one alternate hull/role.

Overall implication: Ena favors a tactical, potentially stealth-capable profile rather than large fleet-only engagement.

Systems of Operation

  • Active in Everyshore region, with recorded kills in:
    • Elarel (recent)
    • Groothese
  • Movement pattern suggests local roaming inside Everyshore rather than long-range projection from another region.

Known Interactions and Possible Grudges

  • DimanLin (ID 317143011) is the primary recurring interaction:
    • DimanLin appears both as Ena’s top victim and as the character who killed Ena.
    • Presence in multiple corp contexts for DimanLin suggests either an alt/dual-allegiance or frequent corp changes — repeated contacts indicate a personal rivalry or recurring encounters.
  • Tauras Elarik is a one-off victim; no clear pattern beyond a single engagement.

Conclusion on grudges: The strongest indicator of a grudge or personal rivalry is with DimanLin — mutual kills and repeated encounters imply ongoing adversarial contact.

Likely Times of Activity

  • Recorded UTC times: ~08:13, ~08:54, ~13:41.
  • Pattern suggests activity in the morning through early afternoon UTC (broad window roughly 06:00–15:00 UTC), though dataset is small and sparse.

Playstyle & Behavioral Indicators

  • Solo/small-gang PvP operator: low kill totals but use of a Loki implies skilled solo/small-group engagements, flexible fittings, and tactical approaches.
  • Opportunistic and persistent: after being killed, Ena re-engaged the same day and secured at least one kill, showing resilience and continued local presence.
  • Local focus: all recorded combat events occur within Everyshore, pointing to regional familiarity and repeated patrol/roam patterns.

Threat Assessment (Everyshore context)

  • Capability: Moderate — low absolute kill count but access to a Loki indicates potential to field a dangerous and flexible fit for small-scale PvP. Panther usage adds tactical variety.
  • Profile suggests a competent, opportunistic pilot operating locally in Everyshore with a specific recurring adversary (DimanLin). Given the small dataset, treat Ena as a likely small-gang/solo threat rather than a fleet commander.

Behavioral Red Flags / Indicators to Monitor

  • Repeated interactions with the same character (DimanLin) — monitor future encounters to determine whether this escalates into continued harassment, revenge fights, or coordinated duels.
  • Continued Loki usage — track fittings and combat outcomes to reassess threat level as more data appear.
  • Concentrated activity in Elarel and Groothese — these systems may be centers of Ena’s operations or staging.

Profile prepared by Everyshore Intelligence Network (EIN) — based on provided kill/death/event logs.