Offline 123.185.209.177:28015 checked 40d ago
单人PVE
Connect
srv = rust.server("123.185.209.177: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
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Sunday 1 November, 03:17 UTC, in 1d 19h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 1d 19h | Sun 1 Nov, 03:17 UTC | wipe |
| 1 | 6d 11h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 15d 19h | Sun 15 Nov, 03:17 UTC | wipe |
| 3 | 29d 19h | Sun 29 Nov, 03:17 UTC | wipe |
| 4 | 34d 11h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 5 | 43d 19h | Sun 13 Dec, 03:17 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 20 Sep, 03:17 UTC40d 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
- 123.185.209.177:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 20 Sep 2026, 03:17 UTC
- hostname
- –
- first seen
- 18 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 · 59 on average | 58/200 |
| 1 | JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイド | EA · groups of 1000+ · 1x · biweekly · 7 on average | 6/69 |
| 2 | [喜相逢] PVE丨仿官原倍丨萌新养老 | EA · groups of 12+ · biweekly · 5 on average | 4/100 |
| 3 | [PVE][JP] そば鯖 Raidable Bases 初心者大歓迎 | EA · groups of 16+ · biweekly · 4 on average | 1/50 |
| 4 | 『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老 | EA · groups of 8+ · biweekly · 3 on average | 10/100 |
| 5 | [JPN] IKKUNN Server B (Tokyo) |Japan PvE [ASIA] | EA · groups of 8+ · biweekly · 2 on average | 5/40 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does 单人PVE rank?
Player hours over seven days put 单人PVE at #13,815, in the top – of the ranked set.
How full does 单人PVE run?
The current row shows 单人PVE offline; the last response was 40 days 2 hours ago.
Server data
What Rust version does 单人PVE run?
Rust network protocol 2633 and build 163794 on Windows is what 单人PVE runs. Steam updates your game for you, but the protocol must match to join.
How reliable is 单人PVE, and is it online now?
The latest sample has 单人PVE offline, with a last sighting 40 days 2 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 18 September 2026.
Which location does 单人PVE run from?
The name of 单人PVE points to Asia, even though no region tag is published. 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.209.177:28015.
Rules, settings, map
What rules and settings are recorded for 单人PVE?
No gather rate appears in the name: 单人PVE. No custom cap; the default of 8 players per group stands. Recorded as pve, player combat is not allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC off.
Which map has 单人PVE loaded?
The game generates its map: procedural, on 单人PVE.
Wipe data
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. Sunday 1 November at 03:17 UTC is when the next wipe is due. This world was created 40 days 4 hours ago. A fortnightly wipe schedule is published in its tags.
On 单人PVE, what happens on wipe day?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which lists on Rust Data hold 单人PVE, and which filters?
These Rust Data lists include 单人PVE: 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): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): Recorded game build: 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^b (Biweekly): Two weeks between wipes; ^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 to join 单人PVE?
In Rust, F1 opens the console: type client.connect 123.185.209.177:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.