Working its way up from the back of the class: #9,641 on player hours.
Uptimehours on the list, last 48
6/ 100
F
Attendance needs work: on the list only 3 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
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
58/ 100
C−
Moving up: up 1,528 places this week.
A term to build on.
Strongest in momentum (C−); uptime 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
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 43% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
7 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··WW··W
··WF···
·······
·WW····
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap2.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 5
The first 48 hours of its last wipes
Wed 14 OctTue 13 OctThu 1 Oct
Players each hour, from the hour of the wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 14 Oct, 10:41 UTC14d ago
–
–
running
1
Tue 13 Oct, 08:29 UTC15d ago
0
–
1.1 days
0
Thu 1 Oct, 18:03 UTCFW27d ago
1
halved by day 5
11.6 days
1
Wed 30 Sep, 14:34 UTC28d ago
1
–
1.1 days
1
Sun 27 Sep, 07:41 UTC31d ago
1
✓ held half
3.3 days
1
Thu 24 Sep, 12:12 UTC34d ago
1
–
2.8 days
1
Wed 23 Sep, 03:50 UTC36d ago
1
–
1.3 days
0
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. You can connect at 153.170.109.3:28020.
Is Test up, and how steady is its uptime?
At this moment, Test is offline; the last time it was seen was 16 hours ago. It was up 6 of 168 hours over the last 7 full days, which is 4% of the time. On 18 September 2026, Rust Server Score saw it for the first time.
What Rust version is Test on?
You will find Test on Rust network protocol 2635 and build 169498, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does Test wipe, and how often?
Test wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 31 days 22 hours.
What should you expect from wipe day on Test?
The average peak on its recent wipes was 1 players. The crowd stayed above half that peak, right through to the next wipe, in 50% of its recent wipes. In the other wipes it slipped under half by day 5.
Player numbers
Where does Test place in the wider field of Rust servers?
Over the last seven days, Test has #9,641 for player hours, in the top 43% of all ranked servers.
What does the population on Test look like?
The last sighting of Test was 16 hours ago, and it is offline right now. It peaked at 1 and averaged 1 players over the last seven days. The highest average in the last 48 hours came at 12:00 UTC, with 1 players.
Tags and filters
What is meant by the tags on Test?
gmrust (Game mode): Rust survival, played by the standard rules; mp0 (Max players): Its slot count is 0; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs169498 (Build): The game build is 169498; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here are the tags Test publishes, and the game's server browser reads them. 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?
These Rust Server Score lists count Test among them: 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
Which rules does Test enforce, and what are its settings?
You will find no gather rate in the name of Test. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Getting in
How should you connect to Test?
Enter client.connect 153.170.109.3:28020 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 asmp0,ptrak,$r?,v2635,gmrust,cs169498,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp0
Max playersIts slot count is 0.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs169498
BuildThe game build is 169498.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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. Strongest in momentum (C−); uptime is the one to work on (F).