Working its way up from the back of the class: #14,185 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
30/ 100
F
Lost ground: down 5,555 places this week. A strong wipe could turn it round.
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 65% 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
Which region is Solo Frontier | SOLO | ТЕСТ based in?
No region tag appears for Solo Frontier | SOLO | ТЕСТ, but the name suggests Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 95.182.104.60:28015.
Is Solo Frontier | SOLO | ТЕСТ up, and how steady is its uptime?
The server is down: Solo Frontier | SOLO | ТЕСТ is offline now, with the last sighting 11 days 9 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 5 October 2026, Rust Server Score saw it for the first time.
What Rust version is Solo Frontier | SOLO | ТЕСТ on?
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.
Resets
On what schedule does Solo Frontier | SOLO | ТЕСТ reset?
There are too few wipes on record for Solo Frontier | SOLO | ТЕСТ 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 23 hours have passed since this world was made.
Player numbers
Where does Solo Frontier | SOLO | ТЕСТ place in the wider field of Rust servers?
In the top 65% of all ranked servers, Solo Frontier | SOLO | ТЕСТ sits at #14,185 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 11 days 9 hours ago.
Tags
What is meant by the tags on Solo Frontier | SOLO | ТЕСТ?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp20 (Max players): Its slot count is 20; ts0 (Group limit): Teams are disabled; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): The game build is 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here are the tags Solo Frontier | SOLO | ТЕСТ publishes, and the game's server browser reads them. 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 Solo Frontier | SOLO | ТЕСТ?
Rust Server Score lists that include Solo Frontier | SOLO | ТЕСТ: 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
How is Solo Frontier | SOLO | ТЕСТ set up, and what rules does it keep?
You will find no gather rate in the name of Solo Frontier | SOLO | ТЕСТ. No group limit is published. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. 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.
Which map is in play on Solo Frontier | SOLO | ТЕСТ?
Solo Frontier | SOLO | ТЕСТ runs a procedural map, which the game generates.
How to join
How do you get onto Solo Frontier | SOLO | ТЕСТ?
Enter client.connect 95.182.104.60: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,cs166494,ts0,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp20
Max playersIts slot count is 20.
ts0
Group limitTeams are disabled.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildThe game build is 166494.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it 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.