On the class lists: F (40), with population over 48 hours and no performance mark.
Players now0/ 1500% full
7-day average0peak –
Rank#15,373top 69%
Last wipe34d 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 150 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,373 on player hours.
Uptimehours on the list, last 48
79/ 100
B
Missed a few lessons: on the list 38 of the last 48 hours.
Performanceserver fps, last 48 hours
2/ 100
F
Needs to work on its frame rate: 1 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 200 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (B); 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.
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
Thu 24 Sep, 10:41 UTC34d 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
staging leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 151.80.25.50:28013 is the address to use.
Is staging up, and how steady is its uptime?
The server is up: staging is online now. According to its reported uptime, the last restart was about 15 minutes ago. It was up 160 of 168 hours over the last 7 full days, which is 95% of the time. It was first seen by Rust Server Score on 13 September 2026.
Is staging smooth to play on?
The average over the last 48 hours was 1 server fps, and it never went below 1. Up to 119,000 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 1,739 MB. Players feel lag when fps drops and entities pile up.
Which Rust version is staging running?
You will find staging on Rust network protocol 2635 and build 169545, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does staging wipe its map?
staging has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 34 days 7 hours have passed since this world was made.
What should you expect from wipe day on staging?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does staging sit among Rust servers?
In the top 69% of all ranked servers, staging sits at #15,373 for player hours over the last seven days.
What does the population on staging look like?
staging is showing 0 players right now, with 150 slots in total. A seven-day average of 0 players applies here.
Tags
What do staging's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp150 (Max players): 150 slots are available; 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; cs169545 (Build): Build number: 169545; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server are the tags staging publishes, and the game's server browser reads them. 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 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include staging: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
What settings and rules apply on staging?
You will find no gather rate in the name of staging. The default of 8 players applies as the group cap. 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. The server runs Valve's anti-cheat, VAC.
Can you tell me which map staging uses?
staging runs a game-generated procedural map at size 4,500, seed 59991. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How do you get onto staging?
Enter client.connect 151.80.25.50:28013 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 asmp150,ptrak,$r?,v2635,gmrust,cs169545,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp150
Max players150 slots are available.
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.
cs169545
BuildBuild number: 169545.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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 uptime (B); population is the one to work on (F).