Working its way up from the back of the class: #15,343 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 1,238 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); wipes are 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.
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 67% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
····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.
usual gap13.5 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 6
The first 48 hours of its last wipes
Fri 2 OctFri 18 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 00:01 UTC27d ago
1
–
running
0
Fri 18 Sep, 11:08 UTC41d ago
1
halved by day 6
13.5 days
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. Find it at 109.252.54.224:28015.
How dependable is TEST, and is it online at the moment?
The server is down: TEST is offline now, with the last sighting 27 days 21 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is TEST running?
Rust network protocol 2634 and build 166494 on Windows is what TEST runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does TEST wipe, and how often?
TEST 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. It has been running its current world for 27 days 22 hours.
What happens on TEST when wipe day arrives?
The average peak on its recent wipes was 1 players. 0 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. In the other wipes it slipped under half by day 6.
Player numbers
Where does TEST sit among Rust servers?
In the top 67% of all ranked servers, TEST sits at #15,343 for player hours over the last seven days.
Is TEST a busy server?
The last sighting of TEST was 27 days 21 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on TEST?
The game's browser takes its cue from the tags TEST has set: gmhardcore (Game mode): A harsher ruleset, hardcore; mp10 (Max players): 10 slots are available; ts0 (Group limit): The team system is turned off; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): Build number: 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here. 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 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; Game mode: Hardcore.
Server rules
What settings and rules apply on TEST?
Nothing in the name of TEST states a gather rate. It publishes no limit on group size. You get hardcore here, Facepunch's most punishing mode. You can raid other players and fight them. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map TEST uses?
A procedural map, generated by the game, is what TEST runs.
Connecting
How should you connect to TEST?
Enter client.connect 109.252.54.224: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?,v2634,gmhardcore,cs166494,ts0
Game
gmhardcore
Game modeA harsher ruleset, hardcore.
mp10
Max players10 slots are available.
ts0
Group limitThe team system is turned off.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildBuild number: 166494.
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 (D); wipes are the one to work on (F).