W.H.O.P. PVE Test
Offline 67.11.72.237:28015 checked 33d 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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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
- 358/ 2000
- 413/ 2000
- 94/ 200
- 68/ 200
- 81/ 200
- 147/ 250
Quick answers
Tags and filters
Where does W.H.O.P. PVE Test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include W.H.O.P. PVE Test: Modded Rust servers and Go deep on PvE servers. Its entry appears under the filters Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the tags on W.H.O.P. PVE Test?
W.H.O.P. PVE Test's game browser tags read: gmvanilla (Game mode): It's vanilla survival; mp10 (Max players): The slot count is 10; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs163207 (Build): It's on build 163207; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^p (PvE): Other players aren't a threat; the world is; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game; ^y (Carbon): Carbon is the plugin framework it uses. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What's the location of W.H.O.P. PVE Test?
W.H.O.P. PVE Test does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 67.11.72.237:28015.
Is W.H.O.P. PVE Test up, and how often does it stay online?
Right now W.H.O.P. PVE Test is offline, having last been seen 33 days 20 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 13 September 2026.
What Rust version is W.H.O.P. PVE Test on?
On Windows, W.H.O.P. PVE Test runs Rust network protocol 2633 and build 163207. The protocol must match to join; Steam will update your game.
Wipe details
What schedule does W.H.O.P. PVE Test follow for wipes?
Too few wipes are on record for W.H.O.P. PVE Test to show its rhythm. 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 40 days 22 hours ago.
Map and rules
What settings are in place on W.H.O.P. PVE Test?
Its name does not state a gather rate for W.H.O.P. PVE Test. Up to 8 players per group, which is the default. pve is the game mode, no fighting other players. The server browser puts it under Modded, as plugins or settings alter the game. Carbon plugins are running here. VAC is on: Valve's anti-cheat is active.
Player stats
What's the population like on W.H.O.P. PVE Test?
W.H.O.P. PVE Test was last seen 33 days 20 hours ago and is offline as you read this.
What's W.H.O.P. PVE Test's rank among Rust servers?
For player hours in the last seven days, W.H.O.P. PVE Test ranks #15,126, within the top – of ranked servers.
How to join
How do you get into W.H.O.P. PVE Test?
Open Rust and press F1, then type client.connect 67.11.72.237:28015. Alternatively, click Launch Rust on this page to join via Steam.