Offline 157.85.230.132:28015 checked 42d ago
AH测试
Connect
srv = rust.server("157.85.230.132:28017")
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 bestWipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 21h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 21h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 8h | Thu 12 Nov, 05:56 UTC | wipe |
| 2 | 27d 8h | Thu 26 Nov, 05:56 UTC | wipe |
| 3 | 34d 21h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 41d 8h | Thu 10 Dec, 05:56 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 17 Sep, 05:56 UTC42d ago | 1 | NaN | running | 1 |
# 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
- 157.85.230.132:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 17 Sep 2026, 05:56 UTC
- hostname
- –
- first seen
- 16 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｜仿官原倍｜休闲养老｜萌新天堂 | EA · groups of 18+ · biweekly · 1 on average | 0/100 |
| 1 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 59 on average | 22/200 |
| 2 | [JP][PvE]mameserver初心者おいで！ | EA · groups of 8+ · biweekly · 7 on average | 0/? |
| 3 | JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイド | EA · groups of 1000+ · 1x · biweekly · 7 on average | 3/69 |
| 4 | [喜相逢] PVE丨仿官原倍丨萌新养老 | EA · groups of 12+ · biweekly · 5 on average | 1/100 |
| 5 | 『向云端』PVE丨原倍丨休闲娱乐 | EA · groups of 8+ · biweekly · 5 on average | 1/99 |
Quick answers
From the figures on this page.
Population
How does AH测试 compare in the rankings?
Player hours over seven days put AH测试 at #14,072, in the top – of the ranked set.
How many players does AH测试 hold at once?
Offline now for AH测试, with the last sample 42 days 15 hours ago.
About the server
What is the Rust version on AH测试?
Version Rust network protocol 2633 and build 163794 on Windows is reported by AH测试. Steam updates your game for you, but the protocol must match to join.
Is AH测试 up, and what does its uptime show?
Offline now for AH测试, last seen 42 days 15 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 16 September 2026.
Where does AH测试 sit?
No region tag is published by AH测试, though its name points to Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 157.85.230.132:28015 is its address.
Map and rules
Which settings and rules does AH测试 run?
The name AH测试 carries no gather rate. No custom cap; the default of 8 players per group stands. pve is the game mode here, and player combat is not allowed. The server browser lists it under Community. VAC is not running; Valve's anti-cheat is off.
Which map has AH测试 selected?
The game generates its map: procedural, on AH测试.
Wipes and dates
When does AH测试 wipe, and on what schedule?
The tag sets the prediction: AH测试 has too few wipes on record to confirm its schedule. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 42 days 15 hours ago. A fortnightly wipe schedule is published in its tags.
What is wipe day on AH测试 like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 1 hours in.
Tags, lists
Where does AH测试 appear among Rust Data lists and filters?
These Rust Data lists include AH测试: Rust community servers, unfiltered and Rust PvE servers. Under these filters on the server list, it is listed: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: Biweekly ^b and PvE ^p; Group limit: 5 or more; Wipe schedule: Every two weeks.
Which meanings do the tags on AH测试 hold?
Read by the game's server browser, the tags AH测试 publishes are: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): The server lists 4 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs163794 (Build): Build number: 163794; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^b (Biweekly): Two weeks between wipes; ^p (PvE): PvE: the world is the threat, not other players. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into AH测试?
The manual route: launch Rust, F1, then client.connect 157.85.230.132:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.