Offline EA 119.183.132.140:54321 checked 8d ago
『测试』
Connect
srv = rust.server("119.183.132.140:54322")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 59% of all ranked servers, top 87% in EA. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 18h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 18h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 18h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 15:14 UTC27d ago | 1 | NaN | running | 1 |
| 1 | Fri 25 Sep, 15:09 UTC34d ago | 1 | NaN | 7 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 119.183.132.140:54321
- region
- EA
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 2 Oct 2026, 15:14 UTC
- hostname
- –
- first seen
- 25 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | 生存PVE S120档 | 丧尸 | 摸金撤离 | 死亡不掉 | RICK | EA · groups of 20+ · monthly · 33 on average | 4/128 |
| 1 | 小淘气PVE-简单玩法-10倍爆率-经久耐玩 | EA · groups of 8+ · monthly · 23 on average | 31/100 |
| 2 | 小萌妹PVE-建家打怪-万款皮肤免费-房子无敌 | EA · groups of 20+ · monthly · 21 on average | 27/100 |
| 3 | 低调/PVE/10倍废料/养老/死亡不掉/等级/强化 | EA · groups of 20+ · monthly · 18 on average | 17/200 |
| 4 | 鲨鲨/PVE/10倍废/全新RPG模式/长久耐玩/死亡不掉 | EA · groups of 20+ · monthly · 15 on average | 17/200 |
| 5 | 黑鲨PVE/10倍废料/打怪升级/长久耐玩/死亡不掉 | EA · groups of 20+ · monthly · 15 on average | 17/200 |
Quick answers
From the figures on this page.
Population
What position does 『测试』 take in the server rankings?
On seven-day player hours 『测试』 is #13,160 overall and #483 in Asia, inside the top 59% of all ranked servers.
How many players does 『测试』 hold at once?
The current row shows 『测试』 offline; the last response was 8 days 9 hours ago.
Server data
Which Rust version is 『测试』 on?
The build is Rust network protocol 2634 and build 166586 on Windows, run by 『测试』. The protocol has to match before you can join, and Steam does the updating.
How reliable is 『测试』, and is it up?
Offline now for 『测试』, last seen 8 days 9 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 25 September 2026.
In which location is 『测试』 hosted?
With its EA tag, 『测试』 lists itself in Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 119.183.132.140:54321 is its address.
Settings and map
What rules and settings are recorded for 『测试』?
No gather rate appears in the name: 『测试』. No custom cap; the default of 8 players per group stands. softcore is the game mode here, and Facepunch's lighter mode, with partial loot kept. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has 『测试』 loaded?
A procedural map runs on 『测试』, generated by the game.
Wipe data
On what schedule does 『测试』 wipe?
The only wipe 『测试』 takes is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 27 days 9 hours ago. A monthly wipe schedule is published in its tags.
On 『测试』, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Where does 『测试』 appear among Rust Data lists and filters?
These Rust Data lists include 『测试』: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Game mode: PvE and Softcore; Server tag: Monthly ^m, Softcore ^s, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Which meanings do the tags on 『测试』 hold?
Read by the game's server browser, the tags 『测试』 publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166586 (Build): Recorded game build: 166586; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^s (Softcore): Softcore, Facepunch's easier mode: part of your inventory survives death; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; EA (East Asia): In the server browser it sits under East Asia. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into 『测试』?
Enter client.connect 119.183.132.140:54321 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.