Working its way up from the back of the class: #16,330 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
32/ 100
F
Lost ground: down 5,740 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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 best
RankRank in region
Top 69% 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
Local PVE Staging leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 65.18.215.85:28025 is the address to use.
Is Local PVE Staging up, and how steady is its uptime?
At this moment, Local PVE Staging is offline; the last time it was seen was 27 days 22 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 30 September 2026.
Which Rust version is Local PVE Staging running?
The server Local PVE Staging is on Rust network protocol 2634 and build 166461 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does Local PVE Staging wipe its map?
The record holds too few of Local PVE Staging's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 29 days 1 hours.
Player numbers
Where does Local PVE Staging sit among Rust servers?
In the top 69% of all ranked servers, Local PVE Staging sits at #16,330 for player hours over the last seven days.
How many players does Local PVE Staging usually have?
The last sighting of Local PVE Staging was 27 days 22 hours ago, and it is offline right now.
Tags and filters
What is meant by the tags on Local PVE Staging?
The game's browser takes its cue from the tags Local PVE Staging has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): Its slot count is 10; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166461 (Build): The game build is 166461; 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): 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.
Where does Local PVE Staging appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Local PVE Staging: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
How is Local PVE Staging set up, and what rules does it keep?
Nothing in the name of Local PVE Staging states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. 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.
Local PVE Staging runs which map?
A procedural map, generated by the game, is what Local PVE Staging runs.
How to join
How should you connect to Local PVE Staging?
To connect, start Rust, press F1, and type client.connect 65.18.215.85:28025. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs166461,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersIts slot count is 10.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166461
BuildThe game build is 166461.
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
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 term to build on. Even marks across the subjects, from F to F.