How we count Roblox player numbers
Where every number on a Baseplate Tools game page comes from, how fresh it is, and what it cannot tell you.
Every game page on Baseplate Tools shows the same handful of numbers: players right now, change since yesterday, peak, visits, favorites, rating. This post explains where each one comes from, so you can decide how much to trust it.
Where the numbers come from
We do not log into anyone's account and we do not use private data. Everything on a public game page comes from public Roblox endpoints that any website can read:
- Players now, visits, favorites, name, creator, genre, created and updated dates — the public games endpoint, up to 50 games per request.
- Likes and dislikes — the public votes endpoint.
- Icons — the public thumbnails endpoint.
- Badges, game passes and in-game events — read when you open the page and cached for six hours.
Roblox itself does not publish a game's past online numbers. So everything that looks like history — charts, daily averages, peaks — is built from our own snapshots.
Snapshots, not live streams
A collector visits each tracked game again and again and saves a snapshot: how many people are playing at that moment. Busy games are visited first. Snapshots become hourly and then daily summaries; the chart you see is drawn from them.
Two things follow from this:
- "Now" is the last time we looked. Every number says when it was counted ("counted 12 minutes ago"). We do not promise a fixed refresh rate; we show how old the number actually is.
- History starts the day we started. Our public tracking began on October 27, 2026. A game we added today has no chart before today — and we do not draw one.
What each number means
| Number | How we count it |
|---|---|
| Playing now | The latest snapshot of this game |
| vs this hour yesterday | Compared with the snapshot closest to 24 hours ago, within ±90 minutes. No snapshot in that window — no arrow |
| Peak (24 h) | The highest of: the chart points of the last 24 hours, the current number, and our peak since tracking if it was set within those 24 hours |
| Peak since tracking | The highest number we have seen — not an all-time record |
| Visits and favorites per day | The gain against the previous calendar day (UTC); the first day has none |
| Update effect | Our last snapshot within 6 hours before an update, against the average of complete 3-hour and 24-hour windows after it |
If a window has not closed yet, the value stays empty. An honest dash is better than a believable guess.
What we check every hour
An audit runs over the database and looks for numbers that cannot be true: a peak lower than the current player count, a peak in the future, a daily average above that day's peak, a busy game that has not been checked for hours. When it finds one, we fix the cause, not the number.
Why we publish this
Numbers without a method are just decoration. If you see a number on Baseplate Tools that looks wrong, it probably is — tell us, and we will show you exactly how it was counted.