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 7h.
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
You'll find no region listed by RUSTINGEZ_STAGING. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 190.206.235.241: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 29 days 15 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 29 September 2026.
Which Rust version is RUSTINGEZ_STAGING running?
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
How frequently does RUSTINGEZ_STAGING wipe its map?
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 14 hours. Its tags record that it wipes monthly.
Player count
Where does RUSTINGEZ_STAGING place in the wider field of Rust servers?
Over the last seven days, RUSTINGEZ_STAGING has #14,441 for player hours, in the top 60% of all ranked servers.
What does the population on RUSTINGEZ_STAGING look like?
The last sighting of RUSTINGEZ_STAGING was 29 days 15 hours ago, and it is offline right now.
Tags
How should you read the tags on RUSTINGEZ_STAGING?
You'll see RUSTINGEZ_STAGING tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166065 (Build): This runs on build 166065; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^q (Premium): You need Rust's premium status to get in in the browser, which picks them up from the server. 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.
Server rules
Which rules does RUSTINGEZ_STAGING enforce, and what are its settings?
Nothing in the name of RUSTINGEZ_STAGING states a gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in 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. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. You need Rust's premium status to get in. The server runs Valve's anti-cheat, VAC.
RUSTINGEZ_STAGING runs which map?
RUSTINGEZ_STAGING runs a procedural map, which the game generates.
Getting in
How should you connect to RUSTINGEZ_STAGING?
To connect, start Rust, press F1, and type client.connect 190.206.235.241:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You need Rust's premium status to get in.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^m,^v,gmrust,cs166065,^q,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166065
BuildThis runs on build 166065.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^q
PremiumYou need Rust's premium status to get in.
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.