Rust Data

rustdata.spaceservers103.39.64.28:35001.ipynb

Run all rust-data · live

‹ All servers

Online 103.39.64.28:35000 checked 9m ago

[HM]测试服

moddedoxide

Connect

srv = rust.server("103.39.64.28:35001")
print(srv.connect_command)

Right now

srv.summary()
players now 0/20 # 0% full
7-day average 0 # peak 1
rank #4,835 # top 22%
last wipe 20d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75101:0010:0020:0005:0014:0023:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040001:0010:0020:0005:0014:0023:00

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 7 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k7 Oct11 Oct16 Oct20 Oct25 Oct29 Oct

Top 22% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.1 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

Sat 10 OctFri 9 OctThu 8 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 14 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 10 Oct, 02:57 UTC19d ago 2 NaN running 1
1 Fri 9 Oct, 01:33 UTC20d ago 2 NaN 1.1 days 0
2 Thu 8 Oct, 14:51 UTC21d ago 1 NaN 0.4 days 1
3 Wed 7 Oct, 04:32 UTC22d ago 1 NaN 1.4 days 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.

display(srv.map, srv.info())

Map

3000 · seed 109373911
Map of [HM]测试服
map
Procedural Map
size
3000
seed
109373911
Open on RustMaps

Server

srv.info()
address
103.39.64.28:35000
region
–
max players
20
group limit
8, the default
wipe schedule
–
last wipe
9 Oct 2026, 01:33 UTC
hostname
–
first seen
7 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0QS『芬达』100000倍/10.30/枪战/蓝图全解/萌新/建造EA · groups of 20+ · weekly · 25 on average28/100
1【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐EA · groups of 8+ · weekly · 22 on average0/200
2[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 14 on average0/100
3[守护]100倍PVE/迷雾僵尸/突袭基地/等级武直/萌新EA · no group limit · 13 on average20/100
4[霸道]10000000倍-10.30日-萌新首选-稳定长久EA · no group limit · 12 on average19/100
5#10-[搞就完了]10倍/10.30新档/无权/萌新首选EA · no group limit · 12 on average20/100

Quick answers

From the figures on this page.

Player counts

How does [HM]测试服 compare in the rankings?

Player hours over seven days put [HM]测试服 at #4,835, in the top 22% of the ranked set.

How many players does [HM]测试服 hold at once?

[HM]测试服 reports 0 players at this refresh, with 20 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 04:00 UTC is the busiest, at 1 players.

Server facts

What does performance look like on [HM]测试服?

Server fps over the last 48 hours averages 196; the floor is 88. Entity numbers reached 44,665, and that includes buildings, deployables and the rest. The memory field tops out at 6,190 MB. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does [HM]测试服 run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by [HM]测试服. Joining needs the same protocol on your game; Steam handles the update.

Is [HM]测试服 up, and what does its uptime show?

The current sample puts [HM]测试服 online. Count back 3 days 11 hours from its reported uptime to get the last restart. Uptime of 84% across the last 7 full days: 141 hours of 168. The first row Rust Data holds for it is dated 7 October 2026.

Where does [HM]测试服 sit?

No region tag is published by [HM]测试服, though its name points to Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 103.39.64.28:35000.

Map and rules

Which settings and rules does [HM]测试服 run?

The name [HM]测试服 carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.

What is the map on [HM]测试服?

Size 3,000, seed 109373911: the procedural map on [HM]测试服, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipes and dates

On what schedule does [HM]测试服 wipe?

No next wipe can be predicted for [HM]测试服, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 20 days 22 hours ago.

On [HM]测试服, what happens on wipe day?

The average peak over recent wipes is 2 players. Peak population on the latest wipe came 14 hours in.

Lists and tags

Where does [HM]测试服 appear among Rust Data lists and filters?

On Rust Data, [HM]测试服 appears in these lists: Modded Rust servers. It appears under these filters on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on [HM]测试服?

The game's server browser reads these tags from [HM]测试服: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): The server lists 20 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way into [HM]测试服?

The manual route: launch Rust, F1, then client.connect 103.39.64.28:35000. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp20,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp20
Max players The server lists 20 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build The server runs build 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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.

Rust Data 61,057 players 11,704 servers online