Working its way up from the back of the class: #15,326 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
49/ 100
D
Slipped a little: down 201 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); 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.
AveragePeakWipe
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
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 24 Sep, 10:41 UTC35d ago
0
–
running
0
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
Where in the world is Facepunch Staging Auto Restart 10 minutes | Nav Disabled?
Facepunch Staging Auto Restart 10 minutes | Nav Disabled 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 57.128.211.49:28019.
How dependable is Facepunch Staging Auto Restart 10 minutes | Nav Disabled, and is it online at the moment?
You cannot join now: Facepunch Staging Auto Restart 10 minutes | Nav Disabled is offline, last seen 2 days ago. It was up 134 of 168 hours over the last 7 full days, which is 80% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Which Rust version is Facepunch Staging Auto Restart 10 minutes | Nav Disabled running?
You will find Facepunch Staging Auto Restart 10 minutes | Nav Disabled on Rust network protocol 2635 and build 169317, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does Facepunch Staging Auto Restart 10 minutes | Nav Disabled wipe its map?
Facepunch Staging Auto Restart 10 minutes | Nav Disabled has not had enough wipes recorded to reveal 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 35 days 3 hours.
What happens on Facepunch Staging Auto Restart 10 minutes | Nav Disabled when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 0 hours into the latest wipe.
Population
What position does Facepunch Staging Auto Restart 10 minutes | Nav Disabled hold in the rankings?
In the top 69% of all ranked servers, Facepunch Staging Auto Restart 10 minutes | Nav Disabled sits at #15,326 for player hours over the last seven days.
How many players does Facepunch Staging Auto Restart 10 minutes | Nav Disabled usually have?
Facepunch Staging Auto Restart 10 minutes | Nav Disabled is offline at the moment; the last time it was seen was 2 days ago. A seven-day average of 0 players applies here.
Lists and filters
How should you read the tags on Facepunch Staging Auto Restart 10 minutes | Nav Disabled?
official (official): Run by Facepunch or one of its partners: the servers in Rust's Official tab. Rust does not publish this, so it is kept by hand; gmrust (Game mode): Survival in the standard Rust style; mp0 (Max players): 0 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs169317 (Build): The game build is 169317; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server are the tags Facepunch Staging Auto Restart 10 minutes | Nav Disabled publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Who operates Facepunch Staging Auto Restart 10 minutes | Nav Disabled?
The same operator most likely runs Facepunch Staging Auto Restart 10 minutes | Nav Disabled and the 124 other servers we track that also publish a playrust.com hostname.
Which Rust Server Score filters and lists feature Facepunch Staging Auto Restart 10 minutes | Nav Disabled?
These Rust Server Score lists count Facepunch Staging Auto Restart 10 minutes | Nav Disabled among them: Official Rust servers, graded. These filters bring it up on the server list: Type: No plugins at all; Group limit: 5 or more; Boxes: Official only.
Server rules
What settings and rules apply on Facepunch Staging Auto Restart 10 minutes | Nav Disabled?
You will find no gather rate in the name of Facepunch Staging Auto Restart 10 minutes | Nav Disabled. 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. Fighting and raiding between players are both allowed. The in-game Official tab of Rust includes it. The server runs Valve's anti-cheat, VAC.
Which map is in play on Facepunch Staging Auto Restart 10 minutes | Nav Disabled?
Facepunch Staging Auto Restart 10 minutes | Nav Disabled runs a game-generated procedural map at size 4,500, seed 9563351. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
What is the way to join Facepunch Staging Auto Restart 10 minutes | Nav Disabled?
To connect, start Rust, press F1, and type client.connect 57.128.211.49:28019. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2635,gmrust,cs169317,ts8
Run by Facepunch or one of its partners: the servers in Rust's Official tab. Rust does not publish this, so it is kept by hand.
Game
gmrust
Game modeSurvival in the standard Rust style.
mp0
Max players0 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs169317
BuildThe game build is 169317.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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 (D); standing is the one to work on (F).