Working its way up from the back of the class: #14,441 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
46/ 100
D
Slipped a little: down 1,222 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 60% 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 7d 10h.
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
RUSTINGEZ_STAGING leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 200.84.42.127:28015 is the address to use.
Is RUSTINGEZ_STAGING up, and how steady is its uptime?
You cannot join now: RUSTINGEZ_STAGING is offline, last seen 29 days 11 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 29 September 2026, Rust Server Score saw it for the first time.
What Rust version is RUSTINGEZ_STAGING on?
The server RUSTINGEZ_STAGING is on Rust network protocol 2634 and build 166065 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does RUSTINGEZ_STAGING reset?
the force wipe gives the basis for estimating RUSTINGEZ_STAGING's next wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 30 days 11 hours have passed since this world was made. Its tags list a monthly wipe schedule.
Population
Where does RUSTINGEZ_STAGING sit among Rust servers?
Over the last seven days, RUSTINGEZ_STAGING has #14,441 for player hours, in the top 60% of all ranked servers.
Is RUSTINGEZ_STAGING a busy server?
The last sighting of RUSTINGEZ_STAGING was 29 days 11 hours ago, and it is offline right now.
Tags and filters
What is meant by the tags on RUSTINGEZ_STAGING?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): Its slot count is 50; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166065 (Build): The game build is 166065; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^q (Premium): Joining requires premium status on Rust are the tags RUSTINGEZ_STAGING 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 RUSTINGEZ_STAGING?
Rust Server Score lists that include RUSTINGEZ_STAGING: Best community servers, graded and Vanilla Rust servers, graded. These filters bring it up on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Game mode: Premium; Server tag: Monthly ^m, Vanilla ^v and Premium ^q; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
What settings and rules apply on RUSTINGEZ_STAGING?
You will find no gather rate in the name of RUSTINGEZ_STAGING. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. Joining requires premium status on Rust. VAC, Valve's anti-cheat, is enabled.
Which map is in play on RUSTINGEZ_STAGING?
A procedural map, generated by the game, is what RUSTINGEZ_STAGING runs.
Connecting
How should you connect to RUSTINGEZ_STAGING?
Enter client.connect 200.84.42.127:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. Joining requires premium status on Rust.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^m,^v,gmrust,cs166065,^q,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersIts slot count is 50.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166065
BuildThe game build is 166065.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Mods and access
^q
PremiumJoining requires premium status on 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 term to build on. Even marks across the subjects, from F to D.