[Glossary](/glossary.md)/[Statistics](/glossary/category/statistics.md)

# Coverage

How much of a server's playerbase a stats site actually tracks, and how fresh those accounts are.

Also known as tracked accounts, tracking coverage.

No tracker sees every account. Wargaming's API is rate limited, so a site discovers accounts through [clan](/glossary/clan.md) rosters and searches, then refreshes each on a cadence it can afford. Coverage is the share of the region's active players it holds, and how recently each was updated.

It matters because every leaderboard and every server average is computed over the [tracked](/glossary/tracks.md) population, not over the whole server. Wide coverage makes those numbers representative, thin coverage makes them a sample.

## See it on the site

[Tracking coverage](/coverage.md)

## Related terms

[SessionA block of battles played in one sitting, reconstructed by a tracker from the difference between two snapshots of an account.](/glossary/session.md)[Expected valuesThe per-vehicle server averages a rating measures a player against: what a typical player produces in that exact tank.](/glossary/expected-values.md)

[Every World of Tanks term](/glossary.md)

## Navigation

- [unicum.gg](/index.md)
- [Discord](https://discord.gg/Hqbfb8YPbU)
- [GitHub](https://github.com/unicum-gg/unicum.gg)

## Indexes

- [llms.txt](/llms.txt): the API, the MCP server and the other machine-readable surfaces.
- [llms-full.txt](/llms-full.txt): the same, with every endpoint's parameters inline.
- [sitemap.md](/sitemap.md): every section of the site, down to the individual pages.