7 min read
KDA is the first number your eye lands on after a game.
It's the easiest stat to read — and the easiest to misread.
This guide covers how KDA is calculated, what a "good" KDA looks like, and why treating it as your main improvement metric will steer you wrong.
KDA is (kills + assists) ÷ deaths.
So an 8-kill, 3-death, 10-assist game is (8 + 10) ÷ 3 = 6.0.
With zero deaths you'd be dividing by zero, so most trackers treat deaths as 1 and label the result a "Perfect KDA."
The "8/3/10" you see on the scoreboard is the K/D/A breakdown; the KDA ratio just collapses those three numbers into one.
In solo queue, a KDA around 3.0 is a rough dividing line, and the average sits somewhere between 2.0 and 2.5.
The table below is a loose, all-roles-averaged reference — a feel, not a precise statistic.
| Rank | Rough KDA | Note |
|---|---|---|
| Iron–Bronze | 1.8–2.2 | Cutting deaths alone climbs here |
| Silver–Gold | 2.2–2.6 | Fight participation is the gap |
| Platinum / Emerald | 2.6–3.0 | Quality of deaths starts to matter |
| Diamond | 3.0–3.5 | Risk management is steady |
| Master+ | 3.5+ | But carry roles swing hard |
The catch: role affects KDA more than rank does.
Supports and junglers rack up assists without needing kills, so their KDA tends to run high.
Carries like ADC and mid take fights and initiate, so they die more — their KDA runs lower and more volatile at the same skill level.
Comparing a support's 4.0 to an ADC's 2.8 tells you nothing.
The useful read is whether your KDA is above or below normal for your role, at your rank.
KDA is an outcome, not a cause — a high number doesn't always mean you played well.
Stat-padding: cleaning up kills after teammates broke the enemy inflates KDA without you creating the win.
Playing too safe: farming all game for a 0-death line can still mean you contributed nothing to the win condition.
Assist inflation: tagging one spell from range counts as the same "1 assist" as committing to the fight.
In practice, CS/min, the gap to your opponent, and death timing correlate with rank more strongly than KDA does.
There's more on that in metrics that correlate with rank.
To make KDA useful, look behind the number rather than at it.
The highest-value lens is death timing: two-plus deaths inside eight minutes points at lane setup; deaths after 25 minutes in fights point at macro.
For how to read each stat, see how to read match stats; for role targets, see stat targets by rank.
Export a game as JSON with LoL2LLM and ask an AI to open up the number:
From this match data, tell me whether my KDA came from early CS difference, death timing, or fight participation — and what to fix first.
KDA is (kills + assists) divided by deaths. For example, 8 kills, 3 deaths, and 10 assists is (8 + 10) / 3 = 6.0. When deaths are 0, most trackers count deaths as 1 to avoid dividing by zero and label the result a Perfect KDA.
In solo queue a KDA around 3.0 is a rough dividing line and the average is about 2.0-2.5. As loose per-rank guidance: Silver-Gold around 2.2-2.6, Platinum/Emerald 2.6-3.0, and Diamond 3.0-3.5. But role affects KDA more than rank does, so treat these as context, not targets.
Yes. Supports and junglers accumulate assists and tend to post higher KDA, while carries like ADC and mid take more fights, die more, and run lower and more volatile KDA at the same skill level. Comparing KDA across different roles is not meaningful; compare within the same role and rank.
Not necessarily. KDA is an outcome, not a cause: it can be inflated by cleanup kills after teammates broke the enemy, or by farming safely for a 0-death game that contributed little. For improvement, CS/min, CS difference vs your opponent, and death timing correlate with rank more strongly than KDA.
Which numbers should a beginner actually aim for to climb in League of Legends? Realistic targets for CS/min, kill participation, vision score, deaths, and damage share by rank and role — and what to fix first.
Read the post-game scoreboard the way a coach would. Role-aware benchmarks, what each number actually measures, and how to combine them before handing the JSON to an AI.
Below Plat, the metrics that move with rank aren't KDA or win rate — they're five much quieter numbers. Improve them and the climb compounds.