Offline 203.23.178.51:28015 checked 10d ago
Local PVE | Closed test
Connect
srv = rust.server("203.23.178.51: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 bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 19 Oct, 10:24 UTC10d ago | 0 | NaN | running | 1 |
| 1 | Mon 12 Oct, 14:41 UTC17d ago | 1 | NaN | 6.8 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
- 203.23.178.51:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 10:24 UTC
- hostname
- –
- first seen
- 21 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 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 246 on average | 280/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 242 on average | 111/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 102 on average | 102/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 59 on average | 32/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 53 on average | 56/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 50 on average | 14/100 |
Quick answers
From the figures on this page.
Population data
How does Local PVE | Closed test compare in the rankings?
Rank #15,308 on seven-day player hours for Local PVE | Closed test, within the top 70% of all ranked servers.
How full does Local PVE | Closed test run?
Local PVE | Closed test returns no live count at this refresh, having last been seen 10 days 14 hours ago.
About the server
Which Rust version is Local PVE | Closed test on?
Version Rust network protocol 2634 and build 167781 on Windows is reported by Local PVE | Closed test. Joining needs the same protocol on your game; Steam handles the update.
Is Local PVE | Closed test up, and what does its uptime show?
Offline now for Local PVE | Closed test, last seen 10 days 14 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 21 September 2026.
Which location does Local PVE | Closed test run from?
There is no region published for Local PVE | Closed test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 203.23.178.51:28015.
Rules, settings, map
Which rules apply on Local PVE | Closed test, and what settings?
The name Local PVE | Closed test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as pve, no combat between players. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Local PVE | Closed test selected?
Local PVE | Closed test runs a procedural map, which the game generates.
Wipe schedule
When does Local PVE | Closed test wipe, and on what schedule?
Too few wipes are on record for Local PVE | Closed test to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 10 days 15 hours ago.
On Local PVE | Closed test, what happens on wipe day?
Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which Rust Data filters and lists contain Local PVE | Closed test?
The Rust Data lists that Local PVE | Closed test fits are: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on Local PVE | Closed test?
The game's server browser reads these tags from Local PVE | Closed test: 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; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 Local PVE | Closed test?
The manual route: launch Rust, F1, then client.connect 203.23.178.51:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.