Working its way up from the back of the class: #15,521 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
29/ 100
F
Lost ground: down 6,435 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.
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 68% of all ranked servers, top 92% in EA. 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
Next wipe Friday 30 October, 05:49 UTC, in 19h.
Biweekly: 14 days after its last 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
You'll see test01 listed in Asia, tagged EA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 59.39.221.72:28015.
How dependable is test01, and is it online at the moment?
The server is down: test01 is offline now, with the last sighting 26 days 2 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 2 October 2026.
What Rust version is test01 on?
Rust network protocol 2634 and build 166652 on Windows is what test01 runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does test01 wipe, and how often?
The estimate for test01's next wipe comes from biweekly: 14 days after its last wipe. Friday 30 October at 05:49 UTC is the date set for its next wipe. The world it runs now was created 27 days 4 hours. A fortnightly wipe schedule appears in its tags.
Player numbers
What position does test01 hold in the rankings?
In Asia, test01 is #479, and overall it is #15,521 on player hours over the last seven days, in the top 68% of all ranked servers.
What does the population on test01 look like?
test01 is offline at the moment; the last time it was seen was 26 days 2 hours ago.
Lists and filters
What do test01's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): Its slot count is 1; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^b (Biweekly): The server wipes on a two-week cycle; EA (East Asia): In the server browser it appears under East Asia are the tags test01 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 lists and filters on Rust Server Score show test01?
These Rust Server Score lists count test01 among them: Best community servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b; Group limit: 5 or more; Wipe schedule: Every two weeks.
Server rules
Which rules does test01 enforce, and what are its settings?
The name of test01 gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. The server does not run VAC, Valve's anti-cheat.
test01 runs which map?
test01 runs a procedural map, which the game generates.
Connecting
How do you get onto test01?
To connect, start Rust, press F1, and type client.connect 59.39.221.72:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2634,^b,EA,gmrust,cs166652,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max playersIts slot count is 1.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Region
EA
East AsiaIn the server browser it appears under East Asia.
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.