A quiet classroom so far: 1 of 10 on average. Plenty of space to grow.
Standingrank on player hours
49/ 100
D
Working its way up from the back of the class: #11,345 on player hours.
Uptimehours on the list, last 48
8/ 100
F
Attendance needs work: on the list only 4 of the last 48 hours.
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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (D); population 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.
AveragePeakWipe
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 51% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
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
Mon 26 Oct, 19:35 UTC1d ago
–
–
running
1
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
You'll find no region listed by TEST. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 178.172.210.17:28015 is the address to use.
Is TEST up, and how steady is its uptime?
At this moment, TEST is offline; the last time it was seen was 34 hours ago. It was up 0 of 24 hours over the last 1 full day, which is 0% of the time. On 26 October 2026, Rust Server Score saw it for the first time.
What Rust version is TEST on?
Rust network protocol 2635 and build 168909 on Windows is what TEST runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does TEST wipe, and how often?
TEST has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 36 hours have passed since this world was made.
Player count
Where does TEST sit among Rust servers?
Over the last seven days, TEST has #11,345 for player hours, in the top 51% of all ranked servers.
Is TEST a busy server?
TEST is offline at the moment; the last time it was seen was 34 hours ago. It peaked at 1 and averaged 1 players over the last seven days. The highest average in the last 48 hours came at 19:00 UTC, with 1 players.
Tags
What is meant by the tags on TEST?
You'll see TEST tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): Its slot count is 10; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as 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.
Which lists and filters on Rust Server Score show TEST?
These Rust Server Score lists count TEST among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Map and rules
How is TEST set up, and what rules does it keep?
Nothing in the name of TEST states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on TEST?
TEST runs a procedural map, which the game generates.
Getting in
What is the way to join TEST?
Enter client.connect 178.172.210.17: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 asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersIts slot count is 10.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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. Strongest in standing (D); population is the one to work on (F).