On the class lists: D (54), with population over 48 hours and no performance mark.
Players now0/ 300% full
7-day average1peak 12
Rank#3,891top 18%
Last wipe24d agomonthly schedule
Next wipe8d 22hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
2/ 100
F
A quiet classroom so far: 1 of 30 on average. Plenty of space to grow.
Standingrank on player hours
82/ 100
B+
Holds a respectable place: #3,891 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 95 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
36/ 100
F
Slipped a little: down 1,057 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (A+); population 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
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 5 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 18% 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
Next wipe Thursday 5 November, 19:00 UTC, in 8d 22h.
The 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
VoidOrder_PVEServer leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 131.129.135.38:28015.
How dependable is VoidOrder_PVEServer, and is it online at the moment?
Right now, VoidOrder_PVEServer is online. According to its reported uptime, the last restart was about 3 days 8 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. On 5 October 2026, Rust Server Score saw it for the first time.
Does VoidOrder_PVEServer perform well?
It never fell below 69 server fps in the last 48 hours, averaging 95. At its peak, it held 144,935 entities, including buildings, deployables and all else in the world. Memory use reached up to 4,379 MB. Players feel lag when fps drops and entities pile up.
On what Rust version does VoidOrder_PVEServer sit?
The server VoidOrder_PVEServer is on Rust network protocol 2635 and build 168909 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does VoidOrder_PVEServer wipe, and how often?
the force wipe gives the basis for estimating VoidOrder_PVEServer's next wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 24 days 12 hours have passed since this world was made. Its tags list a monthly wipe schedule.
Population
Where does VoidOrder_PVEServer sit among Rust servers?
In the top 18% of all ranked servers, VoidOrder_PVEServer sits at #3,891 for player hours over the last seven days.
Is VoidOrder_PVEServer a busy server?
Right now, 0 players are on VoidOrder_PVEServer, which has 30 slots. The seven-day average is 1 players, with a peak of 12. The busiest time in the last 48 hours was 15:00 UTC, with an average of 1 players.
Tags
What is meant by the tags on VoidOrder_PVEServer?
The game's browser takes its cue from the tags VoidOrder_PVEServer has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp30 (Max players): The server holds 30 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show VoidOrder_PVEServer?
These Rust Server Score lists count VoidOrder_PVEServer among them: Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
How is VoidOrder_PVEServer set up, and what rules does it keep?
The name of VoidOrder_PVEServer gives no gather rate. The default of 8 players applies as the group cap. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
VoidOrder_PVEServer runs which map?
The game generates the procedural map on VoidOrder_PVEServer at size 4,500 with seed 1234567. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
What is the way to join VoidOrder_PVEServer?
To connect, start Rust, press F1, and type client.connect 131.129.135.38:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://x.com/s_darts0425.
Server tags
what each one means
Published asmp30,ptrak,$r?,v2635,^m,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp30
Max playersThe server holds 30 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).