concurrent player counts

Concurrent player counts are point-in-time readings of how many people are inside a game right now, published alongside derived peaks and averages. Four sources in this slice carry them, each in a different shape.

Steam Charts - Concurrent Players publishes current players, 24-hour peaks, all-time peaks and monthly average-player history per tracked game. Homepage windows cover trailing 24h/48h/30-day periods, while per-app monthly tables extend back to each game's Steam launch — multi-year history served as HTML.

SteamSpy API reports daily-refreshed concurrent players next to ownership estimates, one record per Steam application. Steam Web API exposes GetNumberOfCurrentPlayers, described as point-in-time, with no historical series. TwitchTracker - Game & Channel Rankings carries the streaming analogue: peak viewer and average viewer ranking fields over trailing 7-day windows.

A sales table tells you what was bought; a concurrent count tells you whether anyone is still playing. Live-service health, retention and event-timing questions are unanswerable without it.

Snapshot versus series is the practical trap. GetNumberOfCurrentPlayers returns one moment; Steam Charts holds monthly averages reaching back to launch. Buying the snapshot when you needed the series means rebuilding history through daily scrapes — and across Datadory's 1,744 cataloged datasets only 22.6% update daily.

Access method adds cost: two of the four sources arrive by web scraping rather than an official API, so markup changes land in your maintenance budget.

1. Check which shapes ship. Steam Charts documents current players, 24-hour peaks, all-time peaks and monthly averages; a vendor offering one number offers one question answered.
2. Ask how far history reaches. Steam Charts per-app monthly tables extend to each game's Steam launch; a point-in-time endpoint cannot be stretched into a series afterwards.
3. Confirm cadence and limits. SteamSpy refreshes daily and documents 1 req/sec generally, 1 req/60s for 'all' — undocumented caps surface as failed collections.
4. Verify the access channel. Steam Charts and TwitchTracker publish HTML and JSON for scraping; Steam Web API is an official API needing a registered key.
5. Mind the denominator. Steam Charts' homepage surfaces the top ~100 by current players, though tens of thousands of titles have their own pages.

Where to see it in context: interactive-home-entertainment data.

• api-rate-limits — Request budgets such as SteamSpy's documented 1 req/sec cap decide whether a collection job finishes at all.
• playtime-aggregates — Time-in-game measures that complement concurrency; SteamSpy accumulates lifetime totals since March 2009 plus rolling two-week windows.