BDO Node War Stats Explained: How to Read Your War Results Screen

When a node war ends in Black Desert Online, the game hands you a results panel with eleven combat stats — and most players read exactly one of them. Kills. Maybe deaths, if the night went badly. Then the screen closes and the richest snapshot of your performance all week disappears with it.

That's a waste, because the results screen is the closest thing BDO gives you to game film. It records not just whether you got kills, but whether you created them, absorbed pressure so someone else could, kept your group standing, or spent a quarter of the war running back from the respawn point. This guide goes through every stat on the screen — what it actually measures, who should be high on it, and how officers read the combinations.

New to node wars entirely? Start with our Node Wars explainer first — this post assumes you've fought in at least one.

Where the results screen comes from

The panel appears when the war ends, and it's personal — each player sees their own line of stats for the night. It's also ephemeral: there's no in-game history to scroll back through later. That's why organized guilds ask everyone to screenshot their results before closing, and why officers collect those screenshots after every war — it's the only record that the night ever happened.

Eleven stats appear on it. Here's the tour, grouped by what they actually tell you.

The scoreboard stats: Kills, Deaths, Best Streak

Kills

The number of enemy players you landed the finishing blow on. It's the stat everyone reads first and the one that needs the most context. Kills cluster on burst classes and backline damage dealers by design — a grab class can set up five kills and receive credit for none of them. High kills are good; low kills are not automatically bad.

Deaths

How many times you died. Like kills, raw deaths mislead without role context: a frontline engager whose job is to dive the enemy backline will die more than a ranged player standing behind three barricades. What matters is whether your deaths bought something — an opening, a peeled healer, a broken flank — or whether they were free gifts to the enemy scoreboard. Kills divided by deaths gives you K/D, which earns enough arguments that we gave it its own benchmarks post.

Best Streak

Your longest run of kills without dying. It's a momentum-and-positioning signal more than a skill stat: long streaks mean you were picking the right fights and leaving before the fight picked you. A player with 20 kills and a best streak of 2 played a very different war than a player with 20 kills and a streak of 11.

The pressure stats: Damage Dealt, Damage Taken

Damage Dealt to Players

Total damage you did to enemy players over the whole war. This is the workhorse metric — it doesn't care who got the killing blow, so it credits sustained pressure that kills never capture. Two things to remember when reading it:

• It scales with war size and length. 40 million damage in a 20-person skirmish and 40 million in a 90-person T3 slugfest are completely different performances. The honest way to read damage is as a share of your guild's total — in a 25-player roster, an average member accounts for 4% of the guild's damage; doing 8% means you pulled double weight.
• It's a DPS-class stat. Supports, shot-callers, and objective players will always look weak here. That's not underperformance — that's specialization.

Damage Taken

Total damage enemies did to you. Counter-intuitively, high damage taken is often a positive signal: it means you were in the fight, holding space, soaking attention that would otherwise land on your squishier teammates. Frontliners and engage classes should be near the top. The bad version of this stat is high damage taken plus high deaths plus low everything else — that's not tanking, that's feeding. The suspicious version is a melee class with very low damage taken: it usually means they never actually committed to a fight.

The playmaker stat: CC Count

CC Count is the number of crowd-control effects you successfully landed — stuns, knockdowns, floats, grabs. In coordinated wars this may be the most underrated number on the entire screen. BDO team fights are decided by CC chains: a landed grab turns an enemy from a threat into a corpse-in-waiting, and the damage dealers who finish them get the kill credit while the CC player gets a +1 on this quiet little counter.

When an officer sees a player with modest kills, modest damage, and a towering CC count, they're not looking at a passenger — they're looking at the person who was opening every door the rest of the guild walked through. Tamers, Strikers, Mystics, and other engage-heavy classes live and die by this stat.

The sustain stats: Self-Healing, Ally Healing

Self-Healing

Health you recovered on your own character — potions, lifesteal, your own recovery skills. Read alongside damage taken, it describes your durability loop: a bruiser with big numbers in both took enormous punishment and survived it. It's rarely a stat anyone optimizes for directly, but it explains how some players post low death counts while living on the frontline.

Ally Healing

Health your skills restored to other guild members. This is the support stat, full stop. A dedicated support build will post ally-healing numbers several times higher than anyone else in the war — and usually bottom-tier damage, because every second spent healing is a second not spent attacking. This is the clearest case in the whole panel of a stat that means nothing for most of the roster and everything for a few players: judge your supports here, not on the damage column. A support with big ally healing won your fights just as surely as the damage dealer who topped the kill list.

The objective stat: Fort Damage

Damage you dealt to objectives — forts, command posts, and defensive structures — rather than players. Node wars are won by killing the enemy's structures, and somebody has to actually hit them while everyone else brawls. Cannon crews, siege-focused players, and whoever was assigned to backdoor the enemy fort will show huge fort damage next to unremarkable player damage. If your guild won the war and your fort damage carried the guild's total, you can ignore every other column on the screen with a clear conscience.

The honest stats: Time Dead, Time Alive

