Working its way up from the back of the class: #14,477 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 307 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.
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 66% 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
In what location does Rust Frontier | Private Survival sit?
Rust Frontier | Private Survival leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 73.121.194.222:28015.
How reliable is Rust Frontier | Private Survival, and is it up?
You cannot join now: Rust Frontier | Private Survival is offline, last seen 16 days 17 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 12 October 2026, Rust Server Score saw it for the first time.
What Rust version is Rust Frontier | Private Survival on?
Rust network protocol 2634 and build 167584 on Windows is what Rust Frontier | Private Survival runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does Rust Frontier | Private Survival wipe its map?
The record holds too few of Rust Frontier | Private Survival's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 16 days 19 hours have passed since this world was made.
Player count
What position does Rust Frontier | Private Survival hold in the rankings?
In the top 66% of all ranked servers, Rust Frontier | Private Survival sits at #14,477 for player hours over the last seven days.
What does the population on Rust Frontier | Private Survival look like?
It has been 16 days 17 hours since Rust Frontier | Private Survival was last seen, and it is offline right now.
Tags
What do Rust Frontier | Private Survival's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): 20 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167584 (Build): Build number: 167584; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set are the tags Rust Frontier | Private Survival publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature Rust Frontier | Private Survival?
These Rust Server Score lists count Rust Frontier | Private Survival among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
How is Rust Frontier | Private Survival set up, and what rules does it keep?
You will find no gather rate in the name of Rust Frontier | Private Survival. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Rust Frontier | Private Survival?
A procedural map, generated by the game, is what Rust Frontier | Private Survival runs.
Connecting
How should you connect to Rust Frontier | Private Survival?
Enter client.connect 73.121.194.222: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 asmp20,ptrak,$r?,v2634,gmrust,cs167584,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp20
Max players20 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167584
BuildBuild number: 167584.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
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).