Concise definitions for metrics IntelBricks exposes or discusses. Definitions are written to be quotable without surrounding context.
The number of players currently inside a Roblox experience at the time of a snapshot.
IntelBricks records concurrent players (often abbreviated CCU) from public Roblox catalog/game APIs during each crawl. CCU changes quickly; treat any figure as point-in-time, not a daily average unless a time series says otherwise.
Related: Playing · Player Count · Visits
Synonym for concurrent players on IntelBricks boards and game pages.
“Playing” on IntelBricks means the live concurrent player count from the latest successful crawl for that experience.
Related: Concurrent Players (CCU) · Player Count
Usually means concurrent players on IntelBricks, not unique daily users.
When IntelBricks ranks games “by player count,” it orders by concurrent players (CCU) unless the board explicitly uses visits or another metric.
Related: Concurrent Players (CCU) · Visits
Lifetime (or cumulative) visit count Roblox reports for an experience.
Visits are a cumulative popularity signal. They grow over time and do not equal current concurrent players. Visit velocity (change between snapshots) can indicate recent demand.
Related: Concurrent Players (CCU) · Favorites · Growth Rate
How many times Roblox users have favorited the experience.
Favorites reflect saved interest. High favorites with low CCU can mean intermittent engagement; rising favorites alongside CCU often support lasting demand.
Related: Visits · Like Ratio · Engagement
Up-votes divided by (up-votes + down-votes) where vote data is available.
IntelBricks surfaces like ratio as a quality/engagement hint. It is not a revenue metric and can be sparse for new or lightly voted experiences.
Related: Engagement · Favorites
A conceptual cluster of signals such as CCU, favorites density, like ratio, and visit velocity.
IntelBricks does not publish a single proprietary “engagement score” as truth. Boards combine observable public metrics; interpret engagement in context of genre and age of the title.
Related: Like Ratio · Favorites · Concurrent Players (CCU)
Relative change in a metric (often CCU or visits) between two snapshot windows.
Growth rate on IntelBricks is computed from stored snapshots over a selected history window (for example 6h or 24h). Percent changes on tiny bases can look extreme — prefer absolute deltas for breakout detection.
Related: Trend Score · Player Growth · Movers
Change in concurrent players between crawl snapshots over a chosen window.
Shown as absolute and percent CCU deltas on trending boards and game pages. Absolute movers are often more actionable than percent-only views for mid/large titles.
Related: Growth Rate · Movers · Concurrent Players (CCU)
IntelBricks’ weighted momentum score across CCU, visits, favorites, likes, update recency, and acceleration.
Trend score is a research signal, not an endorsement. Weights are defined by the active TrendStrategy and can evolve; methodology notes document the intent of the composite.
Related: Growth Rate · Ranking · Update Recency
Position of an experience on a specific IntelBricks board or metric.
Global CCU rank is relative to the tracked catalog size at crawl time — not Roblox Featured, Chart, or Discover placement. Genre ranks use IntelBricks’ genre facets.
Related: Concurrent Players (CCU) · Trend Score · Tracked Catalog
Informal label for high CCU, visits, or favorites — context-dependent.
IntelBricks prefers naming the actual metric (playing, visits, favorites) over vague “popularity.” When used, it points at a named ranking board.
Related: Concurrent Players (CCU) · Visits · Ranking
Sustained or accelerating movement in metrics across recent snapshots.
On IntelBricks, “trending” usually means high weighted trend score for the selected window — not necessarily the absolute biggest games.
Related: Trend Score · Growth Rate · Movers
Past concurrent-player observations stored as timed snapshots.
History begins at the first IntelBricks crawl for each experience — not the Roblox created date. Coverage deepens as the archive ages.
Related: Concurrent Players (CCU) · Snapshot · Data Freshness
A timestamped capture of public metrics for an experience during a crawl.
Snapshots power charts, deltas, and trend scores. Cadence depends on crawl scheduling; gaps can occur during outages or rate limits.
Related: Data Freshness · Historical Player Count
How recently IntelBricks successfully crawled an experience or refreshed a board.
Game pages show last crawled times. Rankings refresh from the catalog archive on a schedule — always prefer the timestamped “as of” time when citing figures.
Related: Snapshot · Last Crawled
The timestamp of the most recent successful IntelBricks capture for an entity.
If last crawled is stale, treat CCU and related metrics as outdated until the next successful crawl.
Related: Data Freshness · Snapshot
Experiences with the largest absolute concurrent-player swings in a window.
The fastest-growing / movers boards prioritize absolute CCU change — useful for spotting sudden demand even when percent growth looks modest on large titles.
Related: Player Growth · Trend Score
Roblox primary/subgenre facets mapped into IntelBricks market views.
Genre rankings compare experiences within a facet. Titles may appear in both a primary genre and a subgenre where Roblox taxonomy provides both.
Related: Ranking · Tracked Catalog
The Roblox user or group credited as the experience creator.
IntelBricks creator and group pages aggregate portfolio CCU, visits, and related games from the tracked catalog — not private Creator Dashboard analytics.
Related: Tracked Catalog · Visits
A Roblox place/universe players can join; “game” on IntelBricks means experience.
Pages are keyed by universe ID. Names and thumbnails can change; the universe ID in the URL remains the stable identity.
Related: Tracked Catalog · Ranking
The set of Roblox experiences IntelBricks has discovered and continues to crawl.
The catalog is large but not every Roblox experience ever published. Rankings are relative to tracked coverage, not the entire Roblox platform.
Related: Ranking · Data Freshness
How recently Roblox reports the experience was updated.
Used as one input to weighted trend scoring. Update timestamps come from Roblox metadata and are distinct from IntelBricks crawl times.
Related: Trend Score · Last Crawled
Whether players return over time — not directly published as a dashboard retention curve on IntelBricks.
Public catalog APIs do not expose official D1/D7 retention. IntelBricks approximates demand change via CCU, visits, and favorites history only; do not treat those as retention substitutes.
Related: Engagement · Historical Player Count
Average time spent in an experience — not a core public IntelBricks metric.
IntelBricks does not claim access to private session analytics. Use Creator Dashboard or first-party telemetry for session length.
Related: Engagement · Retention
See also data & methodology for collection cadence, ranking rules, and limitations.