Rust Data

rustdata.spaceservers202.189.21.212:21093.ipynb

Run all rust-data · live

‹ All servers

Online 202.189.21.212:21091 checked 12m ago

【月栖】PVE

moddedoxide

Connect

srv = rust.server("202.189.21.212:21093")
print(srv.connect_command)

Right now

srv.summary()
players now 0/300 # 0% full
7-day average 0 # peak 1
rank #14,154 # top 64%
last wipe 28d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123405:0014:0000:0008:0017:0002:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608005:0014:0000:0008:0017:0002:00

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 best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

Top 64% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap2.6 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 2 OctSat 26 SepSat 26 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 00:29 UTC28d ago 2 NaN running 0
1 Sat 26 Sep, 10:48 UTC33d ago 2 held half 5.6 days 1
2 Sat 26 Sep, 03:11 UTC34d ago 2 NaN 0.3 days 1
3 Wed 23 Sep, 13:22 UTC36d ago 3 held half 2.6 days 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

4500 · seed 713654521
Map of 【月栖】PVE
map
Procedural Map
size
4500
seed
713654521
Open on RustMaps

Server

srv.info()
address
202.189.21.212:21091
region
–
max players
300
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 00:52 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0QS『芬达』100000倍/10.30/枪战/蓝图全解/萌新/建造EA · groups of 20+ · weekly · 25 on average35/100
1【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐EA · groups of 8+ · weekly · 21 on average0/200
2[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 14 on average0/100
3[守护]100倍PVE/迷雾僵尸/突袭基地/等级武直/萌新EA · no group limit · 13 on average20/100
4#10-[搞就完了]10倍/10.30新档/无权/萌新首选EA · no group limit · 12 on average17/100
5[霸道]10000000倍-10.30日-萌新首选-稳定长久EA · no group limit · 12 on average19/100

Quick answers

From the figures on this page.

Population data

What position does 【月栖】PVE take in the server rankings?

Over the last seven days 【月栖】PVE sits at #14,154 on player hours, in the top 64% of ranked servers.

What population does 【月栖】PVE carry?

The sample now reads 0 players for 【月栖】PVE, out of 300 slots. Over the last seven days it averaged 0 players and peaked at 1.

Server facts

How smoothly does 【月栖】PVE run?

Server fps over the last 48 hours averages 45; the floor is 19. The entity count peaked at 145,941, covering buildings, deployables and the rest of the world. Memory peaked at 4,197 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is 【月栖】PVE on?

Version Rust network protocol 2635 and build 167231 on Linux is reported by 【月栖】PVE. Joining needs the same protocol on your game; Steam handles the update.

How reliable is 【月栖】PVE, and is it online now?

Online is the state at the latest refresh for 【月栖】PVE. A restart about 3 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is 【月栖】PVE hosted?

Its name points to Asia, but 【月栖】PVE publishes no region tag. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 202.189.21.212:21091 is its address.

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. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.

What is the map on 【月栖】PVE?

Size 4,500, seed 713654521: the procedural map on 【月栖】PVE, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

On what schedule does 【月栖】PVE wipe?

No next wipe can be predicted for 【月栖】PVE, which wipes at irregular times. 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 28 days 3 hours ago.

On 【月栖】PVE, what happens on wipe day?

Recent wipes averaged 2 players at their peak. The crowd on the latest wipe topped out 2 hours after it began. Half the peak or more was held to the next wipe in 100% of recent wipes.

Tags and filters

Where does 【月栖】PVE appear among Rust Data lists and filters?

These Rust Data lists include 【月栖】PVE: Modded Rust servers. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on 【月栖】PVE?

The game's server browser reads these tags from 【月栖】PVE: gmrust (Game mode): Survival play, standard Rust; mp300 (Max players): 300 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs167231 (Build): Recorded game build: 167231; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way to join 【月栖】PVE?

In Rust, F1 opens the console: type client.connect 202.189.21.212:21091. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp300,ptrak,$r?,v2635,gmrust,cs167231,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp300
Max players 300 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs167231
Build Recorded game build: 167231.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Modded listing: the game is changed by plugins or settings.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Rust Data 41,075 players 11,634 servers online