On the class lists: C− (59), with population over 48 hours and no performance mark.
Players now0/ ?
7-day average0peak –
Rank#15,341top 69%
Last wipe31d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
unmarked
–
No weekly average to mark yet.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,341 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 60 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
49/ 100
D
Slipped a little: down 216 places this week. Nothing a good wipe can't fix.
A steady term.
Strongest in performance (A+); 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
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 17 Sep. 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
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 peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 27 Sep, 23:45 UTC31d ago
0
–
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
A Rust Staging Server leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 51.161.199.206:28051 is the address to use.
How reliable is A Rust Staging Server, and is it up?
The server is up: A Rust Staging Server is online now. About 11 days 18 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
Is A Rust Staging Server smooth to play on?
It averaged 60 server fps over the last 48 hours, with a low of 59. At its peak, it held 113,000 entities, including buildings, deployables and all else in the world. Memory use reached up to 6,095 MB. Players feel lag when fps drops and entities pile up.
Which Rust version is A Rust Staging Server running?
Rust network protocol 2635 and build 168330 on Linux is what A Rust Staging Server runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does A Rust Staging Server wipe, and how often?
There are too few wipes on record for A Rust Staging Server to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 31 days 6 hours.
What happens on A Rust Staging Server when wipe day arrives?
Recent wipes have peaked at 0 players on average. The crowd on the latest wipe was largest 0 hours after it began.
Population
What position does A Rust Staging Server hold in the rankings?
In the top 69% of all ranked servers, A Rust Staging Server sits at #15,341 for player hours over the last seven days.
Is A Rust Staging Server a busy server?
The current population of A Rust Staging Server is 0 players. Over the past seven days, the average player count was 0.
Lists and filters
What is meant by the tags on A Rust Staging Server?
You'll see A Rust Staging Server tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp0 (Max players): Its slot count is 0; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168330 (Build): The game build is 168330; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; oxidation (Custom tag): The owner or a plugin created this tag, so it is not standard Rust 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 A Rust Staging Server?
Rust Server Score lists that include A Rust Staging Server: 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.
Rules and settings
Which rules does A Rust Staging Server enforce, and what are its settings?
The name of A Rust Staging Server gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map A Rust Staging Server uses?
A Rust Staging Server runs a game-generated procedural map at size 4,250, seed 224871. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: Custom Map.
Connecting
What is the way to join A Rust Staging Server?
To connect, start Rust, press F1, and type client.connect 51.161.199.206:28051. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2635,gmrust,cs168330,ts8,oxidation
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp0
Max playersIts slot count is 0.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168330
BuildThe game build is 168330.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Other
oxidation
Custom tagThe owner or a plugin created this tag, so it is not standard Rust.
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 steady term. Strongest in performance (A+); standing is the one to work on (F).