Skip to content
Calc.

K/D Ratio Calculator

K/D ratio (kill/death ratio) = kills ÷ deaths. Enter your kills and deaths to get your kill death ratio: 150 kills and 75 deaths is a K/D of 2.00, two kills for every death; 1.00 means you kill as often as you die, under 1.00 you die more often than you kill.

Last updated: September 2026

K/D Ratio

2

Formula below · 1 source (hltv.org) · Updated Sep 2026

Compare with similar

About this calculator

K/D ratio formula: K/D = kills ÷ deaths. K/D (or KDR, kill/death ratio) is the number of opponents you eliminate for each time you are eliminated. It is a unitless ratio: 1.0 means one kill per death (break-even), 2.0 means twice as many kills as deaths, 0.5 means twice as many deaths as kills.

Worked example: 150 kills and 75 deaths → 150 ÷ 75 = 2.00. 47 kills and 20 deaths → 2.35. The calculator rounds to two decimals. With zero deaths the ratio is undefined, so the calculator shows the kill count (10 kills, 0 deaths → 10), the convention most game stat screens use; 0 kills and 0 deaths gives 0.

Why 1.0 is the average: in a mode where every kill is another player's death (team deathmatch, free-for-all), total kills and total deaths across a lobby are roughly equal, so the average K/D is close to 1.0 — a little below if falls, self-damage or the environment cause deaths no player gets credit for. Above 1.0 means you are out-trading the average player you meet; how much above is "good" depends on the game, mode and matchmaking, so the most useful comparison is your own trend over many matches.

K/D depends on playstyle and mode. In objective modes (Domination, Search and Destroy, Capture the Flag) a 1.0 player who holds the objective can help the team more than a 2.0 player who stays on the edges. Many games add other measures: KDA = (kills + assists) ÷ deaths is standard in MOBAs such as League of Legends and Dota 2, and Counter-Strike analysts use KAST (rounds with a kill, assist, survival or trade) and HLTV's composite Rating.

Common K/D ratios (kills ÷ deaths)

Scroll sideways to see all columns →

KillsDeathsK/D ratioMeaning
10200.502 deaths per kill
15200.753 kills per 4 deaths
20201.00Break-even
25201.255 kills per 4 deaths
30201.503 kills per 2 deaths
40202.002 kills per death
60203.003 kills per death

How to use

Enter your total kills and total deaths from a match, a session or your career stats screen. Example 1 — session review. 87 kills and 71 deaths over five matches: 87 ÷ 71 = 1.23, so you get about 1.23 kills for every death, slightly better than break-even. Example 2 — one ranked game. 22 kills and 9 deaths: 22 ÷ 9 = 2.44. Single-game K/Ds swing a lot; a season's total kills ÷ total deaths is the more reliable figure. How many kills to raise your K/D? To reach a target K/D, you need target × deaths kills in total. With 87 kills and 71 deaths, a 1.50 K/D needs 1.5 × 71 = 106.5, so about 20 more kills without dying.

Frequently asked questions

What is a good K/D ratio?

Above 1.0 is better than break-even, because in kill-for-death modes the average player across a lobby sits close to 1.0. Beyond that it depends on the game, mode and matchmaking: skill-based matchmaking pairs you with similar players, which tends to pull K/D towards 1.0 as you improve, and objective modes reward play that K/D does not count. A K/D of 1.5 means three kills for every two deaths and 2.0 two kills per death; treat these as personal milestones rather than universal ranks. The most meaningful benchmark is your own trend: going from 0.9 to 1.2 over several months is real improvement.

Is K/D more important than win rate?

Depends on your goal. If you want to maximize personal stats and clip-worthy plays, K/D matters most. If you want to climb ranked ladders and improve as a teammate, win rate matters more — the ladder rewards wins, not frags. Many high-K/D players have mediocre win rates because they prioritize personal gameplay (peeking for picks, chasing kills) over team-positive plays (trading, holding angles, supporting objectives). Conversely, players with modest K/D but high win rate often have strong fundamentals (good positioning, smart trades, voice communication, decisive callouts) that lift team performance even when their personal stats don't shine. For competitive growth, both metrics together (high K/D AND high win rate) indicate elite skill; one without the other suggests focused gameplay style with specific tradeoffs. Pro analytics (HLTV ratings for CS, prox-stats in Valorant) blend many metrics including K/D, KAST, ADR, and clutch stats into composite scores that better reflect actual game impact.

What is KDA and how is it different from K/D?

KDA = (kills + assists) ÷ deaths. It's the dominant performance metric in MOBAs (League of Legends, Dota 2, SMITE) because supporting champions and roles contribute massive team value through assists rather than killing blows. A support champion with 2 kills, 25 assists, and 4 deaths has a 0.5 K/D (looks terrible) but a 6.75 KDA (looks great). KDA better captures the team-play contribution in roles where setting up kills matters more than securing them. Some competitive shooters now report KDA-style metrics — Apex Legends shows kills/assists, Valorant shows "first blood" and "clutches" alongside K/D. KDA isn't directly meaningful in CS:GO/CS2 because assist tracking is less central to scoring. The right metric depends on game design and your role within it — be skeptical of cross-game comparisons since the same number can have very different meanings.

What are the most common mistakes people make optimizing K/D?

The biggest is playing too passively to protect K/D — avoiding fights to avoid deaths often loses games. The second is judging from too small a sample: single-game K/D varies wildly with teammates, opponents and luck, while totals over hundreds of matches are stable. The third is comparing across modes (Hardcore against Core, Domination against Search and Destroy) or across different games, where the pace and number of fights per life differ. The fourth is chasing K/D in ranked at the expense of the objective; rank rewards wins, not kills. The fifth is padding K/D in easy lobbies, which does not carry over to games against equal opponents. Track K/D as a trend alongside win rate.

When should I not use K/D as a performance measure?

Skip it as the main measure in MOBAs (League of Legends, Dota 2, Smite) — use KDA, gold per minute and vision score instead. It also undersells support and tank roles in any game, whose value is not in kills, and objective modes (Domination, Hardpoint, Search and Destroy, Battlefield Conquest), where captures, holds and plants matter more. In battle royale games, placement and damage per match matter as much as kills. In Counter-Strike, analysts prefer HLTV's composite Rating (version 3.0 since August 2025, built from kills, damage, survival, KAST, multi-kills and round swing) to raw K/D. And for casual play, remember the point is to enjoy the game.

Related calculators

Sources & references

How we check our calculators

Think a result is wrong? Report a problem with this calculator.