Working its way up from the back of the class: #13,869 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
48/ 100
D
Slipped a little: down 603 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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 61% 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 leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 72.56.14.104:28015.
How reliable is My Staging Test, and is it up?
At this moment, My Staging Test is offline; the last time it was seen was 25 days 6 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 3 October 2026, Rust Server Score saw it for the first time.
On what Rust version does My Staging Test sit?
You will find My Staging Test on Rust network protocol 2634 and build 166655, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does My Staging Test wipe its map?
The record holds too few of My Staging Test'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. The world it runs now was created 25 days 7 hours.
Player count
Where does My Staging Test sit among Rust servers?
In the top 61% of all ranked servers, My Staging Test sits at #13,869 for player hours over the last seven days.
What does the population on My Staging Test look like?
My Staging Test is offline at the moment; the last time it was seen was 25 days 6 hours ago.
Lists and filters
How should you read the tags on My Staging Test?
You'll see My Staging Test tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp2 (Max players): Its slot count is 2; 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; cs166655 (Build): Build number: 166655; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here in the browser, which picks them up from the 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 My Staging Test appear in the Rust Server Score lists and filters?
Rust Server Score lists that include My Staging Test: 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.
Map and rules
What settings and rules apply on My Staging Test?
You will find no gather rate in the name of My Staging Test. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
My Staging Test runs which map?
My Staging Test runs a procedural map, which the game generates.
How to join
What is the way to join My Staging Test?
Enter client.connect 72.56.14.104:28015 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 asmp2,ptrak,$r?,v2634,gmrust,cs166655,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp2
Max playersIts slot count is 2.
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.
cs166655
BuildBuild number: 166655.
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 D.