Working its way up from the back of the class: #15,503 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
31/ 100
F
Lost ground: down 6,013 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.
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 71% 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 | SOLO | ТЕСТ sit?
The name of Solo Frontier | SOLO | ТЕСТ points to Europe, though no region tag is set. Rust Server Score takes the server's word for its location and does not trace the hardware. 95.182.106.67:28015 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 15 days 17 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 12 October 2026, Rust Server Score saw it for the first time.
Which Rust version is Solo Frontier | SOLO | ТЕСТ running?
The server Solo Frontier | SOLO | ТЕСТ 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.
Resets
On what schedule does Solo Frontier | SOLO | ТЕСТ reset?
Solo Frontier | SOLO | ТЕСТ has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 17 days 19 hours.
Player count
Where does Solo Frontier | SOLO | ТЕСТ sit among Rust servers?
Over the last seven days, Solo Frontier | SOLO | ТЕСТ has #15,503 for player hours, in the top 71% of all ranked servers.
What does the population on Solo Frontier | SOLO | ТЕСТ look like?
Solo Frontier | SOLO | ТЕСТ is offline at the moment; the last time it was seen was 15 days 17 hours ago.
Lists and filters
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): The server holds 20 slots; ts0 (Group limit): Teams are disabled; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; 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): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon 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.
Which lists and filters on Rust Server Score show Solo Frontier | SOLO | ТЕСТ?
These Rust Server Score lists count Solo Frontier | SOLO | ТЕСТ 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 | SOLO | ТЕСТ?
Nothing in the name of Solo Frontier | SOLO | ТЕСТ states a gather rate. No group limit is published. It runs survival, gather, build and raid, as in 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.
Connecting
What is the way to join Solo Frontier | SOLO | ТЕСТ?
To connect, start Rust, press F1, and type client.connect 95.182.106.67:28015. 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 playersThe server holds 20 slots.
ts0
Group limitTeams are disabled.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
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
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: Carbon.
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.