Working its way up from the back of the class: #15,491 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
24/ 100
F
Lost ground: down 8,154 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 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers, and #611 of the quad servers (top 72%). Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 19 Sep, 13:44 UTC38d ago
2
–
running
0
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 name of 测试服 points to Asia, though no region tag is set. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 183.141.176.192:28015.
Is 测试服 up, and how steady is its uptime?
You cannot join now: 测试服 is offline, last seen 37 days 17 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 18 September 2026.
What Rust version is 测试服 on?
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.
Resets
When does 测试服 wipe, and how often?
The record holds too few of 测试服's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 38 days 22 hours.
What should you expect from wipe day on 测试服?
Recent wipes have peaked at 2 players on average. 2 hours after the latest wipe began, the crowd hit its peak.
Population
What position does 测试服 hold in the rankings?
Over the last seven days, 测试服 has #15,491 for player hours, in the top 69% of all ranked servers. In the quad group, it ranks #611.
Is 测试服 a busy server?
The last sighting of 测试服 was 37 days 17 hours ago, and it is offline right now.
Tags
What is meant by the tags on 测试服?
You'll see 测试服 tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp4 (Max players): Its slot count is 4; ts4 (Group limit): Teams cap out at 4; v2633 (Protocol): Join only if your game runs protocol 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; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. 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 lists and filters on Rust Server Score show 测试服?
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: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: Quad.
Map and rules
What settings and rules apply on 测试服?
You will find no gather rate in the name of 测试服. The cap on group size is 4 players (quad). You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is not enabled.
测试服 runs which map?
A procedural map of size 3,000 and seed 5, generated by the game, is what 测试服 runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How should you connect to 测试服?
To connect, start Rust, press F1, and type client.connect 183.141.176.192:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2633,^p,gmrust,cs164530,ts4,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp4
Max playersIts slot count is 4.
ts4
Group limitTeams cap out at 4.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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.