KDA Is Lying to You: What Kill/Death/Assist Ratio Really Means in Competitive LoL

KDA is the first stat everyone checks after a game. It's clean, it's simple, and it feels like it tells the whole story. A player with a 5.0 KDA must be carrying. A player with a 1.2 KDA must be inting. Right?

Not even close.

KDA is one of the most misleading stats in competitive League of Legends — not because it's wrong, but because it rewards the wrong behavior when read in isolation. A high KDA can mean a player is carrying. It can also mean they're playing safe, avoiding every fight that looks risky, and padding their stats while their team bleeds out 4v5.

If you're coaching a team and KDA is your primary evaluation metric, you're getting played by the numbers.

What KDA actually measures

KDA stands for (Kills + Assists) / Deaths. If a player has 0 deaths, most tools treat it as 1 to avoid dividing by zero — which already tells you something about the formula's fragility.

Here's what a high KDA really tells you:

• The player didn't die much — that's it, primarily. Low deaths drive KDA up faster than high kills or assists.
• They were involved in successful fights — kills and assists both count, so a player who shows up after the fight is won still gets credit.
• They might be risk-averse — the easiest way to have a high KDA is to avoid risky plays entirely. No flanks, no engages, no split-push pressure.

And here's what KDA does not tell you:

• Whether the player created advantages or just collected them
• Whether their deaths were meaningless or productive (dying to secure Baron is not the same as dying to a face-check)
• Whether they applied pressure that doesn't show up in the kill feed — wave control, vision, zoning
• Whether they actually did damage proportional to their gold

KDA is a survival stat dressed up as a performance stat. And that distinction matters for coaching.

The KDA padding problem

Every competitive team has seen it: the player who finishes 3/1/7 and looks great on paper, but contributed almost nothing to the team's actual win condition.

KDA padding looks like this:

• Joining fights late — arriving after the outcome is decided, picking up assists or cleanup kills without taking any risk
• Refusing to engage — playing front-to-back every fight even when the team needs a flank or a dive
• Avoiding side lanes — staying grouped to collect assists instead of applying split pressure, which would mean fewer kills/assists and more risk of getting caught
• Holding ultimates — saving high-impact abilities for "the right moment" that never comes, because using them means committing

The result? A great KDA, low damage/min, low kill participation in the fights that actually mattered, and a team that lost despite one player's "perfect" scoreline.

This is why KDA should never be read alone. It needs context.

How to actually read KDA — the metrics that give it meaning

KDA becomes useful when you pair it with other numbers. Here's the framework:

KDA + Damage per minute

This is the most revealing combination.

A player with a 2.5 KDA and high damage/min is probably more valuable than a player with a 5.0 KDA and low damage/min. The first player is in the fight. The second player is watching it.

KDA + Kill participation

Kill participation (KP) measures what percentage of the team's kills a player was involved in. High KDA with low KP means the player is cherry-picking fights — only joining when it's safe.

• KP above 60% with solid KDA — team player, consistently involved
• KP below 40% with high KDA — red flag. Where are they during the fights they skip?
• KP above 70% with low KDA — they're in every fight but dying a lot. Check if they're the engage player — that's expected for certain roles.

KDA + Gold efficiency (DMG/Gold)

Some players farm well (high gold/min) and have decent KDA but convert gold into damage poorly. The damage-to-gold ratio tells you if they're building correctly and positioning to actually deal damage.

A player with high KDA, high CS/min, but low DMG/Gold is collecting resources and wasting them. That's a coaching conversation about itemization and teamfight positioning — not a pat on the back for a clean scoreline.

KDA benchmarks by role — and why they're misleading

Unlike CS/min, KDA benchmarks are dangerous because the "right" KDA depends entirely on how the player's role is supposed to function. But here's a rough reference for competitive and high-elo play:

ADC

ADCs should have higher KDAs because their job is sustained damage from a safe position. A low-KDA ADC is either mispositioning or getting no peel. A very high-KDA ADC who isn't dealing top damage might be playing too far back.

Mid lane

Mid lane KDA varies wildly by champion. An assassin should have a more volatile KDA (high kills, some deaths from aggressive plays). A control mage should trend higher. Compare within champion class, not across them.

Top lane

Top laners naturally have lower KDAs — the island effect means fewer assists, and many top lane champions require committing fully to fights. A Kennen who flashes into 5 and dies but wins the teamfight had a "bad" KDA moment that won the game.

Jungle

Junglers should have high kill participation but their KDA depends heavily on style. An aggressive early-game jungler will have more deaths from invades and dives. A farming jungler will look cleaner statistically. Neither is inherently better — it depends on what the team needs.

