Chris's Private PvE
Offline 66.30.204.52:28015 checked 28d 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
- 6/ 100
- 82/ 400
- 46/ 245
- 132/ 100
- 125/ 1000
- 12/ 700
Quick answers
Tags and filters
Where does Chris's Private PvE appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Chris's Private PvE are: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the tags on Chris's Private PvE?
gmrust (Game mode): This is the standard Rust survival experience; mp2 (Max players): The slot count is 2; 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; cs164530 (Build): The build number is 164530; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game; ^y (Carbon): Carbon is the plugin framework it uses — that is the tag list Chris's Private PvE puts out for the game's server browser. 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 location is Chris's Private PvE in?
Chris's Private PvE does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. To connect, use 66.30.204.52:28015.
What's the uptime like for Chris's Private PvE?
Chris's Private PvE is down at the moment; it was last up 28 days 8 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. Rust Going Deep has had it on record since 19 September 2026.
What is the Rust version for Chris's Private PvE?
On Windows, Chris's Private PvE runs Rust network protocol 2633 and build 164530. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
What schedule does Chris's Private PvE follow for wipes?
The wipes recorded for Chris's Private PvE are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 28 days 12 hours ago.
Settings and map
Which rules and settings is Chris's Private PvE running?
No gather rate appears in the name of Chris's Private PvE. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. Plugins or settings change the game, so the browser lists it as Modded. Plugins in use: Carbon. The server runs Valve's anti-cheat, VAC.
Which map is active on Chris's Private PvE?
A procedural map, generated by the game, is in play on Chris's Private PvE.
Population
How many players are on Chris's Private PvE?
The last sighting of Chris's Private PvE was 28 days 8 hours ago; it is offline right now.
What's Chris's Private PvE's rank among Rust servers?
For player hours in the last seven days, Chris's Private PvE ranks #13,254, within the top – of ranked servers.
How to join
What's the process to join Chris's Private PvE?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 66.30.204.52:28015.