Every figure on a shooter profile is produced by a specific system inside the game, and every one of them omits something. These pages set out what each number measures, which part of the game records it, and where it stops being comparable — across eleven titles, from Rainbow Six Siege to Rocket League.
Eleven games, each with its own ladder, its own recording quirks and its own idea of what a kill is worth. Each game tracker page below opens with the same four questions and answers them for that title alone. The tail on each row names the ranked system that game runs, because a badge from one ladder means nothing on another.
Nothing on a shooter profile is measured by the page showing it. The game records an event, the publisher decides whether to publish it, and only then can anything else read it. Each of those three steps loses something, and knowing which step lost what is most of the skill in reading a profile.
The game records the event. A kill, a round, a plate broken, a heal delivered. This layer is complete but private: it exists inside the match server and the client, and most of it never leaves. Apex Legends is the clearest example of the boundary: it counts statistics per legend, and only through the trackers a player has equipped, so an account can show four hundred kills on one legend and nothing at all on another it has played for a whole season.
The publisher decides what is public. Ubisoft, Epic, Riot, Activision, EA, Blizzard, Psyonix and Sky Mavis all publish some subset of what they hold, and each draws the line differently. Blizzard career profiles are private until the account holder opts in. Activision and Epic default to public but let the player switch match history off. Valve publishes nothing per-match at all, which is why every Counter-Strike figure in circulation arrives by way of a third-party match service rather than from the game itself.
Something else reads it and caches it. This is the step that produces most of the confusion. A page can be accurate about a snapshot that is an hour, a week or a season old, and nothing in the presentation tells you which. Ranked tier is the figure this hurts most: it is the most authoritative number available, coming straight from the ladder, and it is the one most often displayed stale.
There is a fourth step that only applies to a live lookup service, and it is the reason this site is not one: a lookup breaks whenever any of the three steps above changes. A page that explains what damage per round excludes stays true when the endpoint moves.
So the practical question is never whether an fps tracker has the right number. It is which pool that number came from, when it was read, and what the game declined to publish in the first place. Every game tracker page here opens with those three answers before it shows a single figure.
The same seven figures recur across every game tracker page on this site. The fourth column is the one worth reading twice: it names what the number 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. |
Pick a metric to see the formula, how to read it, and the list of things it does not count. Every stat tracker in circulation reports these seven figures; almost none of them report the fourth column.
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
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
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
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
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
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
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
A tier is the only figure on a profile that the game itself is the sole authority on. Every other number can be recomputed from match history by anyone holding the data; a rank is assigned by the publisher's own rating system and cannot be derived from outside it. That makes it the most trustworthy thing on a profile and, at the same time, the most frequently misread.
The misreading is almost always the same: a single leaderboard badge shown next to a name has silently picked one ladder for you. Rocket League keeps a separate rating for 1v1, 2v2, 3v3 and every Extra Mode, and ranks three tiers apart across playlists are completely ordinary. Overwatch 2 ranks Tank, Damage and Support separately, so one account holds three ranks at once. Fortnite keeps Battle Royale, Zero Build and Reload apart. In each case a leaderboard position is real but partial.
The second misreading is time. Ladders re-seed. Rank Points in Rainbow Six Siege are placed again through placement matches each season; Apex resets Ranked Points every split with the entry cost scaling by tier; Rocket League compresses the extremes toward the middle rather than clearing anything. A tier from last season and a tier from this one are not the same claim, and a peak rank without its season attached is not a claim at all. Emerald was inserted into the Siege ladder in Year 8, so a Diamond from before that sat one step higher than a Diamond does now.
No page here prints the percentage of players in a given tier. Those distributions move every season, and a fixed figure on a static page is wrong soon after it is written. The order of the ladder, the sub-division structure and the reset behaviour are the durable parts, and those are what each game page carries.
Six inputs, four results, and the caveat that applies to each. Nothing is sent anywhere: the arithmetic happens in the page.
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.
Statistics are also the raw material of an esports market, and the same discipline applies: a price built on a merged casual-and-ranked K/D: the default on many a stat tracker, is a price built on the wrong number. The betting section covers how esports odds are constructed, which state-regulated sportsbooks carry esports markets in the United States, and where those markets are legal.
No. There is no lookup box here and no account is queried. Each game page explains where that game keeps its figures, which of them are published, and how to read what you find — whether you find it in the game client, on the publisher’s own profile page, or on one of the third-party services that hold a data licence.
That is a deliberate scope. A lookup that breaks the moment a publisher changes an endpoint is worth less than an explanation of what the number meant in the first place.
Almost always because they are reading different pools of matches. Counter-Strike is the clearest case: Valve publishes no per-match statistics API, so every figure in circulation comes from a third-party match service, and two services that recorded different games will disagree while both being accurate.
The other common cause is a merged pool. Casual and ranked records are stored separately in most games, and a page that adds them together will show a lower K/D for anyone who warms up outside ranked.
Matches played, and it is not close. Every ratio on a profile is a fraction whose denominator is the match count, and below roughly fifty matches those fractions swing on single results. Read the sample first, then the ratios.
Because they would be wrong within weeks. The share of the population sitting in each tier moves every season as the ladder re-seeds and boundaries shift, and a hardcoded percentage on a static page decays silently. The ladder order and the way the ladder resets are the parts that hold, so those are what these pages carry.
Not through the published routes. Blizzard career profiles are private by default, and Activision and Epic both let an account holder switch match history off at any time. When a profile goes private the third-party pages usually keep serving whatever they cached last, which is why a figure can look current and be a season old.