On the class lists: F (30), with population over 48 hours and no performance mark.
Players now0/ 50% full
7-day average1peak 1
Rank#8,436top 38%
Last wipe3d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
11/ 100
F
A quiet classroom so far: 1 of 5 on average. Plenty of space to grow.
Standingrank on player hours
62/ 100
C
Working its way up from the back of the class: #8,436 on player hours.
Uptimehours on the list, last 48
8/ 100
F
Attendance needs work: on the list only 4 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 117 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in performance (A+); uptime is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 38% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
classmates: the same kind of game, then region, group limit, rate and wipes
Rust PvE - Test leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 151.59.81.216:28015.
How reliable is Rust PvE - Test, and is it up?
The server is down: Rust PvE - Test is offline now, with the last sighting 44 hours ago. About 12 hours ago, it restarted, based on the uptime it reports. It was up 1 of 24 hours over the last 1 full day, which is 4% of the time. It was first seen by Rust Server Score on 26 October 2026.
How well does Rust PvE - Test run?
It never fell below 106 server fps in the last 48 hours, averaging 117. At its peak, it held 66,670 entities, including buildings, deployables and all else in the world. Memory use reached up to 1,952 MB. When fps is low and entities climb, that is lag to players.
On what Rust version does Rust PvE - Test sit?
You will find Rust PvE - Test on Rust network protocol 2635 and build 168909, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does Rust PvE - Test reset?
Rust PvE - Test has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 3 days 10 hours.
Player numbers
Where does Rust PvE - Test sit among Rust servers?
Over the last seven days, Rust PvE - Test has #8,436 for player hours, in the top 38% of all ranked servers.
What does the population on Rust PvE - Test look like?
The last sighting of Rust PvE - Test was 44 hours ago, and it is offline right now. It peaked at 1 and averaged 1 players over the last seven days. The busiest time in the last 48 hours was 21:00 UTC, with an average of 1 players.
Tags and filters
How should you read the tags on Rust PvE - Test?
gmrust (Game mode): Survival in the standard Rust style; mp5 (Max players): 5 slots are available; ts5 (Group limit): A team can hold 5 players at most; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags Rust PvE - Test publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does Rust PvE - Test appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Rust PvE - Test among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Map and rules
How is Rust PvE - Test set up, and what rules does it keep?
The name of Rust PvE - Test gives no gather rate. You can play in groups of up to 5 players. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Rust PvE - Test runs which map?
A procedural map of size 3,500 and seed 1337, generated by the game, is what Rust PvE - Test runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to Rust PvE - Test?
Enter client.connect 151.59.81.216:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2635,gmrust,cs168909,ts5,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp5
Max players5 slots are available.
ts5
Group limitA team can hold 5 players at most.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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.
A term to build on. Strongest in performance (A+); uptime is the one to work on (F).