Working its way up from the back of the class: #15,348 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
47/ 100
D
Slipped a little: down 803 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (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 powered purifier probe sit?
You'll find no region listed by Solo Frontier | TEST powered purifier probe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 95.46.137.9:28025 is the address to use.
How dependable is Solo Frontier | TEST powered purifier probe, and is it online at the moment?
At this moment, Solo Frontier | TEST powered purifier probe is offline; the last time it was seen was 8 days 17 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 19 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Solo Frontier | TEST powered purifier probe sit?
Rust network protocol 2634 and build 166494 on Windows is what Solo Frontier | TEST powered purifier probe runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does Solo Frontier | TEST powered purifier probe wipe its map?
Solo Frontier | TEST powered purifier probe has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 27 days 7 hours have passed since this world was made.
Player count
What position does Solo Frontier | TEST powered purifier probe hold in the rankings?
In the top 70% of all ranked servers, Solo Frontier | TEST powered purifier probe sits at #15,348 for player hours over the last seven days.
How many players does Solo Frontier | TEST powered purifier probe usually have?
The last sighting of Solo Frontier | TEST powered purifier probe was 8 days 17 hours ago, and it is offline right now.
Lists and filters
What is meant by the tags on Solo Frontier | TEST powered purifier probe?
You'll see Solo Frontier | TEST powered purifier probe tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): Its slot count is 20; 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): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon 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.
Where does Solo Frontier | TEST powered purifier probe appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Solo Frontier | TEST powered purifier probe among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y.
Server rules
How is Solo Frontier | TEST powered purifier probe set up, and what rules does it keep?
You will find no gather rate in the name of Solo Frontier | TEST powered purifier probe. 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.
Which map is in play on Solo Frontier | TEST powered purifier probe?
A procedural map, generated by the game, is what Solo Frontier | TEST powered purifier probe runs.
Connecting
How should you connect to Solo Frontier | TEST powered purifier probe?
To connect, start Rust, press F1, and type client.connect 95.46.137.9: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 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
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is 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. Strongest in momentum (D); standing is the one to work on (F).