RUST METRICSFlight deck · live data
Data live Servers11,737 Players71,230 Populated3,632 Fresh wipes 3 h135 Scan5 min
‹ All servers67.11.72.237:28015
Offline Full Queue Fresh wipe Wipe due No query

W.H.O.P. PVE Test

Offline 67.11.72.237:28015 checked 44d ago

moddedcarbonpve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,126no region published
Last wipe51d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep
PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

When does W.H.O.P. PVE Test wipe?

To tell the rhythm of W.H.O.P. PVE Test, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 51 days 14 hours ago the current world was made.

Lists and filters

How should you read the tags on W.H.O.P. PVE Test?

Check: tags. The game's server browser reads gmvanilla (Game mode): Check: mode. Vanilla survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163207 (Build): Game build reading: 163207; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^p (PvE): No fighting between players: the world itself is the hazard; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon from W.H.O.P. PVE Test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show W.H.O.P. PVE Test?

These Rust Metrics lists carry W.H.O.P. PVE Test: Modded Rust servers, checked live and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.

Population

Where does W.H.O.P. PVE Test sit in the rankings?

Ranking for W.H.O.P. PVE Test: #15,126 on seven-day player hours, top – of all ranked servers.

What player count does W.H.O.P. PVE Test carry?

W.H.O.P. PVE Test is not responding; status offline, last seen 44 days 11 hours ago.

Server details

Where does W.H.O.P. PVE Test sit?

No region comes from W.H.O.P. PVE Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 67.11.72.237:28015.

What Rust version is W.H.O.P. PVE Test on?

Version check: Rust network protocol 2633 and build 163207 on Windows, run by W.H.O.P. PVE Test. Matching protocol is required to join. Let Steam update your game.

What is the uptime on W.H.O.P. PVE Test, and is it online?

Check: connection. W.H.O.P. PVE Test is offline at this moment. Last contact was 44 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

What settings and rules apply on W.H.O.P. PVE Test?

No gather rate appears in the name: W.H.O.P. PVE Test. The group cap is 8 players, which is the default in the game. The mode is pve. Note the following: no combat against other players. Plugins or settings change the game, so it is listed as Modded. Plugin count: Carbon. VAC is on. That is Valve's anti-cheat.

Join

How do you connect to W.H.O.P. PVE Test?

Press F1 in Rust and enter client.connect 67.11.72.237:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,^z,^y,^p,gmvanilla,cs163207,ts8

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163207
Build Game build reading: 163207.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Plugin framework in use: Carbon.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.