W.H.O.P. PVE Test
Offline 67.11.72.237:28015 checked 43d ago
Measurements
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
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| 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.
Quick answers
Player counts
How does W.H.O.P. PVE Test rank against other Rust servers?
The last seven days of player hours place W.H.O.P. PVE Test at #15,126, within the top – of all ranked servers.
How busy is W.H.O.P. PVE Test?
We have no live count for W.H.O.P. PVE Test right now. It was last seen 43 days 21 hours ago.
Lists and tags
What do the server tags on W.H.O.P. PVE Test mean?
These are the tags W.H.O.P. PVE Test publishes, as read by the game's server browser: gmvanilla (Game mode): This is vanilla survival; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team is the default limit; v2633 (Protocol): The protocol is 2633; a different version will not connect; cs163207 (Build): Game build: 163207; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): The region code is left blank; ^p (PvE): Other players are not a threat; the danger comes from the world; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded; ^y (Carbon): A plugin framework, Carbon, is in use. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include W.H.O.P. PVE Test?
These Rust Population lists include W.H.O.P. PVE Test: Modded Rust servers, counted and PvE servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.
Wipe notes
What is the wipe schedule on W.H.O.P. PVE Test?
Its rhythm cannot be told yet: too few of W.H.O.P. PVE Test's wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 51 days ago the current world was made.
Settings
What are the rules and settings on W.H.O.P. PVE Test?
Nothing in W.H.O.P. PVE Test's name says how gather works. No limit is set beyond the standard 8 players per group. You get pve here, no player combat. You find it under Modded, since plugins or settings change how it plays. The plugins it runs are Carbon. VAC, Valve's anti-cheat, runs here.
Server details
Which version of Rust does W.H.O.P. PVE Test run?
The setup is Rust network protocol 2633 and build 163207 on Windows for W.H.O.P. PVE Test. Steam updates your game automatically, but you need the same protocol to join.
Is W.H.O.P. PVE Test online, and how reliable is it?
Offline at the moment, W.H.O.P. PVE Test was last seen 43 days 21 hours ago. It was up 0% of the time over the last 7 full days, 0 out of 168 hours. On 13 September 2026, Rust Population saw it for the first time.
Where is W.H.O.P. PVE Test located?
No region is published by W.H.O.P. PVE Test. The location a server claims is what Rust Population shows, not the place where the machine stands. 67.11.72.237:28015 is where it lives.
How to join
How do I join W.H.O.P. PVE Test?
Either enter client.connect 67.11.72.237:28015 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.