Tools / Nullsec

MERCENARY DEN

Where Mercenary Dens die in nullsec, who hunts them and where to anchor one, from our killmail archive.

A den anchors within 10 km of the skyhook of a temperate planet in nullsec. Skyhooks are not public: here are all the planets that can host one, with the risk measured on killmails.

Possible planets2,443in 1 region

No dens lost nearby0none in the system or one jump away · 30 d

Workforce7,510 – 10,200670 planets where a den has already died

2 planets

Sort

Planet	Sovereignty	Workforce	Dens lost here	Risk · 30 d	Jumps from Zarzakh	Actions
F4R2-Q VII -0.2 · Catch	Sigma Grindset	8,170	6 5 h ago	High8 here · 3 one jump away	14
F4R2-Q VIII -0.2 · Catch	Sigma Grindset	7,530	4 5 h ago	High8 here · 3 one jump away	14

EVE Online Mercenary Dens

Every Mercenary Den destroyed in nullsec, who hunts them and who loses them, the temperate planets where a den is safest, and your own dens with reinforcement, anarchy and MTO timers.

Mercenary Dens are not public: no API lists who owns one or where it sits.

What is public is the moment one dies, because the killmail records the den, the planet it orbited, the infomorph keys left in the wreck and everyone who shot it.

This page reads those killmails from our own archive and turns them into three answers: where dens are falling right now and who is doing it, which temperate planets are the quiet ones to anchor on, and, with your EVE login, the state of every den you own.

What a Mercenary Den is

A Mercenary Den is a Deathless Circle deployable that anchors within 10 km of the Orbital Skyhook of a temperate planet in sovereignty nullsec. It slowly fills with Infomorph Decryption Keys, which are sold on the market or traded with the Deathless in Zarzakh.

Each level of the Mercenary Den Management skill lets a pilot run one den, up to five. A den has two values that move over time: development, which raises the key output, and anarchy, which at level 2 starts draining workforce from the skyhook it sits on.

Who kills dens, and why it matters

Every den kill is sorted into one of three classes, comparing the attackers with the den owner's alliance and with the alliance that holds the system today:

Raid: neither the owner's alliance nor the system holder took part
Landlord: the alliance holding the system cleared its own skyhook
Own alliance: the owner or their own alliance removed it

Choosing a planet to anchor on

The planner lists every temperate planet with workforce in nullsec, about 2,400 of them, with the alliance that holds the system, the workforce of the planet and a risk measured on real kills: dens destroyed in the same system and one jump away in the last 30 days, where those in the system count three times.

A planet where a den has already died is proof that a skyhook was there. Skyhooks themselves are not public, so for any other planet ask the system holder before you bring a den.

Keeping your dens alive

With the Mercenary Den service enabled on your characters, the page reads every den you own and puts what needs you first: a den in reinforcement with the time it comes out, anarchy at level 2, an MTO about to expire, a den stopped because its pilot lost the skill.

A completed MTO adds 10 development, removes 20 anarchy and adds 350 keys.

When a den dies, roughly half of the keys inside are left in the wreck for whoever killed it, so emptying it often is the cheapest protection.

Frequently asked questions

Can I see where other players' Mercenary Dens are?

No. ESI only shows a den to its owner. This page shows where dens have been destroyed, on which planet and by whom, which is the closest public picture of where dens live and where hunters are active.

Why is the system holder killing dens in its own space?

Because a den with high anarchy drains workforce from the skyhook, and that workforce belongs to the alliance that holds the system. Clearing dens keeps the skyhook producing.

How often does the data update?

Den kills come from our killmail archive and are read again every five minutes. Your own dens come from ESI, which refreshes them about once an hour, while MTOs refresh every few minutes.

What permissions does My dens need?

Two ESI permissions in a dedicated service: character structures, for the dens, and character activities, for the MTOs. Enabling them does not change any service you already granted.