Boopers
Online 216.189.198.98:28015 checked 11m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 21:38 UTC2d ago | 0 | – | running | 0 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
Quick answers
Tags and filters
Where does Boopers appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Boopers: Rust community servers, going deep and Go deep on PvE servers. The server list shows it under 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 3 days.
How should you read the tags on Boopers?
Boopers's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp100 (Max players): It holds 100 players; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167781 (Build): The build number is 167781; ptrak (Networking): Standard RakNet networking; $r? (Region code): The region field is empty; ^p (PvE): It's player versus environment, so the world poses the risk, not other players. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
What's the location of Boopers?
Boopers does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 216.189.198.98:28015.
Is Boopers up, and how often does it stay online?
Boopers is live as of this check. In the last full 7 days, 51 of 168 hours were online, 30% uptime. The first sighting by Rust Going Deep was on 21 September 2026.
What Rust version is Boopers on?
Rust network protocol 2634 and build 167781 is what Boopers runs, on Linux. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
How often does Boopers wipe?
Boopers's rhythm is unclear because not enough wipes are on record yet. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 2 days 11 hours ago.
What happens on wipe day at Boopers?
Recent wipes have averaged a busiest crowd of 0 players. On the latest wipe, 0 hours passed before the crowd peaked.
Map and rules
What settings and rules have been applied to Boopers?
Its name does not state a gather rate for Boopers. Up to 8 players per group, which is the default. It runs pve, no fighting other players. It sits under Community in the server browser: a community server. VAC is on: Valve's anti-cheat is active.
What's the map on Boopers?
Boopers uses a game-generated procedural map.
Population
Is Boopers busy?
Out of 100 slots, 0 are filled on Boopers right now. Across the last seven days, the typical count has been 0 players.
What's Boopers's rank among Rust servers?
For player hours in the last seven days, Boopers ranks #15,843, within the top 72% of ranked servers.
Getting in
How do you get into Boopers?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 216.189.198.98:28015.