Quick answer
ROB RUN's current Steam player count is rendered above from the latest stored observation for app 4262460. The page includes its UTC observation time, today's observed peak and a rolling 24-hour chart. A scheduled collector checks Steam every ten minutes; refreshing this page loads saved observations.
On this page 7 sections
What is counted?
The source is Valve's GetNumberOfCurrentPlayers Web API. It returns game-wide activity for the selected app and excludes players disconnected from Steam. It does not provide a population for each ROB RUN world or region.
| Display | Definition |
|---|---|
| Players | Latest successfully saved Steam count, including a valid zero |
| Observed at | UTC time this collector obtained the response |
| Today's observed peak | Highest saved sample since 00:00 UTC, with its time and sample count |
| Stale | Last sample is over 15 minutes old or a later collection failed |
| Missing interval | No completed successful value is available; the chart has a gap |
How is the history collected?
Collection began on November 12, 2026. The collector targets ten-minute intervals, or 144 scheduled checks per full UTC day. Each interval has one stored record. Successful counts, actual observation times and failed attempts are retained; a page visit does not trigger another Steam request.
The chart shows the latest 24 hours as they accumulate. Its line connects consecutive successful intervals only. A single observation appears as a point. Missing or failed checks do not become zero and are not filled by interpolation. The first day and any interrupted window have partial coverage, stated beside the chart.
Records are retained beyond the displayed day. The downloads offer the most recent day or up to fourteen days of saved records. Before that much time has elapsed, they contain only the history actually collected. No pre-launch or earlier observations are reconstructed.
Is the daily peak Steam's official peak?
It is our highest observed sample for the UTC day, rather than a continuous measurement or an official daily maximum. A larger population between ten-minute checks can be missed. At midnight UTC, the peak resets to the new day's samples while the latest observation can still belong to the previous day. If there is no successful sample today, the peak remains empty.
Compare complete days with similar coverage before drawing a trend. An incomplete first morning is a different observation window from a full day, and a failed collection says nothing about the game's actual population at that moment.
Download and cite the observations
Open the observation table above for exact timestamps or download 24-hour CSV and up to fourteen days. Fields include app ID, scheduled interval, attempted time, observed time, player count, result, collection trigger and completion time. All timestamps are UTC. Failed attempts have an empty player field.
When citing a number, include ROB RUN, Steam app 4262460, player count, UTC observation time, and this page's URL. Identify a peak as the highest sampled value and state the day's coverage. The original count comes from Steam; the timestamped historical series is collected by this independent site.
Does the count prove my server is online?
It shows Steam-wide activity at the recorded time. Use the server-status checklist to test your selected world, match an error code and compare connections. An aggregate rise or drop alone cannot identify maintenance, an attack or a problem on your own network.
Sources and editorial check
Checked 2026-11-12. This is an independent guide. Game rules can change during Early Access.