Working its way up from the back of the class: #13,672 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
43/ 100
F
Slipped a little: down 1,807 places this week. Nothing a good wipe can't fix.
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 62% of all ranked servers, top 90% 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 11h.
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
The EA tag on test01 puts it in Asia. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 59.39.216.190:28015.
How reliable is test01, and is it up?
You cannot join now: test01 is offline, last seen 21 days 20 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 7 October 2026.
What Rust version is test01 on?
You will find test01 on Rust network protocol 2634 and build 167058, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does test01 reset?
The estimate for test01's next wipe comes from biweekly: 14 days after its last wipe. Expect the next wipe on Friday 30 October at 05:49 UTC. It has been running its current world for 27 days 12 hours. Its tags say it wipes every two weeks.
Player count
What position does test01 hold in the rankings?
In Asia, test01 is #476, and overall it is #13,672 on player hours over the last seven days, in the top 62% of all ranked servers.
Is test01 a busy server?
test01 is offline at the moment; the last time it was seen was 21 days 20 hours ago.
Tags and filters
How should you read the tags on test01?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): 1 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167058 (Build): Build number: 167058; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^b (Biweekly): A wipe happens once a fortnight; EA (East Asia): You will find it under East Asia in the browser are the tags test01 publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature test01?
These Rust Server Score lists count test01 among them: Best community servers, graded. These filters bring it up 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
What settings and rules apply on test01?
Nothing in the name of test01 states a gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is not enabled.
Can you tell me which map test01 uses?
A procedural map, generated by the game, is what test01 runs.
Connecting
How do you get onto test01?
To connect, start Rust, press F1, and type client.connect 59.39.216.190: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,cs167058,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max players1 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167058
BuildBuild number: 167058.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Region
EA
East AsiaYou will find it under East Asia in the browser.
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.