Station XX-15308 · no signal
Local PVE | Closed test
Offline 203.23.178.51:28015 checked 10d ago
- Players now
- 0/ 4
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,308
- top 70%
- Last wipe
- 10d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 4 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 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.
- usual gap
- 6.8 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 19 Oct, 10:24 UTC10d ago | M0.0▼falling | 0 | – | running | 1 | |
| Mon 12 Oct, 14:41 UTC16d ago | M0.0▲rising | 1 | – | 6.8 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on Local PVE | Closed test?
A procedural map runs on Local PVE | Closed test, generated by the game.
Which settings and rules apply on Local PVE | Closed test?
You will find no gather rate in the name of Local PVE | Closed test. At the game's default, groups can have up to 8 players. In pve mode, no player-versus-player fighting. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.
Live population
How many players are recorded on Local PVE | Closed test right now?
A reading taken now finds Local PVE | Closed test offline; the most recent activity was 10 days 1 hours ago.
How does Local PVE | Closed test rank against other Rust servers?
The last seven days of player hours place Local PVE | Closed test at #15,308, in the top 70% of all ranked servers.
Server facts
How reliably does Local PVE | Closed test stay online?
No contact with Local PVE | Closed test right now, and the last recorded contact was 10 days 1 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 21 September 2026 is when Rust Server Trends first recorded it.
Where in the world is Local PVE | Closed test hosted?
Nothing about a region comes from Local PVE | Closed test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 203.23.178.51:28015.
What build of Rust does Local PVE | Closed test use?
On Windows, Local PVE | Closed test runs Rust network protocol 2634 and build 167781. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on Local PVE | Closed test?
The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does Local PVE | Closed test run its wipes?
Too few wipes of Local PVE | Closed test are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 10 days 2 hours.
Server tags
What do the server tags on Local PVE | Closed test mean?
The game's server browser reads the tags Local PVE | Closed test publishes: gmrust (Game mode): The game mode is standard Rust survival; mp4 (Max players): Slots: 4; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Local PVE | Closed test appear?
These Rust Server Trends lists include Local PVE | Closed test: Modded Rust servers, tracked live and Rust PvE servers. You will find it under these filters 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.
Connecting
What steps get you onto Local PVE | Closed test?
You can connect by pressing F1 in Rust and typing client.connect 203.23.178.51:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.