PvE test
Offline 79.127.169.75:28015 checked 15d 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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
- 17/ 100
- 192/ 400
- 124/ 225
- 121/ 100
- 186/ 1000
- 11/ 700
Quick answers
Tags and listings
Where does PvE test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include PvE test: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on PvE test?
gmrust (Game mode): This is the standard Rust survival experience; mp4 (Max players): There are 4 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): To join, your game has to be on protocol 2634; cs166586 (Build): The build number is 166586; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game — that is the tag list PvE test 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 PvE test in?
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. To connect, use 79.127.169.75:28015.
What's the uptime like for PvE test?
Right now PvE test is offline, having last been seen 15 days 7 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. Rust Going Deep has had it on record since 2 October 2026.
What is the Rust version for PvE test?
On Windows, PvE test runs Rust network protocol 2634 and build 166586. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
What schedule does PvE test follow for wipes?
PvE test's rhythm is unclear because not enough wipes are on record yet. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 15 days 19 hours ago.
Map and rules
What settings are in place on PvE test?
No gather rate appears in the name of PvE test. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Oxide. VAC, Valve's anti-cheat, is enabled.
What's the map on PvE test?
PvE test uses a game-generated procedural map.
Population
How many players are on PvE test?
Right now PvE test is offline, with its last appearance 15 days 7 hours ago.
What's PvE test's rank among Rust servers?
Over the last seven days, PvE test is #15,958 by player hours, among the top 70% of all ranked servers.
Join info
How do you get into PvE test?
Open Rust and press F1, then type client.connect 79.127.169.75:28015. Alternatively, click Launch Rust on this page to join via Steam.