Skip to content
FPSTracker
Metrics
REF / 7 FIGURES

Shooter Statistics Explained: What Each Metric Measures

Seven figures recur across every shooter profile, and every one of them omits something the reader assumes it contains. This page sets out what each measures, which system inside the game produces it, and what it leaves out.

Provenance

How a figure reaches the page

FIG / 01

No page measures anything. Four stages sit between an event in a match and a number on a screen, and each of the three boundaries between them removes something.

01 Match server Every event, complete and private
Removed here Anything not published: per-round context, whether a kill was a trade, the mode split most pages merge.
02 Publisher A chosen subset, privacy-gated
Removed here Anything behind a privacy setting, and anything the read happened to miss.
03 Third party One read, stored with a timestamp
Removed here The age of the reading. A figure an hour old and one a season old look identical on the page.
04 The page The cache, shown without its age

The third boundary is the one that causes most of the confusion, because the loss is invisible. A cached figure and a live one are rendered identically, so a rank read an hour ago and one read a season ago look the same. Where a page shows a last-updated time, it is the most useful thing on the page.

The first boundary produces the errors that survive longest. What the publisher declines to expose cannot be recovered by anyone downstream, which is why per-round context, trade information and the casual-versus-ranked split are absent from almost every figure in circulation; not because pages discard them, but because they were never published.

Table

The seven recurring figures

SHEET / 02
Each figure, the system that produces it, and the thing it quietly excludes.
Metric What it measures Where it comes from Why it is often wrong
K/D ratio How many opponents a player removes for every time they are removed. Match history, summed over whatever pool the page happens to be reading. It counts a trade the same as a solo pick, and it says nothing about when in the round the kill happened.
Win rate How often the player is on the winning side. Lifetime or seasonal match counters, depending on the game. Small samples swing it wildly, and in team games it measures the team as much as the player.
Matches played How much of the game the account has actually played. Lifetime counters. It quietly drops matches from earlier game versions, and from periods when the account was private.
Damage per round Sustained damage output, independent of who secured the kill. Per-round combat logs, where the game exposes them. Damage to shields, armour plates and destructible objects inflates it without changing the round.
Ranked tier Where the game itself places the player against everyone else. The publisher ladder — the only figure the game is the sole authority on. Third-party pages cache it, and it can be an hour or a season out of date.
Peak rank The ceiling the player has demonstrated. Seasonal archives, where the game keeps them. It usually excludes anything before the current ranking system, and beta seasons are often missing entirely.
Headshot percentage How often a kill was finished with a shot to the head. Per-kill logs. It counts only the finishing shot, and weapons that cannot headshot at all drag it down.
Detail

What each figure leaves out

PLATE / 03

Select a metric for its formula, how to read it, and the list of what it does not count.

K/D ratio = kills ÷ deaths

A 1.4 in a tactical shooter and a 1.4 in a 64-player mode are not comparable numbers. Read K/D against the mode first, the rank second, and never on its own.

Not included in this number

  • Assists and downs that someone else finished
  • Whether the kill was a trade or an opening pick
  • Round-win contribution
  • Casual and ranked pools, which most pages merge

Win rate = wins ÷ matches played

Below roughly 50 matches a win rate is noise. In squad modes it is closer to a measure of who the player queues with than of how they play.

Not included in this number

  • Sample size
  • Whether the player queued solo or in a stack
  • Abandoned and re-queued matches
  • Placement matches, which several games weight differently

Matches played = count of recorded matches

This is the number that tells you whether any of the others mean anything. Read it first.

Not included in this number

  • Matches played before the current stats system
  • Matches recorded while the profile was private
  • Modes the game does not track
  • Matches on other platforms for accounts that were not linked

Damage per round = total damage ÷ rounds played

The most honest single number in tactical shooters, and the most misleading one in battle royales, where plate-breaking pads it.

