Station XX-13867 · recording
【月栖】PVE
Online 202.189.21.212:21091 checked 8m ago
- Players now
- 0/ 300
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #13,867
- top 62%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 300 slots
- Motion · 24 h
- M0.0■steady+0 players
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 2.6 daysbetween real wipes
- on rhythm
- 33%of its recent wipes
- wipe-day peak
- 2players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 2 Oct, 00:29 UTC27d ago | M0.3▲rising | 2 | – | running | 0 | |
| Sat 26 Sep, 10:48 UTC33d ago | M0.0▲rising | 2 | held half | 5.6 days | 1 | |
| Sat 26 Sep, 03:11 UTC33d ago | M0.0▲rising | 2 | – | 0.3 days | 1 | |
| Wed 23 Sep, 13:22 UTC36d ago | M0.3▲rising | 3 | held half | 2.6 days | 1 |
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 【月栖】PVE?
Generated by the game, the map on 【月栖】PVE is procedural, size 4,500 with seed 713654521. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on 【月栖】PVE?
The name of 【月栖】PVE gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on 【月栖】PVE right now?
At this moment, 【月栖】PVE records 0 players across 300 slots. The seven-day average is 0 players, with a peak of 1.
How does 【月栖】PVE rank against other Rust servers?
On player hours for the past week, 【月栖】PVE sits at #13,867, which puts it inside the top 62% of every ranked server.
Server facts
How reliably does 【月栖】PVE stay online?
As recorded now, 【月栖】PVE is running. Its reported uptime points to a restart about 16 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. 13 September 2026 is when Rust Server Trends first recorded it.
How well does 【月栖】PVE perform under load?
The 48-hour average is 46 server fps; 19 is the lowest observed. The world held up to 145,941 entities at its peak, buildings and deployables included. It reached a ceiling of 3,969 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.
Where in the world is 【月栖】PVE hosted?
No region tag comes from 【月栖】PVE, though the name points to Asia. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 202.189.21.212:21091.
Which Rust version is 【月栖】PVE running?
Rust network protocol 2635 and build 167231 on Linux is what 【月栖】PVE runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on 【月栖】PVE?
On average, the busiest point of its recent wipes drew 2 players. 2 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
How often does 【月栖】PVE wipe, and on which days?
There is no next wipe to predict at 【月栖】PVE, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 27 days 16 hours.
Lists and tags
What do the server tags on 【月栖】PVE mean?
These are the tags 【月栖】PVE publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp300 (Max players): 300 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs167231 (Build): The game build is 167231; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does 【月栖】PVE appear?
These Rust Server Trends lists include 【月栖】PVE: Modded Rust servers, tracked live. You will find it under these filters on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
What steps get you onto 【月栖】PVE?
To join, enter client.connect 202.189.21.212:21091 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.