Working its way up from the back of the class: #15,222 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
39/ 100
F
Slipped a little: down 3,240 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.
AveragePeak
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 70% 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 Solo Frontier | NEW MAIN | Проверка sit?
No region tag appears for Solo Frontier | NEW MAIN | Проверка, but the name suggests Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 95.182.104.60:28025.
How reliable is Solo Frontier | NEW MAIN | Проверка, and is it up?
The server is down: Solo Frontier | NEW MAIN | Проверка is offline now, with the last sighting 10 days 16 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 16 October 2026, Rust Server Score saw it for the first time.
Which Rust version is Solo Frontier | NEW MAIN | Проверка running?
The server Solo Frontier | NEW MAIN | Проверка is on Rust network protocol 2634 and build 166494 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does Solo Frontier | NEW MAIN | Проверка wipe its map?
There are too few wipes on record for Solo Frontier | NEW MAIN | Проверка to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 26 days 6 hours have passed since this world was made.
Player count
Where does Solo Frontier | NEW MAIN | Проверка sit among Rust servers?
In the top 70% of all ranked servers, Solo Frontier | NEW MAIN | Проверка sits at #15,222 for player hours over the last seven days.
Is Solo Frontier | NEW MAIN | Проверка a busy server?
Solo Frontier | NEW MAIN | Проверка is offline at the moment; the last time it was seen was 10 days 16 hours ago.
Tags and filters
What do Solo Frontier | NEW MAIN | Проверка's tags stand for?
You'll see Solo Frontier | NEW MAIN | Проверка tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp5 (Max players): 5 slots are available; ts0 (Group limit): You cannot form teams here; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166494 (Build): This runs on build 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^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. 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 Solo Frontier | NEW MAIN | Проверка?
These Rust Server Score lists count Solo Frontier | NEW MAIN | Проверка among them: European Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Carbon ^y.
Rules and settings
What settings and rules apply on Solo Frontier | NEW MAIN | Проверка?
You will find no gather rate in the name of Solo Frontier | NEW MAIN | Проверка. No group limit is published. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Solo Frontier | NEW MAIN | Проверка runs which map?
A procedural map, generated by the game, is what Solo Frontier | NEW MAIN | Проверка runs.
How to join
How do you get onto Solo Frontier | NEW MAIN | Проверка?
To connect, start Rust, press F1, and type client.connect 95.182.104.60:28025. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2634,gmrust,cs166494,ts0,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp5
Max players5 slots are available.
ts0
Group limitYou cannot form teams here.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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.