On the class lists: D (50), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average0peak 2
Rank#11,166top 50%
Last wipe6d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 40 on average. Plenty of space to grow.
Standingrank on player hours
50/ 100
D
Working its way up from the back of the class: #11,166 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (D); 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
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.
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 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 50% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W····
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 13 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 21 Oct, 10:39 UTC6d ago
2
–
running
0
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
STAGING STAGING16368 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 5.196.124.159:10004.
How reliable is STAGING STAGING16368, and is it up?
At this moment, STAGING STAGING16368 is offline; the last time it was seen was 5 days ago. It was up 38 of 168 hours over the last 7 full days, which is 23% of the time. The first sighting by Rust Server Score was on 1 October 2026.
What Rust version is STAGING STAGING16368 on?
You will find STAGING STAGING16368 on Rust network protocol 2635 and build 168806, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does STAGING STAGING16368 wipe its map?
The record holds too few of STAGING STAGING16368's wipes to tell 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 6 days 13 hours.
What happens on STAGING STAGING16368 when wipe day arrives?
Across its recent wipes, the busiest moments averaged 2 players. The crowd on the latest wipe was largest 13 hours after it began.
Population
What position does STAGING STAGING16368 hold in the rankings?
In the top 50% of all ranked servers, STAGING STAGING16368 sits at #11,166 for player hours over the last seven days.
How many players does STAGING STAGING16368 usually have?
The last sighting of STAGING STAGING16368 was 5 days ago, and it is offline right now. Averaging 0 players over seven days, it peaked at 2.
Lists and filters
What is meant by the tags on STAGING STAGING16368?
The game's browser takes its cue from the tags STAGING STAGING16368 has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp40 (Max players): Its slot count is 40; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168806 (Build): The game build is 168806; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does STAGING STAGING16368 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count STAGING STAGING16368 among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
Server rules
Which rules does STAGING STAGING16368 enforce, and what are its settings?
You will find no gather rate in the name of STAGING STAGING16368. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is enabled.
STAGING STAGING16368 runs which map?
The game generates the procedural map on STAGING STAGING16368 at size 4,000 with seed 32512311. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto STAGING STAGING16368?
To connect, start Rust, press F1, and type client.connect 5.196.124.159:10004. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,gmrust,cs168806,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp40
Max playersIts slot count is 40.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168806
BuildThe game build is 168806.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
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 standing (D); population is the one to work on (F).