Local PVE | Closed test
Offline 203.23.178.51:28015 checked 10d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot 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| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 19 Oct, 10:24 UTC10d ago | 0 | – | running | 1 |
| Mon 12 Oct, 14:41 UTC17d ago | 1 | – | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 254 on average | 135 / 2000 |
| [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 243 on average | 267 / 2000 |
| Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 107 on average | 43 / 200 |
| 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 58 on average | 74 / 200 |
| [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 54 on average | 34 / 300 |
| TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 49 on average | 65 / 100 |
Quick answers
from the figures on this pageWipe data
On what cycle does Local PVE | Closed test wipe?
With too few of its wipes on record, Local PVE | Closed test's rhythm is not yet clear. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. 10 days 4 hours ago the current world was made.
On Local PVE | Closed test, what happens on wipe day?
The average busiest count over recent wipes is 0 players. The highest player count on the latest wipe arrived 0 hours in.
Server details
Which location hosts Local PVE | Closed test?
No region appears in what Local PVE | Closed test publishes. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. The address of the server is 203.23.178.51:28015.
What Rust build does Local PVE | Closed test run?
On Windows, Local PVE | Closed test runs Rust network protocol 2634 and build 167781. Your game must match the protocol to join, and Steam applies that update.
What uptime does Local PVE | Closed test show, and is it up?
The current status is offline for Local PVE | Closed test, with the last sighting 10 days 3 hours ago. 0% uptime over the last 7 full days, equal to 0 of 168 hours. 21 September 2026 is when Rust Server Analytics first recorded it.
Tags
How should the tags on Local PVE | Closed test be read?
The game's server browser reads the tags Local PVE | Closed test publishes: gmrust (Game mode): Survival in the standard Rust format; mp4 (Max players): 4 slots in total; ts8 (Group limit): Team cap of 8, the stock game setting; v2634 (Protocol): Protocol 2634 is required: your game must match to connect; cs167781 (Build): Game build: 167781; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): A region code is not set; ^p (PvE): No fighting between players, with the world as the threat; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): The Modded section, because plugins or settings modify play. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
Where does Local PVE | Closed test appear across Rust Server Analytics's lists and filters?
The following Rust Server Analytics lists count Local PVE | Closed test among their servers: Modded Rust servers: live data and PvE Rust servers by live population. It appears on the server list under the following filters: 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.
Player numbers
What position does Local PVE | Closed test hold in the server rankings?
The seven-day player-hours rank for Local PVE | Closed test is #15,308, inside the top 70% of all ranked servers.
At what level does Local PVE | Closed test run its population?
The last sighting of Local PVE | Closed test was 10 days 3 hours ago; it is offline at this refresh.
Map and rules
What settings and rules does Local PVE | Closed test use?
No gather rate is given in the name of Local PVE | Closed test. The default group cap of 8 players applies. pve is the game mode, no fighting other players. Plugins or settings modify the game, and it is listed as Modded. The plugin framework is Oxide. Anti-cheat status: VAC on.
What is the map for Local PVE | Closed test?
Local PVE | Closed test uses a procedural map, which the game generates.
How to join
How do you connect to Local PVE | Closed test?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 203.23.178.51:28015.