Working its way up from the back of the class: #13,897 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
38/ 100
F
Slipped a little: down 3,206 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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 1 Oct. 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 3h.
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 takes the server's word for its location and does not trace the hardware. 186.94.247.180:28015 is the address to use.
How reliable is RUSTINGEZ_STAGING, and is it up?
You cannot join now: RUSTINGEZ_STAGING is offline, last seen 27 days 21 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 1 October 2026.
What Rust version is RUSTINGEZ_STAGING on?
Rust network protocol 2634 and build 166472 on Windows is what RUSTINGEZ_STAGING runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does RUSTINGEZ_STAGING wipe, and how often?
The estimate for RUSTINGEZ_STAGING's next wipe comes from the force 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 30 days 19 hours. The tags show a monthly wipe schedule.
Player count
What position does RUSTINGEZ_STAGING hold in the rankings?
In the top 60% of all ranked servers, RUSTINGEZ_STAGING sits at #13,897 for player hours over the last seven days.
Is RUSTINGEZ_STAGING a busy server?
RUSTINGEZ_STAGING is offline at the moment; the last time it was seen was 27 days 21 hours ago.
Lists and filters
How should you read the tags on RUSTINGEZ_STAGING?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): 50 slots are available; 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; cs166472 (Build): The game build is 166472; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^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 lists and filters on Rust Server Score show 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.
Map and rules
What settings and rules apply on RUSTINGEZ_STAGING?
You will find no gather rate in the name of RUSTINGEZ_STAGING. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. By its own description it is vanilla: facepunch's own version, with no changed rates, kits or rules. Joining requires premium status on Rust. VAC, Valve's anti-cheat, is enabled.
RUSTINGEZ_STAGING runs which map?
A procedural map of size 4,500 and seed 1628882553, generated by the game, is what RUSTINGEZ_STAGING runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How do you get onto RUSTINGEZ_STAGING?
To connect, start Rust, press F1, and type client.connect 186.94.247.180:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. Joining requires premium status on Rust.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^m,^v,gmrust,cs166472,^q,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max players50 slots are available.
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.
cs166472
BuildThe game build is 166472.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
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 F.