Vedmak Loss in DR-427 Ends a Fraternity Skirmish at a Cost

A Fraternity Vedmak was destroyed in DR-427 after Out of the Blue. caught the cruiser in a compact but costly skirmish that drew 28 pilots into the fight. The ship’s 1.1 billion ISK value made the loss stand out immediately, even before the field was over and the wreckage was counted.

THE CATCH

The engagement appears to have opened with Out of the Blue. finding a valuable Fraternity cruiser exposed in DR-427. What followed was not a prolonged siege but a fast, concentrated exchange that put the Vedmak under immediate pressure. With 23 attackers credited on the final blow report and 28 pilots involved overall, the fight suggests a sudden local clash rather than a clean one-on-one hunt.

THE COLLAPSE

The Vedmak did not survive the contact. It was destroyed with 263.3 million ISK lost outright and 874.2 million ISK recovered by the attackers, a sign that the ship’s fit and cargo made this a particularly expensive casualty. The presence of Sabres, Drake Navy Issues, and Cyclone Fleet Issues among the attackers points to a force that was ready to hold a target in place and keep it there long enough for the damage to land.

THE PRIZE

The victim, wood Colored of Fraternity. and Chaos arbiter, lost more than a cruiser hull here. The damage report shows stacks of exotic plasma ammunition destroyed or dropped in the wreck, reinforcing the sense of a combat-ready ship caught before it could disengage. For Out of the Blue., the result was a clean and visibly profitable catch rather than a routine trade of fire.

WHY IT MATTERS

Single-ship losses of this scale tend to resonate beyond the system where they occur. A Vedmak worth 1.1 billion ISK is the kind of target that changes the tone of a roaming engagement, especially when it falls quickly under coordinated fire. In DR-427, the fight appears to have ended with Out of the Blue. controlling the field and Fraternity. absorbing a sharp and memorable loss.

Sources and verification

Based on recorded combat data Narrative based on recorded New Eden activity and archived editorial analysis.

Permalink

CONTINUE EXPLORING

More Stories From New Eden

View all stories →

Nullsec

ChuangShi Parked 234 Ships in P-ZMZV. Can't park there m8 Noticed.

The first confirmed loss in P-ZMZV wasn't a ship. At 13:49 the opening entry on the killboard is a capsule - a pilot's escape pod, logged and destroyed. The last entry, some two and a half hours later, is an Osprey Navy Issue flown for Black Layer Syndicate. In between, the system swallowed 581 losses and roughly 1.77 trillion ISK, and when the shooting finally stopped, one side was still out there sweeping the grid for pods.

Highsec

Rattini Tribe Topped Amamake's Kills and Its Losses

At 22:01 UTC the first wreck of the night was a Slasher, a frigate so cheap it barely registers as a rounding error in a system like Amamake. Nearly four hours later, at 01:59, a Hecate stopped burning and the shooting finally trailed off. In between, Heimatar's most notorious lowsec system swallowed a Titan, a supercarrier, thirty-three capitals and somewhere in the region of 12.2 trillion ISK of everything else. The final tally: 1,705 ships destroyed, roughly 44,900 pilots credited across the killmails, and one alliance sitting proudly at the top of both the kill column and the loss column.

Nullsec

Evermore Warriors Lose Ten as Eight Capitals Melt in Fifteen Minutes

At 02:06 UTC a Hurricane exploded in V2-GZS. Fourteen minutes later the last loss on the board was a capsule belonging to a Hounds of War. pilot, and the Kalevala Expanse had eight fewer capitals in it than it did a quarter of an hour earlier.

Pochven

Big Vantus Paid 15 Ships Toward Pochven's 72 Billion ISK Tab

Of the 47 ships destroyed in Ignebaener, 46 were, in ISK terms, background noise. The 47th was a Paladin valued at just under 57.5 billion ISK - close to four-fifths of everything the system destroyed in one sitting. One hull, one pilot, one very bad moment, and the number that will define this fight long after the killboards stop updating.