Working its way up from the back of the class: #15,962 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
27/ 100
F
Lost ground: down 7,474 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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 30 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers, top 92% in EA, and #203 of the solo servers (top 91%). 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 6d 22h.
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. 103.39.64.190:20015 is the address to use.
Is [江湖]测试服 up, and how steady is its uptime?
The server is down: [江湖]测试服 is offline now, with the last sighting 26 days 15 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 30 September 2026.
On what Rust version does [江湖]测试服 sit?
You will find [江湖]测试服 on Rust network protocol 2633 and build 164530, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does [江湖]测试服 wipe, and how often?
the force wipe gives the basis for estimating [江湖]测试服's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 29 days 12 hours have passed since this world was made. The tags show a monthly wipe schedule.
Population
What position does [江湖]测试服 hold in the rankings?
In Asia, [江湖]测试服 is #483, and overall it is #15,962 on player hours over the last seven days, in the top 70% of all ranked servers. In the solo group, it ranks #203.
What does the population on [江湖]测试服 look like?
It has been 26 days 15 hours since [江湖]测试服 was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on [江湖]测试服?
gmrust (Game mode): Rust survival, played by the standard rules; mp500 (Max players): Its slot count is 500; ts1 (Group limit): Teams cap out at 1; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): The server browser lists it under East Asia are the tags [江湖]测试服 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.
Where does [江湖]测试服 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [江湖]测试服 among them: Modded Rust servers, graded and Solo Rust servers, graded. These filters bring it up on the server list: Region: Asia; Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Monthly.
Server rules
What settings and rules apply on [江湖]测试服?
Nothing in the name of [江湖]测试服 states a gather rate. No teams are allowed: it is solo only. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. By its own description it is vanilla: you get the unmodified game: no rate changes, no kits, no rule changes. The server does not run VAC, Valve's anti-cheat.
[江湖]测试服 runs which map?
The game generates the procedural map on [江湖]测试服 at size 3,200 with seed 1. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
What is the way to join [江湖]测试服?
To connect, start Rust, press F1, and type client.connect 103.39.64.190:20015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp500,ptrak,$r?,v2633,^m,^v,EA,gmrust,cs164530,ts1,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp500
Max playersIts slot count is 500.
ts1
Group limitTeams cap out at 1.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildThe game build is 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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 F.