Heavy Armor Brawl Turns Deadly in J-Space: Wolves Amongst Strangers and E.C.H.O. Slug It Out Before Kite Fleet Snuffs 31 Billion ISK
On June 14, 2026, capsuleers in the wormhole system J123235 (E-R00027) witnessed a classic EVE Online drama: a committed heavy armor brawl between two experienced wormhole groups that suddenly escalated into a chaotic bloodbath when a third-party kite fleet crashed the party. Roughly 31 billion ISK in ships and modules were destroyed in the ensuing carnage, leaving wrecks scattered across the system and pilots cursing (or laughing) at the unpredictability of J-space.
The battle report is available here: capsuleers.app/tools/battle-report/545f1060-8b37-4288-9a6a-a23430003f78
The Rivals: Wolves Amongst Strangers (LUPUS) vs. E.C.H.O.
Wolves Amongst Strangers (alliance ticker LUPUS) is a well-known wormhole PvP alliance with around 685 members. It includes prominent corporations such as Almost Dangerous (primarily US/EU English-speaking timezone, often abbreviated OMGGF) and Little Red Riding Hole (RE-HO, a German-speaking corp). These groups are no strangers to high-stakes wormhole fights, frequently rolling connections and hunting content in C5 and similar class wormholes.
Opposing them was E.C.H.O., another active alliance with a history of clashing against LUPUS in wormhole space. The two sides had previously thrown down in armor brawls, including a notable engagement documented in 2025.
This fight was another chapter in their ongoing rivalry — but it didn’t stay a clean 1v1 for long.
The Heavy Armor Brawl
What started as a classic heavy armor brawl saw both fleets commit to close-range, high-tanking compositions. In wormhole space, these fights often feature battleships and T3 cruisers (Proteus, Legion, etc.) fitted for armor buffer or active reps, supported by Guardian or Oneiros logistics chains. Pilots manage capacitor, watch for neuts, and call targets while logi struggle to keep the front line alive under heavy fire.
Fleet comms (captured in the accompanying video) show intense coordination: rapid target calling, tackling, spooling weapons or modules, and managing rep chains as the two sides ground into each other. The brawl was in full swing by roughly the 2-minute mark of the video.
Third-Party Kite Fleet Crashes the Party
Then came the twist that defines so many J-space fights: a kitey third-party fleet arrived and began picking apart the engaged forces.
Kiting fleets excel at range control — using speed, long-range weapons (rails, artillery, or missiles), and mobility to avoid the brawl’s brutal close-range DPS while still applying damage. Once the two armor fleets were committed and relatively stationary (or slowed by tackle), the kiting force could dictate engagements, pick off damaged ships, or force the brawlers to break formation.
Video timestamps highlight the chaos:
• ~38:50 — Third-party kite fleet arrives and begins disrupting the fight.
• ~46:27 — RE-HO (Little Red Riding Hole) elements enter or escalate their involvement.
The result was a feeding frenzy. What began as a structured armor slugfest devolved into a multi-sided mess with wrecks everywhere. The kite fleet effectively “snuffed” many of the hulls that had been tanking each other moments earlier.
31 Billion ISK in Losses — “Annihilated for Bob”
Total destruction reached approximately 31 billion ISK. In wormhole culture, fights like this are often jokingly offered “for Bob” — a tongue-in-cheek reference to the semi-mythical RNG deity of wormhole space who supposedly controls hole spawns, mass limits, and the timing of third parties.
One Reddit post summarizing the fight captured the sentiment perfectly: “Wolves and ECHO duke it out with a heavy armor brawl; Only to get Ganked by a kitey fleet. 31 Billion isk annihilated for bob. Shame we didn’t loot the field…”
Many participating corporations run Ship Replacement Programs (SRP), which helped soften the blow for line members. Still, losing that much value in a single fight stings — especially when a third party walks away with the glory (and potentially some loot).
Watch the Fight: Fleet POV Video
Content creator Khagah uploaded an excellent 1-hour+ POV video of the engagement on June 17, 2026:
Video: Hufflepuff Watch these Hulls Get Snuffed - 31 Billion Isk Blown up - EVE Online PVP
The video includes clear fleet comms, tactical decisions under pressure, and the exact moment the third party arrives. It’s a great watch for anyone wanting to see how these fights actually play out from inside the fleet — the stress of logi reps, the sudden “oh shit” when the kiting force appears, and the rapid adaptation required.
Key timestamps in the video:
• 00:00 – Intro
• 02:04 – Heavy armor brawl begins in earnest
• 38:50 – Third-party kite fleet arrives
• 46:27 – RE-HO elements join/escalate
• ~1:00:00 – Battle report discussion
Why This Fight Matters
In EVE Online’s wormhole space, there are no local chat warnings and no easy way to know who else is in system until they decloak or land on grid. Fights are opportunistic, often triggered by rolling holes, scouting, or simply being in the wrong place at the right time. A clean 1v1 brawl can instantly become a 2v1 or free-for-all.
This engagement perfectly illustrates that reality: two groups showed up for content, committed to a brutal close-range armor fight, and paid the price when a mobile third party exploited their positioning.
For Wolves Amongst Strangers and E.C.H.O., it’s another data point in a long-running rivalry. For the kite fleet, it was likely a highly profitable evening of opportunistic ganking. For everyone else watching the video or reading the battle report, it’s prime EVE content — tense comms, exploding hulls, and the ever-present risk that someone else is already watching from the shadows.
Full Battle Report: capsuleers.app/tools/battle-report/545f1060-8b37-4288-9a6a-a23430003f78
Video POV: youtu.be/IQhbFldwZpg
In New Eden, the only certainty is that if you bring a fleet to a fight, someone else might bring a better one — or at least a faster, longer-ranged one. Fly safe (or don’t), and keep rolling those holes. Bob is always watching