Working its way up from the back of the class: #16,717 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,763 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (F); 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
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 70% 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
Next wipe Thursday 5 November, 19:00 UTC, in 8d 19h.
The 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
EU · groups of 150+ · 1x · monthly · 132 on average
40 / 300
Quick answers
from the figures on this page
Server facts
Which region is stagingtest based in?
stagingtest leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 217.155.45.48:28015 is the address to use.
Is stagingtest up, and how steady is its uptime?
At this moment, stagingtest is offline; the last time it was seen was 27 days 2 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 30 September 2026.
Which Rust version is stagingtest running?
Rust network protocol 2634 and build 166406 on Windows is what stagingtest runs. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does stagingtest wipe its map?
the force wipe gives the basis for estimating stagingtest's next wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. The world it runs now was created 27 days 3 hours. The tags show a monthly wipe schedule.
Player numbers
Where does stagingtest sit among Rust servers?
Over the last seven days, stagingtest has #16,717 for player hours, in the top 70% of all ranked servers.
How many players does stagingtest usually have?
It has been 27 days 2 hours since stagingtest was last seen, and it is offline right now.
Tags
What do stagingtest's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp2 (Max players): 2 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166406 (Build): Build number: 166406; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes are the tags stagingtest publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature stagingtest?
These Rust Server Score lists count stagingtest among them: Best community servers, graded and Vanilla Rust servers, graded. You can find it under these server-list filters: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Monthly ^m and Vanilla ^v; Group limit: 5 or more; Wipe schedule: Monthly.
Server rules
What settings and rules apply on stagingtest?
Nothing in the name of stagingtest states a gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. The vanilla label is its own: you get the unmodified game: no rate changes, no kits, no rule changes. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map stagingtest uses?
stagingtest runs a procedural map, which the game generates.
How to join
How do you get onto stagingtest?
Enter client.connect 217.155.45.48: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,^m,^v,gmrust,cs166406,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp2
Max players2 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166406
BuildBuild number: 166406.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
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 momentum (F); standing is the one to work on (F).