Roblox Game Updates
What actually changed across the games we track — updates shipped, milestones crossed and games surging, newest first. Every entry is a change we watched happen between two hourly readings.
3 September
270 playingMilestone
10,926 playingMilestone
5,927 playingMilestone
11,109 playingMilestone
10,424 playingMilestone
14,464 playingSurging
1,655 playingSurging
1,499 playingSurging
4,249 playingUpdate
8,121 playingUpdate
3,770 playingUpdate
10,670 playingUpdate
2,590 playingUpdate
1,748 playingUpdate
1,219 playingUpdate
1,272 playingUpdate
3,806 playingUpdate
1,792 playingUpdate
2,070 playingUpdate
8,890 playingUpdate
2,738 playingUpdate
1,583 playingUpdate
8,854 playingUpdate
4,359 playingUpdate
1,669 playingUpdate
2,260 playingUpdate
1,956 playingUpdate
18,411 playingUpdate
1,379 playingUpdate
1,260 playingUpdate
10,862 playingUpdate
1,213 playingUpdate
2,579 playingUpdate
1,432 playingUpdate
1,635 playingUpdate
9,640 playingUpdate
2,370 playingUpdate
55,055 playingUpdate
23,000 playingUpdate
1,650 playingUpdate
4,198 playingUpdate
5,195 playingUpdate
2,849 playingUpdate
1,254 playingUpdate
2,425 playingUpdate
57,870 playingUpdate
4,099 playingUpdate
1,187 playingUpdate
2,121 playingUpdate
11,680 playingMilestone
4,140 playingSurging
11,656 playingSurging
2,849 playingUpdate
2,858 playingUpdate
1,329 playingUpdate
6,980 playingUpdate
3,335 playingUpdate
2,916 playingUpdate
1,127 playingUpdate
5,278 playingUpdate
4,022 playingUpdate
3,383 playingUpdate
8,101 playingUpdate
2,329 playingUpdate
4,424 playingUpdate
6,035 playingUpdate
2,446 playingUpdate
1,158 playingUpdate
14,767 playingUpdate
4,952 playingUpdate
8,753 playingUpdate
21,848 playingUpdate
1,866 playingUpdate
366 playingMilestone
1,046 playingSurging
8,604 playingSurging
5,751 playingUpdate
54,096 playingUpdate
1,015 playingUpdate
2,288 playingUpdate
3,064 playingUpdate
Hourly collection began , which is 50.7 days ago, and 308 consecutive pairs of readings have been compared so far. On the very first sweep we recorded 14,259 thresholds that games were already above and emitted none of them as events — announcing those would have credited a thousand games with reaching numbers they passed years before this site existed. Against that, 942 crossings have actually been witnessed. That ratio is the whole design.
What each filter contains
Updates — Roblox’s own published timestamp for a game moved forward between two of our readings, meaning the developer shipped something. Alongside it sit the editorial changes: a game renamed, re-iconed, re-bannered, or its description rewritten.
Milestones — a game crossed a round number while we were watching: 100 / 1K / 10K / 100K / 1M concurrent players, 100K / 1M / 10M / 100M / 1B / 10B visits, or 10K / 100K / 1M / 10M favourites. Only crossings we observed appear; everything a game was already above when we started is recorded silently and can never be claimed.
Trending — a game whose hourly move was extreme against what every other tracked game did in the same hour. This is not the same as the trending chart, which scores sustained momentum over days; this is the single-hour spike, which is a different and more perishable event.
All — every one of the above in one stream, ordered by when it happened and by nothing else. An event feed sorted by anything other than time is a chart wearing a disguise.
Questions about this feed
Roblox publishes an "updated" timestamp for every experience, and we read it once an hour along with the player count. When that timestamp moves forward between two of our readings, the developer has published something. It is the highest-confidence signal available to anyone outside the game, because it comes from Roblox rather than from us guessing at a player-count wobble. What it does not tell you is what changed — Roblox exposes the fact of an update and not its contents, so this page says a game shipped an update and never invents patch notes.
Because the second sentence would be false. We started taking hourly readings on 17 August 2026 and hold nothing from before that. A game sitting at half a million concurrent players today crossed 100,000 years ago, and announcing it as a fresh achievement would be inventing history. On the first reading of every game we record every threshold it is already above as a silent baseline, which permanently blocks that threshold from ever being reported as something we saw. Concurrent players also is not a counter that only goes up — a game near 1,000 crosses that line twice a day — so what we can honestly claim is the first time we ourselves recorded it in that band. Visits and favourites do only go up, so those are worded as a genuine passing of the mark.
A game has to be doing something unusual, not just doing well. Roblox concurrency has a violent daily cycle: at peak hours nearly every game on the platform is up, so a fixed percentage threshold would fill this page with games whose only achievement was existing during a busy hour. Instead we take every tracked game holding at least 500 players, express each one's hourly move as a log ratio, and standardise those across the whole set for that hour. A game surges when it lands at least 3 standard deviations above what everything else did over the identical window and is up at least 15% in its own terms. A game can only surge once every twelve hours, so a long climb reads as one story rather than a dozen.
Ordinary player-count movement, which is what the charts are for — every game's numbers change every hour and that is weather, not news. Repeat crossings of a threshold a game has already been recorded above. Milestones below a sensible floor: 10,000 concurrent players, 1M visits, 100K favourites, because every game we track already passed the smaller ones. Anything happening to a game holding under 1,000 concurrent players, with milestones exempted — a game passing a hundred million lifetime visits is worth reading about whatever its player count happens to be this hour. And the first reading of any game, always: we have no previous value to compare it against, and "we had not looked before" is not a change.
Because hourly collection started on 17 August 2026, and an event can only exist where we hold two readings either side of it. Everything on this page was derived from consecutive sweeps that actually ran; nothing is backfilled from before collection began and nothing is estimated. An empty filter means we have not observed that kind of event yet, which is a different statement from nothing having happened. The feed lengthens on its own with no deployment or backfill as more hours accumulate.
Yes, and they are the one part of this that needs a warning. Player counts and visits arrive in the hourly sweep, so those diffs are exact. Names, descriptions, icons and banners live only on the game record, which is refreshed by a separate, slower ingestion job — so a rename shows up here on the first hourly reading after that job noticed it, not the moment it happened. Descriptions are compared as a hash rather than stored twice, so the feed can tell you a description was rewritten but not what it now says; these are unmoderated developer strings and this site is read by children.
Follow it. The Follow button on any game page adds it to your watchlist, and every event on this page for a game you follow becomes a notification on the bell at the top of this page — updates, milestones, renames and surges. Editorial churn like icon swaps and description edits is browsable here but deliberately not something we interrupt you for. Notifications are in-app only; nothing is emailed and no address is required.
Follow the numbers further
Trending Roblox games → · Most played right now → · Biggest player gains → · Biggest player drops →
Your watchlist → · Milestones as they happen → · Daily history → · The full game database → · Working game codes → · Best Roblox games by genre →