Working its way up from the back of the class: #16,084 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
50/ 100
D
Holding steady: up 27 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
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
StagingLab leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 178.126.210.193:28115.
How dependable is StagingLab, and is it online at the moment?
The server is down: StagingLab is offline now, with the last sighting 28 days 4 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 1 October 2026, Rust Server Score saw it for the first time.
Which Rust version is StagingLab running?
Rust network protocol 2634 and build 166462 on Windows is what StagingLab runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does StagingLab wipe, and how often?
There are too few wipes on record for StagingLab to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 28 days 14 hours.
Population
Where does StagingLab sit among Rust servers?
In the top 69% of all ranked servers, StagingLab sits at #16,084 for player hours over the last seven days.
What does the population on StagingLab look like?
StagingLab is offline at the moment; the last time it was seen was 28 days 4 hours ago.
Tags and filters
What do StagingLab's tags stand for?
You'll see StagingLab tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp800 (Max players): The server holds 800 slots; ts50 (Group limit): Teams cap out at 50; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166462 (Build): Build number: 166462; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; modded (Modded): Plugins or settings alter the game, so it sits under Modded; oxidation (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one in the browser, which picks them up from the server. 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 StagingLab?
These Rust Server Score lists count StagingLab among them: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
How is StagingLab set up, and what rules does it keep?
You will find no gather rate in the name of StagingLab. A group here can reach 50 players. pve is the mode here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Connecting
What is the way to join StagingLab?
Enter client.connect 178.126.210.193:28115 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 asmp800,ptrak,$r?,v2634,^p,gmrust,cs166462,ts50,^o^z,oxidation,modded
Game
gmrust
Game modeRust survival, played by the standard rules.
mp800
Max playersThe server holds 800 slots.
ts50
Group limitTeams cap out at 50.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166462
BuildBuild number: 166462.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
modded
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
oxidation
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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 momentum (D); standing is the one to work on (F).