Working its way up from the back of the class: #14,544 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
42/ 100
F
Slipped a little: down 2,380 places this week. Nothing a good wipe can't fix.
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.
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 64% 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
My Staging Test Server 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 31.59.205.12:28015.
How reliable is My Staging Test Server, and is it up?
You cannot join now: My Staging Test Server is offline, last seen 24 days 16 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 4 October 2026.
Which Rust version is My Staging Test Server running?
The server My Staging Test Server is on Rust network protocol 2634 and build 166629 under Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
When does My Staging Test Server wipe, and how often?
There are too few wipes on record for My Staging Test Server to show a 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 34 days 15 hours.
Player numbers
Where does My Staging Test Server sit among Rust servers?
In the top 64% of all ranked servers, My Staging Test Server sits at #14,544 for player hours over the last seven days.
How many players does My Staging Test Server usually have?
It has been 24 days 16 hours since My Staging Test Server was last seen, and it is offline right now.
Tags
What is meant by the tags on My Staging Test Server?
The game's browser takes its cue from the tags My Staging Test Server has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166629 (Build): The game build is 166629; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does My Staging Test Server appear in the Rust Server Score lists and filters?
Rust Server Score lists that include My Staging Test Server: 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.
Map and rules
Which rules does My Staging Test Server enforce, and what are its settings?
The name of My Staging Test Server gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
My Staging Test Server runs which map?
My Staging Test Server runs a procedural map, which the game generates.
Getting in
What is the way to join My Staging Test Server?
To connect, start Rust, press F1, and type client.connect 31.59.205.12:28015. 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,cs166629,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166629
BuildThe game build is 166629.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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.