Everyshore Intelligence Network

minh me

minh me

Corp: Master Miners

Ships: Rokh, Mobile Tractor Unit, Capsule, Vexor, Nemesis

Profile last Updated at: 2025-10-04T12:27:30.130Z

Notes

Everyshore Intelligence Network — Character Profile

Character: minh me
Character ID: 2117072054
Corporation: Master Miners (814655894)
Profile generated: 2025-10-04

Executive summary

minh me is a low-activity capsuleer with a clear mining/industrial profile who has been engaged repeatedly and unfavorably with one specific aggressor (Merimah Aniss). Dataset shows episodic activity in Syndicate (KTHT-O) with both capital/large-ship mining (Rokh, MTU) and occasional small-ship action (Vexor, Nemesis). Total combat record is poor (1 kill / 7 deaths), with the majority of deaths attributable to a single opponent and one multi-actor event on 2025-09-30.

Confidence in core observations: medium (limited sample size).

Key statistics

  • Total kills: 1
  • Total deaths: 7
  • Solo kills: 0
  • Last kill (recorded): 2025-09-14T21:01:09Z
  • Last death (recorded): 2025-09-30T18:26:40Z

Top contacts (adversarial)

  • Merimah Aniss (char 2123106110, corp Silk Dance)
    • Role: Primary antagonist. Responsible for 5 of minh me’s recorded deaths (top killer). Also appears as minh me’s only recorded victim (minh me has one kill on Merimah). Timestamp overlap on 2025-09-14 indicates repeated engagements/two-sided rivalry.
    • Interaction intensity: high (for dataset).
  • Group kill on 2025-09-30 (same timestamp 18:26:40Z) included members from:
    • RAZOR Alliance (Calanthe Maulerant, Constance Navarette — The Hatchery)
    • Shadow Cartel (Dr Zuma, Evilelmo — Mea Culpa.)
    • This indicates a coordinated multi-actor kill against minh me on 2025-09-30.

Grudge likelihood: Merimah Aniss — very likely. RAZOR / Shadow Cartel actors — likely opportunistic or coordinated aggressors (possible response to mining in contested space).

Confidence: medium-high for Merimah, medium for the multi-actor group.

Preferred ships & inferred roles

Recorded ships (use count 1 each, recent uses shown):

  • Rokh (battlecruiser/battleship-class) — last used 2025-09-30T18:26:40Z
    • Inference: Primary large-ship mining platform or fleet-mining battleship. Likely fitted for mining or tanked for belt ops.
  • Mobile Tractor Unit (shipId 33475) — last used 2025-09-30T02:46:58Z
    • Inference: Deployed in industrial/mining operations to collect/minimize haul loss; indicates organized mining ops rather than lone AFK miner.
  • Vexor — last used 2025-09-14T21:00:17Z
    • Inference: Drone cruiser — can be used for ratting, small-gang PvP or mining support.
  • Nemesis (stealth bomber) — last used 2025-09-14T20:49:17Z
    • Inference: Occasional use of covert-frigate tactics — suggests willingness to fly small, combat-oriented ships (recon/strike).
  • Capsule — last used 2025-09-14T21:01:09Z

Operational profile inferred:

  • Primary: Organized mining operations (Rokh + MTU usage).
  • Secondary/occasional: Small-ship PvP or covert engagements (Vexor, Nemesis).
  • Not a solo PvP specialist (zero solo kills; heavy death ratio).

Confidence: medium.

Systems & geography of activity

  • KTHT-O (Syndicate) — only system with recorded activity (killCount 1; last at 2025-09-14T21:01:09Z).
  • Multiple events tied to Syndicate region timestamps (9/14 and 9/30). MTU deployment suggests operations in or near asteroid belts/ice fields in that region.

Inference: Mining/industrial operations primarily in Syndicate, specifically KTHT-O or nearby systems.

Confidence: low-medium (dataset small; possible other systems not recorded).

Temporal activity patterns (UTC)

Recorded activity timestamps:

  • 2025-09-14: 20:49:17Z (Nemesis), 21:00:17Z (Vexor), 21:01:09Z (Capsule / last kill event)
    • Pattern: concentrated activity over ~12 minutes in late evening UTC.
  • 2025-09-30: 02:46:58Z (MTU deployment), 18:26:40Z (Rokh destruction / multi-kill)
    • Pattern: operations at both pre-dawn/early morning and early evening UTC.

Inferred likely active windows (limited sample):

  • Evening UTC: ~20:30–21:10 (observed on 2025-09-14)
  • Early evening UTC: ~18:20–18:40 (observed 2025-09-30)
  • Early-morning UTC: ~02:30 (MTU deployment on 9/30)

Confidence: low (very small number of timestamps; treat as indicative rather than definitive).

Behavior & tactics (inferred)

  • Primarily industrial/mining operator using large hulls (Rokh) supported by MTU deployments — suggests participation in fleet or corp mining rather than solo belt-mining.
  • The presence of Nemesis and Vexor in the same timeframe as a PvP encounter suggests occasional switching to small combat ships (possibly for scouting, harassment, or escape attempts).
  • High death ratio and lack of solo kills indicate low PvP competency or frequent exposure to superior forces.
  • Recurrent conflict with a single aggressor (Merimah Aniss) implies either personal rivalry, contested mining claims, or repeated encounters in the same systems.

Confidence: medium.

Vulnerabilities & risk profile

  • Exposed during organized mining ops (MTU + Rokh): targetable by roams/rostered gangs — evidenced by multi-actor kill on 2025-09-30.
  • Repeated losses to one actor (Merimah Aniss) indicate tactical or situational disadvantage in encounters with that opponent.
  • Lack of recorded solo kills and frequent use of large mining hulls makes the character an attractive target for gankers and roams in contested systems.

Confidence: medium.

Conclusions

  • minh me is best characterized as an industrial-focused capsuleer operating in Syndicate with intermittent small-ship PvP activity.
  • Main adversary: Merimah Aniss (Silk Dance) — responsible for most recorded deaths and likely a sustained grudge.
  • A single coordinated multi-actor engagement on 2025-09-30 involved RAZOR Alliance and Shadow Cartel members, indicating exposure to alliance-level harassment or roaming groups.
  • Activity appears concentrated in evening UTC windows with occasional early-morning operations (MTU deployment).

Overall confidence: medium (dataset is small; conclusions should be treated as probabilistic).