"CS2 ADR explained: what average damage per round really measures"

Bottom line: ADR — average damage per round — is the cleanest single measure of a CS2 player's output. Across 204,663 professional match performances in our data, the median is about 73, a strong game sits near 82, and an elite one clears 92. It tracks overall rating closely without the noise of kill/death ratio, which is why analysts reach for it first. Every figure here comes from the EsportsOdds CS2 data API.

What ADR actually is

ADR stands for average damage per round. It is exactly what it sounds like: the total damage a player deals across a map, divided by the number of rounds played.

Because a kill in Counter-Strike requires 100 damage to a full-health opponent, ADR is closely tied to fragging — but it also rewards the chip damage that sets up a teammate's kill, the utility damage from an HE grenade or Molotov, and the shots that force an enemy to back off. A player who deals 80 damage to three different opponents in a round contributed a great deal to that round, even if they finished with zero kills. Kill/death ratio ignores all of it; ADR captures it.

That is the core reason ADR is more stable than K/D. Kills are lumpy — a single multi-kill round swings a K/D noticeably — whereas damage accumulates in smaller increments across every round, so it converges on a player's true output faster.

What counts as a good ADR

Here is the actual distribution of ADR across 204,663 professional CS2 match performances (aggregated per player, per match) in our dataset. It is close to a normal curve centred on a median of roughly 73.

The benchmarks that fall out of that distribution:

So when a broadcast talent says a player "had a huge game," they usually mean an ADR up around 90 or beyond. A player sitting at 60 across a series is having a rough time by professional standards, even if their kill count looks respectable off a couple of lucky rounds.

One caveat worth stating: these numbers are for professional Counter-Strike. Matchmaking and lower-tier ADR distributions look different — less consistent, wider spread — because the skill gap between players in a single game is far larger. The benchmarks above describe the pro game, not your own ranked matches.

ADR tracks rating almost linearly

The reason ADR is trusted as a shorthand for impact is that it correlates tightly with overall player rating. Group every performance by its rating band and average the ADR in each, and the relationship is almost a straight line:

A 0.6-rated performance averages about 55 ADR; a 1.0 (an average game) sits near 71; a 1.4 (an elite game) clears 81. There is no band where higher rating does not mean higher damage. That is what makes ADR a good "first look" number: you can glance at it and know roughly how a player performed before you open the full rating breakdown.

It is not a complete picture — a lurker who deals steady damage but wins fewer duels outright, or an entry fragger who trades their life for space, can have similar ADR but very different value to a team. That context is what KAST and the newer Round Swing metrics add. But as a single number, ADR is hard to beat.

ADR vs KDA: why analysts prefer it

Three quick reasons ADR earns its place over the more familiar kill/death ratio:

• It counts damage, not just finishes. The player who softens two enemies for a teammate to clean up gets credit. K/D gives them nothing.
• It is less streaky. Damage accrues every round; kills arrive in clusters. Over a Bo3, ADR settles closer to a player's real level.
• It resists farming. Padding kills in a lost round barely moves ADR, because the damage was already likely to be there. A player can't inflate ADR the way they can inflate a K/D on exit frags.

None of this means K/D is useless — it answers a different question (did you win your duels?). But if you can only look at one output number, ADR is the more honest one.

Getting ADR from the API

Every player's per-map and per-match ADR is available through the EsportsOdds CS2 data API, alongside kills, deaths, assists, KAST, headshots, opening duels and the rest of the box score. A match's player-stats payload returns ADR as a plain number per player, so building a leaderboard, a form chart, or a fantasy projection is a single request — no HTML scraping, no parsing a stats site's markup.

That is the whole point of the product: the CS2 match, player, team and tournament data that sites like HLTV display, delivered as clean JSON on a flat $99/month plan, so you can compute these benchmarks yourself instead of eyeballing them.

Frequently asked questions

What is a good ADR in CS2?

For professional play, an ADR around 80 is a strong game and 90+ is elite. The median pro performance sits near 73 in our data. In ranked matchmaking the bar is lower and far more variable, so these pro benchmarks don't map directly onto a Premier or matchmaking game.

How is ADR calculated?

Total damage dealt divided by rounds played. Because 100 damage kills a full-health opponent, ADR is closely linked to fragging, but it also credits partial damage that doesn't result in a kill — which is exactly why it's a fuller picture than kills alone.

Is ADR better than K/D ratio?

For measuring output, generally yes: ADR counts damage that sets up kills, is less streaky across a series, and is harder to inflate. K/D still answers a useful, different question — whether you win your duels. Analysts use both.

What's the difference between ADR and rating?

ADR is a single raw output stat (damage per round). Rating — such as HLTV Rating 3.0 — is a composite that blends ADR with survival, KAST, multi-kills and round context into one number. ADR is one of the ingredients of rating.

Where can I get CS2 ADR data programmatically?

Through the EsportsOdds CS2 data API: per-map and per-match player statistics, including ADR, as JSON. It's a flat $99/month plan with a 7-day trial.