Support

Support KDA is the most role-dependent. Engage supports (Nautilus, Leona) will die more because their job is to start fights. Enchanter supports (Lulu, Janna) should have higher KDAs because they operate from the backline. Compare within champion archetype or the numbers are meaningless.

The deaths that don't show up in KDA

Not all deaths are equal, but KDA treats them that way. This is its biggest flaw.

Deaths that are worth it:

• Dying to secure Baron or Dragon soul
• Trading 1-for-1 when the enemy's death is worth more (shutting down a fed carry, killing a key player before an objective)
• Dying as the engage to win a 4-for-1 teamfight
• Getting caught while split-pushing but forcing 2+ enemies to respond, giving your team a numbers advantage elsewhere

Deaths that aren't:

• Face-checking without vision
• Getting caught farming a side wave with no wards
• Dying in a fight your team already lost (arriving late to a 3v5)
• Greeding for a kill under tower and trading 1-for-1 when you're the fed member

A good coach doesn't just look at how many times a player died — they ask which deaths were productive. KDA can't make that distinction. You need VOD review for that.

SoloQ KDA vs. Scrim KDA — the context shift

The same player can have very different KDAs in SoloQ versus scrims, and both tell you different things:

SoloQ KDA significantly higher than scrim KDA? Normal and expected for most players. SoloQ opponents are less coordinated, so it's easier to get kills and avoid deaths. But if the gap is massive (e.g., 4.5 SoloQ vs 2.0 scrim), the player might be struggling to adapt their playstyle to coordinated play. They take risks in SoloQ that get punished in scrims.

Scrim KDA higher than SoloQ? Less common but not unusual. Some players perform better with team coordination — they get more peel, better engages, and more structured teamfights. It can also mean they're autopiloting in SoloQ and taking unnecessary risks because "it's just SoloQ."

Both similar? Consistent player who doesn't change their approach based on the environment. Cross-reference with damage/min to make sure they're not just consistently passive in both.

How to act on KDA data as a coach

High KDA, low impact

This is the most common coaching blind spot. The player looks great on paper but the team keeps losing.

1. Pull damage/min — if it's low relative to their role and gold income, they're playing too safe.
2. Check kill participation — if it's below 50%, they're absent from too many fights.
3. Watch 2-3 teamfight VODs — look for where they're positioned. Are they in range to deal damage? Are they holding cooldowns too long?
4. Have the conversation — frame it around team needs, not individual stats. "We need more damage in fights" is better than "your KDA is fake."

Low KDA, high impact

Sometimes your most impactful player has the worst KDA. This is common for engage players and aggressive junglers.

1. Check if the deaths are productive — are they dying to start winning fights, or dying for nothing?
2. Look at the team's win rate in their games — if the team wins despite the player's low KDA, the deaths might be worth it.
3. Monitor the trend — a slight downward KDA trend with stable win rate is fine. A downward KDA trend with a declining win rate means something changed.

KDA suddenly dropping

A sudden KDA drop (more than 1.0 over 7 days) needs investigation, not a verdict:

• New champion picks — unfamiliar kits lead to bad positioning and more deaths
• Role change or meta shift — different role expectations change KDA baselines
• Tilt or burnout — risky plays increase when a player is frustrated
• Opponent quality change — ranking up means facing better players who punish harder

KDA differences between teammates

Comparing KDA between players in different roles is pointless. But comparing KDA trends across the same role (e.g., if you have two mid laners in your roster) can reveal who's adapting better to the current meta or matchups.

The metric that matters more than KDA

If you had to pick one stat to evaluate a player's actual contribution, it's not KDA — it's damage per minute relative to gold per minute (the DMG/Gold ratio).

This tells you: for every gold coin this player earns, how much damage are they putting out?

A player with lower KDA but higher damage efficiency is doing more with less. They're in the fight, they're hitting targets, and they're converting resources into pressure. That's what wins games — not a clean scoreline.

KDA can stay in your dashboard. But it should never sit there alone.

Stop reading KDA in isolation

KDA is not a bad stat. It's a bad stat to use by itself. The moment you pair it with damage/min, kill participation, and gold efficiency, it becomes one piece of a much clearer picture.

With VictoryView, every player's KDA sits next to their CS/min, damage/min, gold/min, and vision score — all filterable by queue type and time window. You don't have to open five tabs and piece the story together manually. The full picture is already there.

Import your team's matches, filter by the last 7 days, and check: is your highest-KDA player actually your highest-impact player? The answer might surprise you.