Pick a room by its current map, see what is coming next, and find out when each lobby has company. Use All rooms, Standard, or Mania to focus the dashboard. Each room has artwork, approximate progress, a nearby Join button, a queue preview and expandable settings. The compact Live lobbies widget on the left is available throughout the wiki. On smaller screens, tap its heading to open it. The top bar offers Discord and optional Ko-fi donations to keep the project running.

Current room status, player counts, maps, observed queues, settings and join links refresh every ten seconds while the tab is visible. Under People here, Peak observed is the highest complete owner-lobby total recorded since the date shown, using whichever owner rooms were running at each observation. It includes spectators. The record was seeded from earlier five-minute readings and is now checked on each ten-second status export; it persists beyond the rolling chart window. Very short spikes between observations may have been missed. Map artwork comes from the map set when its ID is available. Statistics and occupancy history retain their five-minute schedule. Join links open osu!lazer; room cards also offer a browser fallback.

The progress bar moves continuously between status updates while the tab is visible, and respects reduced-motion preferences. It estimates elapsed song time from an observed match start and the map’s catalog length, including breaks, with a small allowance for the lead-in and finish. Required speed mods adjust the estimate; individual speed changes and network timing can differ. It resets on the next observed match start, including a replay of the same map. Finishing… means the estimate has reached the end while the next match has not yet been observed. The browser checks for an update near the estimated end and continues its regular ten-second refresh.

If the status snapshot becomes more than 35 seconds old, current maps and join controls are withheld until fresh data returns. With JavaScript disabled, artwork and join links use the page’s snapshot; reload for current status.

Graphs show sampled occupancy, including spectators; they describe people present, not simultaneous gameplay. Total players · running lobbies adds the counts for whichever owner lobbies are running at each five-minute observation: one, two, three or four. It uses the same hour, day, week or month window as the room graphs and is independent of the Standard or Mania room-card filter. This is summed room occupancy, not a deduplicated count of unique people who may be connected to several rooms. Explicitly unconfigured slots and confirmed-offline rooms contribute zero; a missing reading from a configured running room still leaves a gap rather than showing a misleading partial total. Historical unknown readings remain unknown; the current room configuration is not applied retrospectively. Peak and average use only complete totals. The recent-observations table includes the same combined total.

In the individual room graphs, zero means an open room with nobody connected. A red mark means the room was confirmed offline at that observation. A break without a red mark means a room reading was unavailable; it does not prove downtime. Gaps longer than 15 minutes also break chart lines. Readings counts valid five-minute occupancy observations for each room, so rooms can have different totals. Observed availability describes the bot service at those sample times, and is not a guarantee that every room was playable between them.

See the lobby guides, player achievements, or how these statistics work.

On October 5, 2026, a code-release switch exposed a local exporter/health-monitor path mismatch. It produced missing-data readings and a false UNHEALTHY alert, rather than proving that the lobbies had crashed. The collectors now read persistent runtime paths independently of the active release, and fresh readings for all four rooms were verified after the fix. Missing or stale data still fails closed as described above; genuine warnings remain visible. Supervisor deployment and operational correction.

Consenting independent hosts now appear alongside the owner presentation on the homepage, this dashboard and the sidebar, with explicit host attribution and shared map cards. Owner occupancy totals and administrative controls remain owner-scoped. Map art and duration resolve centrally without operator-side research collection. An expired, revoked or unavailable community listing does not establish that owner rooms are offline.

Richer remote public settings, observed playing-player counts and Estimated song progress require both a compatible v2 operator client and activation of the qualified central v2 hub; that hub remains staged at the October 14 review. Existing clients can receive central art/duration without an invented song clock. Unknown timing, speed or participant observations stay unknown. See community hosting and display limits.