Working its way up from the back of the class: #13,922 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 5,249 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 61% 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
test leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 145.224.83.228:20000 is the address to use.
Is test up, and how steady is its uptime?
You cannot join now: test is offline, last seen 25 days 10 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 3 October 2026.
On what Rust version does test sit?
The server test is on Rust network protocol 2634 and build 166652 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does test reset?
There are too few wipes on record for test to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 26 days 11 hours have passed since this world was made.
Player count
What position does test hold in the rankings?
Over the last seven days, test has #13,922 for player hours, in the top 61% of all ranked servers.
Is test a busy server?
test is offline at the moment; the last time it was seen was 25 days 10 hours ago.
Tags and filters
How should you read the tags on test?
The game's browser takes its cue from the tags test has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here. 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.
Which Rust Server Score filters and lists feature test?
Rust Server Score lists that include test: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
What settings and rules apply on test?
The name of test gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is not enabled.
Which map is in play on test?
The game generates a procedural map for test.
Getting in
How do you get onto test?
To connect, start Rust, press F1, and type client.connect 145.224.83.228:20000. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set 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.