EVE COMBAT INTEL

BATTLE REPORT

Tactical battle report for alliances and corporations, with multi-team support, mandatory system filter and up to 1-month time window.

Open the guide

BATTLE CONFIG TERMINAL

ONLINE

Import from another battle report

Paste the URL of a warbeacon.net or br.evetools.org report: systems, time windows and team split come from there. Killmails are not copied — our own compute reads them again.

INVOLVED SYSTEMS0

CURRENT EVE TIME—

At least one system is required. Add every system involved in the engagement.

No system selected — required to generate the report

TEAMS0

Configure teams manually OR use Auto-detect to seed them from the killmails. You can always refine the suggestion by moving entities between teams.

Configure at least one team before generating the report.

EVE Online Battle Report

Rebuild an EVE Online fight with as many teams as it had: per-system time windows, automatic side detection, damage and composition. Free.

The battle report on Capsuleers.app aggregates the killmails of an EVE Online battle at the alliance, corporation and system level. Unlike the fleet report (which starts from a pilot list), the battle report starts from the entities involved: add the alliances or corps that fought, pick the engagement's systems and an independent UTC time window for each one, so you never import noise from unrelated fights in the same system.

The tool supports N simultaneous teams: configure them manually for simple cases, or use auto-detect which inspects the killmails to suggest who fought whom based on co-attack and opposition patterns. You can always refine the suggestion by moving entities between teams.

The report is organized in tabs: Involved (pilot list per team grouped by alliance > corp), Summary (ISK, top lost hulls, top damage dealers, most active systems), Timeline (killmail cadence over time), Damage (per pilot, corp or alliance) and Composition (per-team hull breakdown). Every report has a unique shareable URL and a Refresh button that recomputes from source when eve-kill ingests late killmails. Editing the config produces a new URL: every share is an exact snapshot of the config.

Rebuilding a fight

A battle report here starts from where the fight happened rather than from a link someone sent you. Add every system involved, give each one its own UTC window, then build the teams and generate.

The report that comes out has five views. Involved lists every entity that appeared and which team it ended up on. Summary is the scoreboard: kills, losses and ISK per side. Timeline replays the engagement in order. Damage breaks down who did what. Composition shows what each side was flying.

Every report gets a shareable link, and the numbers are always recomputed from the configuration rather than trusted from whoever opens it, so a shared report cannot be doctored by editing the URL.

As many teams as the fight had

Most battle report tools assume two sides. Real fights in null and low are frequently three-way or worse: a third party lands on a contested grid, shoots whoever is weakest, and leaves. Folded into a two-sided report they distort both sides' numbers and the argument afterwards is about a number nobody trusts.

Here a team is just a named, coloured group of alliances and corporations, and you can have as many as you need. Entities are dragged between teams while you build, so correcting a misassignment is one gesture rather than a rerun.

Automatic side detection

You do not have to know the order of battle in advance. Given the systems and the window, the tool reads the killmails and proposes the teams itself.

It does this by building two relationships out of the data: who appeared on the same killmail as an attacker as whom, and who shot whom. Entities that consistently shoot alongside each other group together, entities that consistently shoot each other end up on opposite sides, and the groups are grown outwards from the strongest relationships.

The proposal is a starting point, not a verdict. It is usually right about the two main blocs and it is the part of setting up a report that takes longest by hand.

Time windows per system, not one global window

A single window across every system is the quickest way to poison a report. If a fight moved through three systems over ninety minutes, a window wide enough to cover all three will also sweep in every unrelated gate kill that happened in the first system during the other sixty.

Giving each system its own from and to keeps each stretch of the fight bounded by when it actually happened there. It is more work to set up and it is the difference between a report that matches what people remember and one that does not.

Starting from a report someone else made

Paste a warbeacon.net or br.evetools.org report URL and we read the systems and teams out of it and load them into the form. From there you can add the system the fight spilled into, tighten a window, or split a third party into its own team.

Any report can also be forked, which copies its configuration into a new one and leaves the original untouched.

Frequently asked questions

Do I need an account to generate a battle report?

No. The battle report builder works signed out, and so does every shared report link.

Why do the ISK numbers differ from other battle reports?

Because of what is counted, not because of a rounding error. We exclude NPC kills and structure padding from the totals, and a killmail's value is the one frozen at the moment of the kill rather than recalculated from today's market. Two tools that make different choices on those three points will disagree by a few percent on any large fight.

The report is missing a structure loss with no pilot on it.

Structures and deployables die without a pilot on the killmail, so there is nothing to assign them to directly. We attribute such a loss to the corporation's own pilot who died closest to it in time, within a thirty-minute window. It is a heuristic and it is the same one other battle report tools use.

Can I regenerate a report after the fight has been fully reported?

Yes. An existing report has a refresh button that recomputes it from the same configuration, which is worth doing an hour or so after a big fight since killmails keep arriving for a while. It is limited to once every five minutes per report.