Working its way up from the back of the class: #16,111 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
20/ 100
F
Lost ground: down 9,781 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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% 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 Thursday 5 November, 19:00 UTC, in 7d 16h.
The force 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 [测试] puts it in Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 202.189.23.219:60005 is the address to use.
How reliable is [测试], and is it up?
You cannot join now: [测试] is offline, last seen 34 days 1 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
On what Rust version does [测试] sit?
You will find [测试] on Rust network protocol 2633 and build 164530, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does [测试] wipe, and how often?
The next wipe on [测试] is a projection from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 53 days 11 hours. The tags show a monthly wipe schedule.
Population
Where does [测试] place in the wider field of Rust servers?
Over the last seven days, [测试] has #16,111 for player hours, in the top 71% of all ranked servers and #474 in Asia.
How many players does [测试] usually have?
It has been 34 days 1 hours since [测试] was last seen, and it is offline right now.
Tags
How should you read the tags on [测试]?
You'll see [测试] tagged with gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): 2 slots are available; ts5 (Group limit): Teams cap out at 5; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; EA (East Asia): In the server browser it appears under East Asia in the browser, which picks them up from the server. 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 [测试]?
These Rust Server Score lists count [测试] among them: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Vanilla and Modded; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
How is [测试] set up, and what rules does it keep?
The name of [测试] gives no gather rate. The limit for a group is 5 players. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The vanilla label is its own: you get the unmodified game: no rate changes, no kits, no rule changes. VAC, Valve's anti-cheat, is enabled.
[测试] runs which map?
The game generates the procedural map on [测试] at size 4,200 with seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. The name of the map reads: Custom Map.
How to join
How do you get onto [测试]?
To connect, start Rust, press F1, and type client.connect 202.189.23.219:60005. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2633,^m,^v,EA,^p,gmrust,cs164530,ts5,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp2
Max players2 slots are available.
ts5
Group limitTeams cap out at 5.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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.