3,232 Roblox games tracked, re-checked every day

Updated

SpawnScope

Methodology

SpawnScope publishes one thing: what the public Roblox API returned about an experience, and the date it returned it. This page explains exactly how that happens so you can judge the numbers yourself.

What we collect

Once a day an automated collector reads, for each tracked experience:

  • concurrent players (playing)
  • cumulative visits
  • favourite count
  • up and down votes, from which the rating percentage is derived
  • the experience's own updated timestamp
  • creator, genre and creation date

These come from Roblox's public endpoints — the games, votes and thumbnails APIs, plus the universe lookup used to resolve a place ID. We do not scrape the website, we do not run game clients, and we do not estimate anything.

How games enter the tracked set

The collector starts from a small set of seed experiences and walks Roblox's own "recommended experiences" graph outward, breadth-first, up to a fixed ceiling per run. This means the tracked set reflects what Roblox itself associates with popular games, rather than a list we hand-picked. As of the latest run we hold records for 3,232 experiences.

Why some games have gaps

Each run collects a bounded cohort, so a game that drops in popularity can fall out of that cohort and reappear later. When that happens the history has a gap. We show the gap. Charts are plotted against a real calendar axis, and a seven-day comparison is only made against a reading that genuinely exists on or before that date — never against "the reading seven rows up", which would quietly compare the wrong dates.

What we publish and what we hold back

An experience gets a public page once we hold at least 3 daily readings for it and it has recorded visits. A single data point is not a trend, and a page built on one is a thin page that helps nobody. We currently hold 18,646 readings in total, collected between Jul 24, 2026 and Aug 27, 2026; 1851 experiences clear the publication threshold.

What these numbers are not

  • Not revenue. Roblox does not publish per-experience earnings, and we do not model them.
  • Not unique players. "Visits" is a cumulative session count published by Roblox; it counts repeat sessions from the same account.
  • Not a live feed. Concurrent players is a single reading taken once a day. A game's true peak almost certainly sits above the number we recorded.
  • Not a quality verdict. The rating percentage is Roblox's own up-vote share. We show the vote count alongside it because a 100% rating from 40 votes means very little.

Timezone and timing

All dates are UTC. The collection runs at roughly the same time each day, but a reading taken at a different hour will land on a different point of a game's daily cycle, so small day-to-day movements should not be over-read. Week-over-week comparisons are more reliable than 24-hour ones for that reason.

Corrections

If a number here contradicts what you see on Roblox, the most likely explanation is that our reading is up to 24 hours old. If you believe something is genuinely wrong, please tell us — we log corrections publicly.