Players and CCU

What players now (CCU), the observed peak, average players and the hourly means are, how the player charts bucket readings, and what each history range shows.

Metrics & data / Metrics and data

Player numbers in the panel are the collector's readings of how many people were in a game at one moment. Each reading is a snapshot; how often a game gets one depends on its tier.

Player numbers at a glance

Players now (ccu)players

Window: the moment of the latest snapshot. Source: Roblox's game details, every 5 minutes to every week by tier. Null: the game has never been read, or is a private or unreleased studio game.

Observed peak (peak_ccu, peak_ccu_at)players

Window: since tracking began. Source: the highest players of any stored snapshot. Null: no snapshot yet.

Of its peak (peak_ratio)ratio, 0 to 1

Window: now. Source: recomputed every 5 minutes. Null: no peak above zero.

Average players, 24 hours (avg_ccu_24h)players

Window: the 24 hours before the latest snapshot. Source: recomputed every 5 minutes. Null: first snapshot under 20 hours old, or fewer than 3 snapshots in the day.

Hourly mean and peak (ccu_hourly)players

Window: one UTC clock hour. Source: a TimescaleDB aggregate refreshed every 10 minutes. Null: no snapshot in that hour.

Players by hour of the weekplayers

Window: the last 4 weeks (1 to 12), complete hours only, in UTC. Source: the hourly means. Null: no complete hour in that cell.

How a player count reaches the page

From Roblox to a player chart. A snapshot batch reads up to 50 games' details from Roblox and stores one snapshot per game, updating the game's players now and its observed peak. TimescaleDB rolls the snapshots into hourly means every 10 minutes, and the worker recomputes the averages, peak ratio and signals every 5 minutes. The API reads the snapshots for charts and the derived numbers for tiles, and the panel draws them.

The formulas, written out:

text
peak_ratio  = ccu / peak_ccu                       (empty when peak_ccu is 0)
avg_ccu_24h = mean(ccu of every snapshot in the 24 hours before the latest)
hourly mean = mean(ccu of the hour's snapshots); hourly peak = max(...)
bucket avg  = round(mean(ccu of the bucket's snapshots)); bucket peak = max(...)

Players now (CCU)

CCU (concurrent users) is how many people are playing a game at the moment of its latest snapshot. It is the playing count Roblox's public game details give (games.roblox.com/v1/games), stored as ccu. It is labelled Players now on a game's page, Players in Explore and CCU on a studio game's hub.

It is as old as the game's last snapshot: a hot game's is at most about 5 minutes old, a cold game's up to a day. The studio hub says when it was read ("playing now, read 3 minutes ago"). A game that has never been read has no CCU, and a private or unreleased studio game shows "Not tracked: private or unreleased".

The observed peak (highest seen since tracking began)

A game's peak is the highest CCU any snapshot of it has recorded since the collector started tracking it, with the time it was seen (peak_ccu, peak_ccu_at). It is shown under the Concurrent players chart as "Highest seen since tracking began".

It is not Roblox's all-time record: a game that peaked before it was tracked, or between two readings, has a lower peak here. Where the panel says "all-time high" (Radar's At an all-time high list, the Of its peak signal) it means this observed peak. A game's own peak player count as Roblox reports it to the owner is a different number: Peak concurrent players.

Of its peak (peak ratio)

Players now divided by the observed peak, from 0 to 1, shown as a percentage on a game's page under Signals. 100% means the game is at the highest count seen. It is recomputed every 5 minutes and is empty when the game has no peak above zero. It feeds the breakout score.

Average players over the last 24 hours

The mean of every snapshot's CCU in the 24 hours before the game's latest snapshot (avg_ccu_24h). It is empty until the game has most of a day of history: its first snapshot must be at least 20 hours old, with at least 3 snapshots in the day. The day before is averaged the same way (avg_ccu_prev_24h) for daily growth. Recomputed every 5 minutes.

It is a mean of readings, not of time: a game read more often for a while (a hot spell) weights that stretch more.

Hourly means and hourly peaks

The database keeps, for every game and clock hour (UTC), the mean and the highest CCU of that hour's snapshots, and how many there were (ccu_hourly, a TimescaleDB continuous aggregate). TimescaleDB refreshes it every 10 minutes for the last 3 days; the newest hour is read from the raw snapshots until then.

Hours are the honest resolution across games, since games are read at different rates. The breakout score and its signals, the market's players over time and players by hour of the week all come from these hourly means, not from raw snapshots.

Average and peak players in a chart

A game's Average and peak players chart, and its Concurrent players chart, group the snapshots of the chosen range into buckets. For each bucket:

  • Average is the mean CCU of the snapshots in it, rounded.

  • Peak is the highest CCU of a snapshot in it.

  • Visits and favorites are the last reading in the bucket (see engagement).

A bucket with no snapshot has no point. A chart needs at least two readings in its range; with fewer it says so.

History ranges and how much each chart point covers

A game's page has five ranges. Each has a fixed bucket width, chosen to give a few hundred points:

RangeCoversOne point per
6hThe last 6 hours5 minutes
24hThe last 24 hours5 minutes
7dThe last 7 days30 minutes
30dThe last 30 days2 hours
AllEverything since tracking1 day

A game read every hour (warm tier) has one point an hour even on the 5-minute ranges, so its line has fewer points; a cold game, one a day.

Players over time on the market overview

The Market overview's Players over time adds up the hourly mean players of today's 1,000 most played tracked games (by players now). In the 24-hour and 7-day ranges each point is an hour; in the 30-day range each point is a day, the mean of its hours. Stacked by genre, it shows the six largest genres over the range and adds the rest, games without a genre included, as one series. Each game counts under the genre Roblox files it under today, for its whole history.

Those 1,000 games are read at least every 15 minutes, so every hour has a reading of each of them.

Players in tracked games (market tile)

The Market overview's Players in tracked games tile adds up players now across every listed game that has a genre, and says across how many genres. Games without a genre are not in this sum. Games tracked counts every game the platform stores, including games still waiting for their first reading and games Roblox no longer serves; "the 1,000 most played are charted" is the set above.

When a game is played: players by hour of the week

The Players by hour of the week heatmap on a studio game's Overview shows when a game is played, in UTC. Each cell is one weekday and hour: the mean of that hour's hourly means over the last 4 weeks, and the highest players seen in it. Only complete hours count, so the hour still being read never does. Any tracked game has it (GET /v1/games/:id/hours, weeks 1 to 12, 4 by default).

Related: Growth and momentum, Freshness and empty numbers, Glossary.

Updated