The official Roblox Games API reported 1,434 people playing Scream And Run at 05:33 UTC on September 1, 2026. In the same response, the experience had 557,105 visits and 4,533 favorites. A separate Votes API request returned 1,162 upvotes and 129 downvotes. These are dated snapshots, and the concurrent player count can change from minute to minute.
Player-count snapshot card
The API also identified the experience as Scream And Run [RELEASE], Place ID 113481077323469, Universe ID 10761687472, created by Scream And Run Studios. Check those fields before trusting a statistic from a similarly named experience.
What “playing” means
playing is the platform’s concurrent total for the universe at the moment Roblox generated the response. It includes active people across current servers and whatever internal places belong to the experience. It does not say how many are in Escape, Free Roam, Hide And Seek, a lobby, or a custom room.
The count may move quickly after a creator update, video, time-zone peak, server outage, or ordinary joins and leaves. A single value cannot establish that the game is growing or declining. For a trend, collect consistent time-stamped samples over many days and keep missing requests separate from genuine zero values.
Do not compare playing directly with maxPlayers. The 50-player maximum is an instance-capacity setting; 1,434 playing is a universe-wide concurrent total across instances.
Visits, favorites, and votes are different
Visits accumulate as the experience is entered under Roblox’s rules. They are not unique accounts, successful escapes, badge awards, or purchases. One player returning can contribute more than once. A rising visit number shows additional entries, not how long people stayed.
Favorites count accounts that saved the experience. A favorite can help a player return later, but it is not a live player, a vote, or a guarantee that the account completed a round. Votes are collected separately and can change on a different schedule.
The raw upvote and downvote counts are more transparent than presenting a rounded rating without context. If you calculate a percentage, store both source counts and the check time so another player can reproduce it.
Refresh the official value
Open the Games API request and find the object whose id is 10761687472. Read playing, visits, favoritedCount, maxPlayers, created, and updated. If the response is empty or fails, do not show zero; keep the last successful value with its timestamp.
Open the Votes API request separately for upvotes and downvotes. Record its request time too. Browser or network tools may format the JSON differently, but the field names are the same.
Always link back to the official experience page for a human-readable identity check. Third-party trackers can add historical charts, but their sampling interval and missing-data rules should be visible before you rely on them.
Use the number for a player decision
Concurrent count can help you estimate whether public matchmaking is likely to find people at that moment. It cannot guarantee a particular region, ping, mode, lobby size, or available role. If you want to play with friends, coordinate a time or use the current in-game custom-lobby tools rather than assuming the global count places you together.
If a mode feels empty while the global playing value is high, remember that players may be distributed across servers, internal places, modes, or rounds. Check the live server browser and game UI. Do not report the API as broken solely from one quiet lobby.
If you are deciding whether the experience is “popular,” combine the current count with a longer, consistently sampled series. Visits and favorites provide scale but not current momentum. This page deliberately avoids a permanent popularity label from one launch-week snapshot.
Player count FAQ
How many people were playing Scream And Run?
Roblox returned 1,434 playing at 05:33 UTC on September 1, 2026. Refresh the endpoint for the value now.
Is visit count the number of unique players?
No. The field is cumulative visits under Roblox’s platform definition and can include repeat entries.
Are all players in one server?
No. The concurrent total is spread across experience instances. The configured per-instance maximum was 50.
Why does another tracker show a different number?
It may have sampled at another time or used a cached interval. Compare timestamps and Universe IDs before deciding there is a conflict.
Continue to Server Size for capacity or Badges for escape outcomes.