Not included in this number

  • Whether the damage led to a kill
  • Utility and grenade damage in some games but not others
  • Damage to non-player targets
  • Overkill damage past zero health

Ranked tier = a band on the game's own rating ladder

The most authoritative figure available and the one most often shown stale. Check when it was last refreshed before believing it.

Not included in this number

  • Refresh lag between the game and the page showing it
  • Which playlist or role the badge came from
  • Seasonal resets that have already happened
  • Whether placements are complete

Peak rank = highest tier reached, per season

Useful only with the season attached. A peak from a season with different tier boundaries is a different achievement wearing the same name.

Not included in this number

  • Seasons before the current system
  • Beta and pre-release periods
  • Peaks on unlinked accounts
  • Tier boundary changes between seasons

Headshot percentage = headshot kills ÷ total kills

Read it per weapon or not at all. An account-wide headshot percentage mostly reports which guns the player likes.

Not included in this number

  • Every shot except the last one
  • Weapons with no headshot multiplier
  • Explosive and vehicle kills
  • Hero abilities that ignore hit location
Reading

Four rules that cover most misreadings

RULE / 04

Read the sample first. Matches played is the denominator of everything else on the page. Under roughly fifty matches, every ratio is still moving, and in team modes a win rate is measuring the people you queued with as much as you.

Name the pool. Which mode, which playlist, which season, and; in Counter-Strike, which match service. Two figures from different pools are not a comparison. Most disagreement between pages is this, not error.

Normalise by play, not by time. Per round, per match, per ten minutes. Any lifetime total is primarily a measure of how long the account has existed, which is why Overwatch publishes rates alongside its totals and why damage per round beats total damage everywhere.

Compare against the rank, not the population. The same figure means something different at every tier. The useful question is never whether a number is good but whether it is good for that tier, and a number shown without its tier has lost the context that made it readable.

Bench

Work the ratios out

CALC / 05

Six inputs, four results, and the caveat attached to each. The arithmetic happens in the page and nothing is sent anywhere.

max 1,000,000
max 1,000,000
max 100,000
max 100,000
max 100,000,000
max 1,000,000
  • K/D ratio kills ÷ deaths
  • Win rate wins ÷ matches
  • Damage per round damage ÷ rounds
  • Kills per match kills ÷ matches
READ IT AS

A ratio is only worth reading next to the match count that produced it. Below roughly fifty matches, every figure on this bench is noise.

Questions

Frequently asked questions

FAQ / 07

Which figure should be read first on any profile?

Matches played. Every ratio on the page is a fraction with that number underneath it, and below roughly fifty matches the fractions swing on single results. Reading a K/D before reading the sample is reading a number without its error bar.

Why do two sites disagree about the same account?

Because they are reading different pools of matches, or the same pool at different moments. Counter-Strike is the extreme case — Valve publishes no per-match statistics, so every figure comes from a third-party match service with its own pool. Elsewhere the usual cause is a merged mode split, or one page holding a cache the other has refreshed.

Is K/D a useful figure at all?

Within one mode, at one rank, with the sample stated, yes. Across modes it is close to meaningless: a 1.4 in a five-a-side tactical shooter and a 1.4 on a sixty-four-player server are not comparable quantities, and most published figures merge casual and ranked pools on top of that.

Which figure is the most honest?

Damage per round in games that record it cleanly, and round win rate everywhere else. Both are normalised per unit of play, so neither simply grows with time, and the round is the unit most of these games are actually built around.

Why is ranked tier both the best and the worst figure?

Best because the game itself is the sole authority on it — no one can recompute a rank from outside the publisher rating system. Worst because it is the figure most often served from a stale cache, and nothing in the presentation tells you how old the reading is.

What does headshot percentage actually tell you?

Mostly which weapons an account buys. It counts only the finishing shot, weapons without a headshot multiplier drag it down, and ability kills that ignore hit location sit in the denominator without being able to count in the numerator. It is readable per weapon and misleading per account.