Metrics and data

Every number the panel shows, defined once: what it means, how it is computed, over what window, where it comes from and when it is empty.

Metrics & data

Every number in the panel is defined once, in this section. Each page says what a number means, how it is computed, the window it covers, where it comes from, how often it is read and when it is left empty.

Where the panel's numbers come from

The panel never asks Roblox or GitHub directly. Three readers store what they read, and every page reads that stored data:

The collector

Reads public Roblox data about every tracked game (players, visits, favorites, votes, sorts, recommendations) and Rolimon's list, every 5 minutes to every week by tier. These are the market numbers, and the public numbers of the studio's own games.

Owned analytics

A daily read of the numbers Roblox reports only to a game's owner (daily active users, retention, revenue), for the studio's own games, with their group's key.

The GitHub collection

Reads the BlockoutGames organization every 30 minutes for the Code pages.

Where every number comes from. The collector reads Roblox's public endpoints, Rolimon's list, Roblox Open Cloud with each studio group's key, and GitHub, and stores the readings in Postgres. TimescaleDB keeps hourly means of the player counts, and the worker recomputes growth and the breakout score every 5 minutes from the stored readings. The API reads the stored and derived numbers, caches its answers in Redis, and the panel shows them.

What each stored table holds is in Data model; how a stored number reaches the page is in API and caching.

How often each is read, and what "stale" means, is in Freshness and empty numbers.

The pages

Rules every number follows

  • Empty is never zero. A number nobody could read or compute is shown as a dash with its reason, never as 0. A growth of 0% means the game really did not grow.

  • Times and days are UTC. A day is a UTC day and a week starts Monday 00:00 UTC (GitHub's weeks start Sunday 00:00 UTC; see Code metrics).

  • Growth is a ratio. The API sends 0.5 for +50%; the panel shows it as a percentage.

  • Peaks are what the collector saw. A game's "all-time" peak is the highest player count seen since tracking began, not Roblox's real all-time record.

How each number is described

Each Metrics & data page opens with the numbers it defines, each with the same five facts:

Name

The label the panel shows, and the field the API sends.

Unit

Players, visits, a ratio (shown as a percentage), Robux, hours or days.

Window

The time it covers: a moment, the last 24 hours, a UTC day, a range.

Source

Where it is read from, and how often.

Null rule

When it is empty instead of a number, and what the panel says then.

Every word in one list: Glossary.

Updated