Working its way up from the back of the class: #15,150 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
27/ 100
F
Lost ground: down 6,872 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 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 TEST - acceptance sit?
Solo Frontier TEST - acceptance leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 95.182.106.48:28115.
How dependable is Solo Frontier TEST - acceptance, and is it online at the moment?
You cannot join now: Solo Frontier TEST - acceptance is offline, last seen 13 days 22 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 14 October 2026, Rust Server Score saw it for the first time.
What Rust version is Solo Frontier TEST - acceptance on?
Rust network protocol 2634 and build 166494 on Windows is what Solo Frontier TEST - acceptance runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does Solo Frontier TEST - acceptance reset?
There are too few wipes on record for Solo Frontier TEST - acceptance 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. 27 days 12 hours have passed since this world was made.
Player count
What position does Solo Frontier TEST - acceptance hold in the rankings?
In the top 70% of all ranked servers, Solo Frontier TEST - acceptance sits at #15,150 for player hours over the last seven days.
What does the population on Solo Frontier TEST - acceptance look like?
The last sighting of Solo Frontier TEST - acceptance was 13 days 22 hours ago, and it is offline right now.
Lists and filters
What do Solo Frontier TEST - acceptance's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp20 (Max players): The server holds 20 slots; ts0 (Group limit): You cannot form teams here; 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): This is RakNet: the network layer Rust normally uses; $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 are the tags Solo Frontier TEST - acceptance 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 TEST - acceptance?
Rust Server Score lists that include Solo Frontier TEST - acceptance: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y.
Rules and settings
How is Solo Frontier TEST - acceptance set up, and what rules does it keep?
You will find no gather rate in the name of Solo Frontier TEST - acceptance. You will find no published group limit. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. You are covered by VAC, Valve's anti-cheat.
Solo Frontier TEST - acceptance runs which map?
Solo Frontier TEST - acceptance runs a procedural map, which the game generates.
Connecting
How do you get onto Solo Frontier TEST - acceptance?
Enter client.connect 95.182.106.48:28115 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 playersThe server holds 20 slots.
ts0
Group limitYou cannot form teams here.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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.