Time Dead is the total time you spent dead or returning to the fight; Time Alive is the inverse. Many officers consider time dead the most honest stat on the screen, for one simple reason: it can't be padded. Kills can be stolen, damage can be farmed on tanky targets that never die, but every minute of time dead is a minute your guild fought with one fewer player. Two members with identical K/D can differ by ten minutes of time dead — and that difference is the difference between them.

High time dead usually decomposes into one of three problems: dying at bad moments (deaths early in each fight), slow respawn discipline (alt-tabbing at the respawn point), or long walks back because you died far from the action. All three are fixable once you know which one it is — which is exactly why this stat rewards attention.

The whole screen at a glance

So what's a "good" number?

There isn't one — and that's the most important thing this screen can teach you. Three pieces of context change what every number means:

1. War size. Raw totals scale with how many players were fighting and for how long. The fix is thinking in shares: in a war where your guild fielded 25, the average member is 4% of every guild total. Beat your fair share and you pulled more than your weight — at any war size.
2. Your role. Every stat on the screen is somebody's job and somebody else's noise. A support's damage, a cannon crew's kills, and a backliner's damage taken are all equally meaningless. Compare players against their own class and role, or don't compare at all.
3. The night itself. A brutal loss against a stronger guild compresses everyone's numbers; a stomp inflates them. One war is an anecdote — the signal lives in trends across weeks.

Reading combinations like an officer

Experienced officers don't read stats in isolation — they read patterns across columns:

• Low kills + high CC count — a playmaker. This player creates the kills the scoreboard credits to others.
• High damage taken + low deaths + high self-healing — a real frontliner. Absorbing that much and surviving it is a skill.
• High kills + low damage dealt — a finisher. They're last-hitting fights other people won. Fine in moderation; a red flag in a player who claims to carry.
• Huge ally healing + nothing else — a support doing exactly their job. Never judge this line by any other column.
• Decent K/D + enormous time dead — the invisible problem. They win their fights, then spend eight minutes of the war walking back.
• Everything mediocre, every single week — the actual coaching case. One quiet night is noise; a quiet month is a conversation.

That last line is the catch: none of these reads work from a single screenshot. The screen shows one night. Roles, trends, and fair-share math only emerge when someone records the numbers war after war — which is why serious guilds log every results screen, whether in a spreadsheet or a tool like CritIQ (full disclosure: we make CritIQ) that reads the screenshots automatically and tracks every one of these eleven stats per member, per war, with class-aware standards. However you do it: the screen is only game film if somebody keeps the film.

Frequently asked questions

Where do I see my node war stats in BDO?

When a node war ends, BDO shows a personal war results panel listing your combat stats for the night — kills, deaths, best streak, damage dealt to players, damage taken, CC count, self-healing, ally healing, fort damage, time dead, and time alive. It only appears at the end of the war, so most guilds screenshot it before closing — once it's gone, it's gone.

What does CC Count mean in BDO node wars?

CC Count is the number of crowd-control effects you successfully landed on enemy players — stuns, knockdowns, floats, grabs, and the rest. In organized wars it's one of the most telling stats on the screen: a landed CC is what turns an enemy into a free kill for your damage dealers, so a high CC count usually marks the players creating openings, not just finishing them.

What is a good K/D in a node war?

It depends entirely on your role and the war. A backline damage dealer might sit at 2.0+ in a war their guild dominated, while a frontline engager doing their job perfectly can finish below 1.0 because their job is to eat the enemy's attention. Supports and shot-callers routinely have unimpressive K/D in wars they carried. Compare against your guild's average for that same war, and against players in the same role — not against a universal number.

What's the difference between Damage Dealt and Fort Damage?

Damage Dealt to Players counts only damage you did to enemy players. Fort Damage counts damage to objectives — forts, command posts, and defensive structures. A player can top one list and be near zero on the other; siege-focused players and cannon crews often show modest player damage but huge fort damage, which is exactly what the guild asked them to do.

What's the difference between Self-Healing and Ally Healing?

Self-Healing is health you recovered on your own character — potions, lifesteal, and your own skills. Ally Healing is health your skills restored to other guild members, and it's effectively the support stat: dedicated healer builds produce ally-healing numbers many times higher than anyone else in the war. Judging those players by damage instead of ally healing misses their entire contribution.

Do Time Dead and Time Alive matter?

More than most players think. Time Dead is the total time you spent dead or running back during the war — every minute of it is a minute your guild fought a player down. Two players with identical K/D can have wildly different time-dead numbers, and the one who dies at bad moments and respawns slowly contributed far less. Many officers consider time dead the most honest stat on the screen because it can't be padded.

The bigger picture

The results screen exists because node wars are a team sport pretending to have an individual scoreboard. Read naively, it crowns whoever plays the flashiest class. Read well, it shows you the engager who opened every fight, the support who kept the ball rolling, the siege player who actually ended the war, and the honest cost of every death. Learn to read all eleven columns and you'll never look at "I went 12-3" the same way again — and if you're the one collecting those screens for your guild, our posts on Node Wars and Sieges cover the systems all these numbers come from.