Working its way up from the back of the class: #15,432 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
35/ 100
F
Slipped a little: down 4,577 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.
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 69% 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
No region is published for Solo Frontier | SOLO. Rust Server Score takes the server's word for its location and does not trace the hardware. 95.46.137.23:28025 is the address to use.
How dependable is Solo Frontier | SOLO, and is it online at the moment?
You cannot join now: Solo Frontier | SOLO is offline, last seen 8 days 8 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 21 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Solo Frontier | SOLO sit?
You will find Solo Frontier | SOLO on Rust network protocol 2634 and build 166494, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does Solo Frontier | SOLO wipe its map?
There are too few wipes on record for Solo Frontier | SOLO to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 28 days 4 hours have passed since this world was made.
Player count
Where does Solo Frontier | SOLO sit among Rust servers?
In the top 69% of all ranked servers, Solo Frontier | SOLO sits at #15,432 for player hours over the last seven days.
Is Solo Frontier | SOLO a busy server?
Solo Frontier | SOLO is offline at the moment; the last time it was seen was 8 days 8 hours ago.
Tags
What do Solo Frontier | SOLO's tags stand for?
You'll see Solo Frontier | SOLO tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): Its slot count is 20; ts0 (Group limit): The team system is turned off; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): Build number: 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here 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.
Where does Solo Frontier | SOLO appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Solo Frontier | SOLO among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y.
Map and rules
What settings and rules apply on Solo Frontier | SOLO?
Nothing in the name of Solo Frontier | SOLO states a gather rate. You will find no published group limit. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Solo Frontier | SOLO uses?
A procedural map, generated by the game, is what Solo Frontier | SOLO runs.
How to join
How should you connect to Solo Frontier | SOLO?
To connect, start Rust, press F1, and type client.connect 95.46.137.23:28025. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2634,gmrust,cs166494,ts0,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp20
Max playersIts slot count is 20.
ts0
Group limitThe team system is turned off.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildBuild number: 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonCarbon provides the plugin framework here.
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.