Working its way up from the back of the class: #13,771 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
38/ 100
F
Slipped a little: down 3,434 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.
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 60% 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
PrecisionSorter Test leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 94.54.148.95:28015.
How dependable is PrecisionSorter Test, and is it online at the moment?
You cannot join now: PrecisionSorter Test is offline, last seen 36 days 9 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 22 September 2026, Rust Server Score saw it for the first time.
On what Rust version does PrecisionSorter Test sit?
Rust network protocol 2633 and build 164530 on Windows is what PrecisionSorter Test runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does PrecisionSorter Test wipe its map?
The record holds too few of PrecisionSorter Test's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 36 days 14 hours.
Player count
Where does PrecisionSorter Test place in the wider field of Rust servers?
In the top 60% of all ranked servers, PrecisionSorter Test sits at #13,771 for player hours over the last seven days.
What does the population on PrecisionSorter Test look like?
It has been 36 days 9 hours since PrecisionSorter Test was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on PrecisionSorter Test?
You'll see PrecisionSorter Test tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp20 (Max players): Its slot count is 20; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): Build number: 164530; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does PrecisionSorter Test appear in the Rust Server Score lists and filters?
These Rust Server Score lists count PrecisionSorter Test among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does PrecisionSorter Test enforce, and what are its settings?
You will find no gather rate in the name of PrecisionSorter Test. With no change from the game default, groups take up to 8 players. 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. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map PrecisionSorter Test uses?
PrecisionSorter Test runs a procedural map, which the game generates.
How to join
How do you get onto PrecisionSorter Test?
To connect, start Rust, press F1, and type client.connect 94.54.148.95:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp20
Max playersIts slot count is 20.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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.