Skip to content

Settings

Guest

Profile
Credits
…

AI skill and stats calls: 0.06 credits each, plus model usage.

Game data & sharingManageYour dataManagePrivacy policy
← Analytics

Public Roblox data

Browse public Roblox data for free, without signup or MCP. Hosted AI advice uses verification and credits.

What the metrics mean

Game detail URLs use a universe ID. Roblox game links use a place ID. An experience ID; use this for statistics. The starting place ID used in roblox.com/games links.

Public metric names, units and definitions
MetricUnitMeaning
playingplayersPublic concurrent players at retrieval; not daily active users.
visitsvisitsCumulative visits, not unique players.
favoritesfavoritesCumulative public favorites.
likesvotesPublic upvotes; null means unavailable.
dislikesvotesPublic downvotes; null means unavailable.
likeRatiofractionLikes / (likes + dislikes), 0–1; null when unavailable or no votes.
maxPlayersPerServerplayersConfigured server capacity, not current occupancy.
medianPlayersplayersMedian concurrent players among matching games in the chart sample.
leaderSharefractionLargest matching game's share of the pattern's players, 0–1; null when the total is zero.
sharefractionGenre players / total players in the specified sample, 0–1.
risingCountgamesMatching games listed in Up-and-Coming; not measured growth.
trendingCountgamesMatching games listed in Top Trending; not measured growth.

Missing values remain unknown, not zero. The public data does not supply actual revenue, retention, daily active users, session length, demographics or private developer analytics.

Sources and freshness

  • Current game counts and metadata come from Roblox game statistics; public charts come from Roblox Charts.
  • Name search uses Roblox's web search endpoint, which is undocumented and may change or fail. Sponsored placements are labelled in search results.
  • fetchedAt is when Romanum retrieved the observation. Cache hits retain that time; expiresAt is its cache expiry. Roblox's underlying measurement time is not supplied.
  • Search and statistics cache for 60 seconds, charts for 120 seconds and place-to-universe mappings for one hour. Artwork is retrieved separately and can cache for up to one hour. Processes have separate caches; these do not create history.

Cite the game or chart page, metric, unit and full UTC retrieval date. Counts can change after retrieval.

Chart coverage and recorded history

Market summaries deduplicate universes across loaded charts and exclude sponsored entries. Titles match heuristic patterns that can overlap; they do not verify gameplay. Genre shares describe the specified sample, not all of Roblox. Failed charts are omitted and listed as unavailable. The overview's genre breakdown uses Top Playing Now; the Genres view uses the union of loaded charts.

Title patterns match game names and can overlap. They don't establish gameplay, demand, saturation or growth. Top Earning is Roblox's ranking, without revenue figures.

get_game_history returns only persisted public observations since Romanum collection began. observedAt is retrieval time for observed points; for null gap points it is the expected collection slot. A missing observation is not zero. Chart ranks are chart-specific, exclude sponsored rows and are retrieved separately from game counts. Do not extrapolate a short history into sustained growth. The collector schedules five-minute slots. Actual successful retrieval times can vary, and coverage exists only for games it has sampled. Opening a game page does not enroll it or backfill earlier history.

Earnings ranges are heuristic projections from current concurrent players, a chosen period and genre assumptions. They are separate from observed statistics. Read the earnings model and assumptions.

Public HTTP access

These read-only JSON endpoints require no authentication. Use them directly or through MCP.

  • GET /api/public/catalog

    Machine-readable endpoint directory, accepted queries, metric definitions and coverage guidance. Current public statistics, charts and market samples are available as JSON through /api/public/stats, /api/public/charts and /api/public/market. These use the same free public data tools as MCP and preserve retrieval times and partial coverage.

  • GET /api/games/search?q=Brookhaven

    Accepts a game name, a Roblox game URL, or a numeric place ID. Names are limited to 80 characters. A game URL is parsed and resolved through Roblox; arbitrary submitted URLs are never fetched. Results include source and retrieval/cache times.

  • GET /api/history/games

    Returns up to 100 games with recorded public observations. This is a collection directory, not a list of every Roblox game.

  • GET /api/history?universeId=UNIVERSE_ID&days=7

    Replace UNIVERSE_ID with a positive universe ID. The period accepts 1-30 days and defaults to one day. Results report their source, period, sample count, gaps, observation status and nullable metrics. An empty or unavailable response does not establish zero activity.

  • GET /api/history/compare?universeIds=ID_A,ID_B&days=7

    Compare two to five distinct games on matching recorded collection slots, with one fixed cutoff. Read the recorded spans, gaps, paired overlap and complete requested-period coverage alongside the player-count summaries. Insufficient evidence withholds statistics. Three paired slots and 50% overlap of the valid-slot union are an engineering evidence floor, not statistical significance; a qualifying short sample does not establish a sustained trend.

Public game statistics are also readable in each game's HTML page. MCP offers additional structured stats, charts, market summaries, definitions and guides; see the free MCP guide. Private connected-game metrics are not included in these public endpoints or MCP.

Ground a game idea in observations

  1. Find comparable games and inspect their public pages and chart context.
  2. Cite the actual counts, sources, sample coverage and retrieval dates. Use recorded history only where it exists.
  3. Separate the observed evidence from a design hypothesis. Describe an original mechanic or audience test, the uncertainty and what result would change your decision.

Use these observations to test a design hypothesis. Popularity alone doesn't establish demand for your game or guarantee success.