IntelBricks Data & Methodology

IntelBricks crawls publicly available Roblox catalog and games endpoints (directly and via configured proxies when required). For each tracked experience we store metric snapshots: concurrent players, visits, favorites, vote fields when present, thumbnails/icons, creator identity, genre facets, and Roblox created/updated timestamps.

Operated by North Star Global LLC. IntelBricks is not affiliated with Roblox Corporation.

Crawl scheduling targets roughly every 1 hour for catalog refresh jobs, subject to rate limits, outages, and operational pauses. Individual experiences may refresh more or less frequently depending on discovery priority and API availability.

Always prefer the visible last crawled or as of timestamp when quoting a number. Stale crawls should be treated as outdated until the next successful capture.

• Top / most played — ordered by latest concurrent players (CCU) among the tracked catalog.
• Trending / analytics — weighted trend score combining CCU, visit velocity, favorites, likes, update recency, and acceleration across a selected history window (active TrendStrategy).
• Fastest growing / movers — largest absolute CCU changes over the window (preferred over percent-only views for breakout research).
• Genre ranks — relative to experiences tagged with the same Roblox primary/subgenre facet inside the tracked catalog.

Rankings are not Roblox Featured, Discover, or Chart placements. Catalog coverage is large but incomplete — ranks are relative to whatIntelBricks tracks.

Charts, deltas, and trend windows only stretch as far back as the first successful IntelBricks snapshot for each experience — not its entire Roblox lifetime. Coverage deepens as the archive ages. We do not invent retroactive CCU history.

Concise definitions live in the metric glossary. Core terms include concurrent players, visits, favorites, like ratio, trend score, movers, and data freshness.

• Concurrent Players (CCU) — The number of players currently inside a Roblox experience at the time of a snapshot.
• Playing — Synonym for concurrent players on IntelBricks boards and game pages.
• Player Count — Usually means concurrent players on IntelBricks, not unique daily users.
• Visits — Lifetime (or cumulative) visit count Roblox reports for an experience.
• Favorites — How many times Roblox users have favorited the experience.
• Like Ratio — Up-votes divided by (up-votes + down-votes) where vote data is available.
• Engagement — A conceptual cluster of signals such as CCU, favorites density, like ratio, and visit velocity.
• Growth Rate — Relative change in a metric (often CCU or visits) between two snapshot windows.

• Public-signal models only — no private revenue, retention, or session dashboards.
• API gaps, rate limits, and outages create missing or delayed snapshots.
• Names, thumbnails, and genre labels can change; universe IDs stay stable.
• Marketplace USD figures use published DevEx conversion assumptions; they are estimates.
• Predictive or “breakout” labels are research signals, not guarantees.

Prefer self-contained statements that keep who/what/when: e.g. “IntelBricks recorded approximately X concurrent players for [Game] as of [ISO timestamp].” Link the game page and this methodology page when publishing research.