Station XX-4803 · recording
[HM]测试服
Online 103.39.64.28:35000 checked 10m ago
- Players now
- 0/ 20
- 0% full
- Motion · 24 h
- M0.0▼falling
- −1 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #4,803
- top 22%
- Last wipe
- 21d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 20 slots
- Motion · 24 h
- M0.0▼falling−1 players
- Sharpest hour
- +1into Thu 12:00 UTC
- Peak · 48 h
- 1most players in any hour
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 22% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 1.1 daysbetween real wipes
- on rhythm
- 33%of its recent wipes
- wipe-day peak
- 2players, 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, 14 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 10 Oct, 02:57 UTC20d ago | M0.0▲rising | 2 | – | running | 1 | |
| Fri 9 Oct, 01:33 UTC21d ago | M0.3▲rising | 2 | – | 1.1 days | 0 | |
| Thu 8 Oct, 14:51 UTC21d ago | M0.0■steady | 1 | – | 0.4 days | 1 | |
| Wed 7 Oct, 04:32 UTC23d ago | M0.0▲rising | 1 | – | 1.4 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which map is running on [HM]测试服?
[HM]测试服 runs a procedural map of size 3,000 with seed 109373911, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on [HM]测试服?
The name of [HM]测试服 gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on [HM]测试服?
At this moment, [HM]测试服 records 0 players across 20 slots. The seven-day average is 0 players, with a peak of 1. The last 48 hours show their highest activity at 11:00 UTC, averaging 1 players.
How does [HM]测试服 rank against other Rust servers?
On player hours for the past week, [HM]测试服 sits at #4,803, which puts it inside the top 22% of every ranked server.
Server details
How reliably does [HM]测试服 stay online?
[HM]测试服 is up at the moment. The uptime it reports puts its last restart about 3 days 18 hours ago. Of the 168 hours in the last 7 full days, it was up for 165, or 98% of the time. 7 October 2026 is when Rust Server Trends first recorded it.
Does [HM]测试服 hold a steady tick rate?
Across the last 48 hours it averaged 197 server fps, with a floor of 88. The world held up to 44,757 entities at its peak, buildings and deployables included. Its highest memory use was 6,190 MB. What you feel as lag is the combination of low fps and a rising entity count.
Where in the world is [HM]测试服 hosted?
Its name points to Asia, but [HM]测试服 publishes no region tag. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 103.39.64.28:35000.
What build of Rust does [HM]测试服 use?
Rust network protocol 2635 and build 168909 on Linux is what [HM]测试服 runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on [HM]测试服?
On average, the busiest point of its recent wipes drew 2 players. The peak on the most recent wipe came 14 hours after the wipe.
How often does [HM]测试服 wipe, and on which days?
No next wipe can be predicted for [HM]测试服, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 21 days 6 hours.
Server tags
What do the server tags on [HM]测试服 mean?
These are the tags [HM]测试服 publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): Slots: 20; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does [HM]测试服 appear?
The Rust Server Trends lists that take in [HM]测试服 are: Modded Rust servers, tracked live. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
How do you connect to [HM]测试服?
To join, enter client.connect 103.39.64.28:35000 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.