Working its way up from the back of the class: #13,143 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
46/ 100
D
Slipped a little: down 987 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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.
AveragePeak
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, 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 15h.
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
In Asia, according to its own listing, sits test01, with the EA tag. Rust Server Score takes the server's word for its location and does not trace the hardware. 59.39.220.166:28015 is the address to use.
How reliable is test01, and is it up?
At this moment, test01 is offline; the last time it was seen was 15 days 21 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 12 October 2026.
What Rust version is test01 on?
The server test01 is on Rust network protocol 2634 and build 167781 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does test01 wipe its map?
The next wipe on test01 is a projection from biweekly: 14 days after its last wipe. Expect the next wipe on Friday 30 October at 05:49 UTC. 27 days 8 hours have passed since this world was made. A fortnightly wipe schedule appears in its tags.
Population
Where does test01 place in the wider field of Rust servers?
In Asia, test01 is #477, and overall it is #13,143 on player hours over the last seven days, in the top 61% of all ranked servers.
How many players does test01 usually have?
test01 is offline at the moment; the last time it was seen was 15 days 21 hours ago.
Tags and filters
How should you read the tags on test01?
The game's browser takes its cue from the tags test01 has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): The server holds 1 slots; 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; cs167781 (Build): The game build is 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^b (Biweekly): A wipe happens once a fortnight; EA (East Asia): The server browser lists it under East Asia. 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.
Where does test01 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count test01 among them: Best community servers, graded. You can find it under these server-list filters: 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.
Rules and settings
How is test01 set up, and what rules does it keep?
You will find no gather rate in the name of test01. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: 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.
Can you tell me which map test01 uses?
test01 runs a procedural map, which the game generates.
How to join
How do you get onto test01?
To connect, start Rust, press F1, and type client.connect 59.39.220.166: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,cs167781,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersThe server holds 1 slots.
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.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Region
EA
East AsiaThe server browser lists it 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 D.