Working its way up from the back of the class: #15,102 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
34/ 100
F
Lost ground: down 4,874 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.
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 70% of all ranked servers. 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 21h.
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
No region tag appears for AH测试, but the name suggests Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 183.159.57.190:28015.
Is AH测试 up, and how steady is its uptime?
You cannot join now: AH测试 is offline, last seen 13 days 7 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 15 October 2026, Rust Server Score saw it for the first time.
Which Rust version is AH测试 running?
Rust network protocol 2634 and build 167398 on Windows is what AH测试 runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does AH测试 reset?
The next wipe on AH测试 is a projection from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 19 days 16 hours. Its tags say it wipes every two weeks.
Player count
Where does AH测试 sit among Rust servers?
Over the last seven days, AH测试 has #15,102 for player hours, in the top 70% of all ranked servers.
How many players does AH测试 usually have?
AH测试 is offline at the moment; the last time it was seen was 13 days 7 hours ago.
Tags and filters
What do AH测试's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp4 (Max players): Its slot count is 4; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167398 (Build): This runs on build 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^b (Biweekly): A wipe happens once a fortnight; ^p (PvE): Players do not fight one another here; the world is the danger are the tags AH测试 publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature AH测试?
These Rust Server Score lists count AH测试 among them: Best community servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: Biweekly ^b and PvE ^p; Group limit: 5 or more; Wipe schedule: Every two weeks.
Map and rules
What settings and rules apply on AH测试?
The name of AH测试 gives no gather rate. With no change from the game default, groups take up to 8 players. You get pve here, no PvP between players. 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.
AH测试 runs which map?
A procedural map, generated by the game, is what AH测试 runs.
Getting in
How should you connect to AH测试?
To connect, start Rust, press F1, and type client.connect 183.159.57.190:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2634,^b,^p,gmrust,cs167398,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp4
Max playersIts slot count is 4.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
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.