Working its way up from the back of the class: #13,215 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
36/ 100
F
Slipped a little: down 3,580 places this week. Nothing a good wipe can't fix.
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.
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 57% of all ranked servers, top 78% 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 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
You'll see 【炮炮测试】 listed in Asia, tagged EA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 113.26.33.221:28015 is the address to use.
Is 【炮炮测试】 up, and how steady is its uptime?
You cannot join now: 【炮炮测试】 is offline, last seen 36 days 5 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 16 September 2026, Rust Server Score saw it for the first time.
On what Rust version does 【炮炮测试】 sit?
You will find 【炮炮测试】 on Rust network protocol 2633 and build 163794, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does 【炮炮测试】 wipe its map?
the force wipe gives the basis for estimating 【炮炮测试】's next wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. The world it runs now was created 45 days 12 hours. Its tags list a monthly wipe schedule.
Player numbers
Where does 【炮炮测试】 sit among Rust servers?
Over the last seven days, 【炮炮测试】 has #13,215 for player hours, in the top 57% of all ranked servers and #452 in Asia.
Is 【炮炮测试】 a busy server?
【炮炮测试】 is offline at the moment; the last time it was seen was 36 days 5 hours ago.
Tags
What do 【炮炮测试】's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): 10 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): This runs on build 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): In the server browser it appears 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.
Which Rust Server Score filters and lists feature 【炮炮测试】?
Rust Server Score lists that include 【炮炮测试】: Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up 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.
Server rules
What settings and rules apply on 【炮炮测试】?
Nothing in the name of 【炮炮测试】 states a gather rate. The default of 8 players applies as the group cap. It runs pve, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. VAC, Valve's anti-cheat, is enabled.
Which map is in play on 【炮炮测试】?
A procedural map, generated by the game, is what 【炮炮测试】 runs.
Getting in
How do you get onto 【炮炮测试】?
To connect, start Rust, press F1, and type client.connect 113.26.33.221:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2633,^m,^v,EA,^p,gmrust,cs163794,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max players10 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildThis runs on build 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under 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.