Offline 123.185.210.178:28015 checked 32d ago
单人PVE
Connect
srv = rust.server("123.185.210.178: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 best
Top 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 10h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 10h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 9d 19h | Sun 8 Nov, 03:33 UTC | wipe |
| 2 | 23d 19h | Sun 22 Nov, 03:33 UTC | wipe |
| 3 | 35d 10h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 37d 19h | Sun 6 Dec, 03:33 UTC | 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 | Sun 27 Sep, 03:33 UTC32d ago | 1 | NaN | running | 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
- 123.185.210.178:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 27 Sep 2026, 03:33 UTC
- hostname
- –
- first seen
- 27 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 16+ · biweekly · 58 on average | 61/200 |
| 1 | [JP][PvE]mameserver初心者おいで! | EA · groups of 8+ · biweekly · 8 on average | 4/65 |
| 2 | JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイド | EA · groups of 1000+ · 1x · biweekly · 7 on average | 5/69 |
| 3 | [喜相逢] PVE丨仿官原倍丨萌新养老 | EA · groups of 12+ · biweekly · 5 on average | 1/100 |
| 4 | [PVE][JP] そば鯖 Raidable Bases 初心者大歓迎 | EA · groups of 16+ · biweekly · 4 on average | 0/50 |
| 5 | 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 | EA · groups of 8+ · biweekly · 3 on average | 5/100 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does 单人PVE rank?
Player hours over seven days put 单人PVE at #14,491, in the top 61% of the ranked set.
How many players does 单人PVE hold at once?
The current row shows 单人PVE offline; the last response was 32 days 3 hours ago.
About the server
What Rust version does 单人PVE run?
Version Rust network protocol 2633 and build 165217 on Windows is reported by 单人PVE. Joining needs the same protocol on your game; Steam handles the update.
How reliable is 单人PVE, and is it online now?
Offline now for 单人PVE, last seen 32 days 3 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 27 September 2026.
Where does 单人PVE sit?
No region tag is published by 单人PVE, 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. You can reach it at 123.185.210.178:28015.
Map and rules
Which rules apply on 单人PVE, and what settings?
You will not find a gather rate in the string 单人PVE. No custom cap; the default of 8 players per group stands. Recorded as pve, player combat is not allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is not running; Valve's anti-cheat is off.
What is the map on 单人PVE?
The game generates its map: procedural, on 单人PVE.
Wipe schedule
When does 单人PVE wipe, and how often?
The prediction follows the tag, because 单人PVE's wipes on record are too few to confirm the schedule. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 32 days 4 hours ago. The tags list a two-weekly wipe cycle.
On 单人PVE, what happens on wipe day?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Where does 单人PVE appear among Rust Data lists and filters?
On Rust Data, 单人PVE appears in these lists: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Which meanings do the tags on 单人PVE hold?
These tags are published by 单人PVE and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into 单人PVE?
In Rust, F1 opens the console: type client.connect 123.185.210.178:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.