Ilavane Meere Riraille

Ilavane Meere Riraille — Everyshore Intelligence Profile

Basic summary

Character: Ilavane Meere Riraille (ID 2122181724)
Corporation: EVE University (917701062) — Alliance: Ivy League (937872513)
Killboard snapshot: 23 kills / 17 deaths (K/D ≈ 1.35) — 7 solo kills
Recent activity window in dataset: lastDeath 2025-10-11T15:19:09Z, lastKill 2025-10-11T15:52:15Z

Top ships recorded (by use count)

Ferox — useCount 9 (last used 2025-10-11T15:20:25Z)
- Primary hull used. Indicates a preference for battlecruiser-scale engagements: small-gang or fleet brawling with medium turrets/launchers or missile fits.
Capsule — useCount 5 (last used 2025-10-11T15:19:09Z)
- Multiple pod records: either podded several times or recorded pod kills; shows survivability/podding events are present in his history.
Punisher — useCount 4
- Frigate use for solo or skirmish work; fits with 7 solo kills.
Retribution — useCount 3
- Another small-ship option for solo/FC scouting, gatecamp or duel scenarios.
Brutix Navy Issue — useCount 3
- Heavy cruiser/battlecruiser role available; consistent with BC/BCN use (Ferox, Brutix N. Issue).

Inferred behavior:

Primary overall role: battlecruiser-centric PvP (Ferox + occasional Brutix NI) with capability to drop into frigates for solo work or small gang skirmishes.
Mix of soloable fights (7 solo kills) and participation in small- to mid-sized fleet engagements.

Top systems by kill count:

Isbrabata (Metropolis) — 9 kills (last activity there 2025-09-30T01:42:35Z)
- Major hotspot; large cluster of activity on 2025-09-30 suggests participation in a significant fight/ambush.
Ahbazon (Genesis) — 8 kills (last activity 2025-10-11T15:20:25Z)
- Recent concentrated activity; recent Ferox use timestamped here.
Eytjangard (Metropolis) — 2 kills
Floseswin (Metropolis) — 1 kill
EUU-4N (Insmother) — 1 kill (last at 2025-10-11T15:52:15Z)

Operational pattern:

Primary regions: Metropolis and Genesis. Activity clustered in a few systems rather than widely dispersed — likely operating around local staging, jump routes or commonly used low-security lanes in those regions.

Notable timestamp clusters:

2025-09-30 ~01:42 UTC — big cluster (Isbrabata). Suggests late-night / early-hours activity (could be alliance/corp ops or regional fights).
2025-10-11 between ~14:07 and ~19:31 UTC — several events (Ahbazon and Insmother). Strong afternoon UTC activity centered around ~15:00–16:00 UTC on that date.

Probable activity windows (based on recorded engagements):

Characters who have killed Ilavane multiple times (top killers)

Dickinson planet (2119468582) — 4 kills (corp Yamata No Orochi Yamete) — last contact 2025-09-30T01:42:12Z
Itoreya Tsuruomo (2119468550) — 3 kills (same corp) — 2025-09-30T01:42:12Z
Moonface Abyss (2116480810) — 3 kills (same corp) — 2025-09-30T01:42:12Z
Yamon Airuta (2119468513) — 3 kills (same corp) — 2025-09-30T01:42:12Z
- The four above are co-located by timestamps and corp — indicates a single large engagement/ambush in Isbrabata on 2025-09-30 where Ilavane was repeatedly engaged/podded by members of Yamata No Orochi Yamete. Those pilots are high-priority grudges.
Mecclovin Tiberius Skywalker (2123701397, Ivy League) — 3 kills (last 2025-09-15T22:03:49Z)
- Same alliance/corporation association — repeated internal kills suggest either frequent friendly podding/duels within corp/alliance or recurrent fleet mishaps. Not necessarily hostile but should be flagged.

Top victims (people Ilavane has killed repeatedly or recently)

Several single-kill victims: Amber Horizons, Benjamin Daerling, Bigus Dingus DOI (Ivy League), Busterguy Omaristos, Dima125 — no high-value repeat victim list beyond single kills. No clear rivalry from topVictims.

Grudge summary:

Primary external grudges: the Yamata No Orochi Yamete pilots listed above (clustered kills on 2025-09-30). Expect animosity/retaliation toward that corp.
Secondary/internal items of interest: Mecclovin Tiberius Skywalker (same alliance) — frequent internal kills may indicate rivalry, podding, or contested fleet leadership.

2025-09-30 ~01:42 UTC (Isbrabata, Metropolis) — cluster of deaths to Yamata No Orochi Yamete pilots (multiple entries, multiple kills). Significant defeat / large-scale fight.
2025-10-11 ~15:20 UTC (Ahbazon, Genesis) — active in Ferox; recent cluster of kills in Genesis (8 kills in Ahbazon overall across dataset); also recorded death at 15:19 UTC same day (pod record), then kill at 15:52 UTC in EUU-4N — indicates back-and-forth engagements that day.
Repeated Ferox usage with recent timestamps indicates ongoing BC role in current operations.

Uses BC hulls frequently (Ferox, Brutix NI) — likely fits optimized for brawling or skirmish missile/turret setups.
Maintains capability to switch to frigates for solo work (Punisher, Retribution) — versatile between fleet BC role and solo harassment/scouting.
Pod interaction (capsule entries) is non-trivial — multiple pod events imply he is frequently involved in decisive fights where ships are lost.
Engagements appear concentrated rather than roving — likely operates around alliance/corp staging systems and known local conflicts.

Systems: Isbrabata (Metropolis), Ahbazon (Genesis), Eytjangard, Floseswin — prioritize Isbrabata and Ahbazon.
Pilots (priority):
- Dickinson planet (2119468582)
- Itoreya Tsuruomo (2119468550)
- Moonface Abyss (2116480810)
- Yamon Airuta (2119468513)
- Mecclovin Tiberius Skywalker (2123701397) — internal
Ship types to expect: Ferox and other BC hulls; occasional Punisher/Retribution for solo ops.

Profile compiled from provided kill/death records (timestamps and system names).