LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
The current map
Thursday 15 October 2026, 21:38 UTC
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
The average peak across its recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
The record holds too few of Boopers's wipes to reveal its rhythm. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. This world dates from 13 days 18 hours.
These are the Rust Live Stats lists Boopers fits: Live Rust community servers and Rust PvE servers, live now. Under the filters Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more; Last wipe: In the last 2 weeks it appears on the server list.
The server browser reads gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): The slot count is 100; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2634 (Protocol): Join only if your game is on protocol 2634; cs167781 (Build): Build: 167781; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): The server sets no region code; ^p (PvE): No player fights another — the danger comes from the world, which Boopers publishes. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
Boopers is carrying 0 players at the moment, with 100 slots in total. Averaged over seven days: 0 players.
On player hours for the past seven days, Boopers sits at #15,341, inside the top 69% of ranked servers.
Nothing in the name of Boopers states a gather rate. Eight players per group, which is the game's default. It runs pve, no fighting other players. You find it under Community in the server browser. VAC is enabled: Valve's anti-cheat.
A procedural map, generated by the game, runs on Boopers.
No region is published by Boopers. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. 216.189.198.98:28015 is its address.
Boopers operates on Linux with Rust network protocol 2634 and build 167781. Joining requires the same protocol on your game; Steam takes care of updating it.
Right now Boopers is online. 167 of 168 hours were online in the last 7 full days, giving 99% uptime. On 21 September 2026, Rust Live Stats saw it for the first time.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 216.189.198.98:28015.