RUST METRICSFlight deck · live data
Data live Servers11,869 Players90,153 Populated3,832 Fresh wipes 3 h374 Scan5 min
‹ All servers202.189.9.186:28024
Offline Full Queue Fresh wipe Wipe due No query

【晴天PVE】原倍|萌新|养老|突袭|死亡不掉

Offline 202.189.9.186:28024 checked 43d ago

monthly wipes oxidepve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,479no region published
Last wipe45d agomonthly schedule
Next wipe7d 3hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep
PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h. The force wipe · high confidence

wipe-day peak3players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 3hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 3hFW

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 14 Sep, 07:20 UTC45d ago 3 – running 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What happens on 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 when wipe day comes?

The busiest point of its recent wipes drew 3 players on average. 7 hours after the wipe, the crowd peaked on the latest wipe.

When does 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 wipe?

The only wipe for 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 is the force wipe, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was made 45 days 7 hours ago. The tags state a wipe schedule of one wipe a month.

Tags

Which tags does 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 carry, and what do they mean?

These are the tags 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163493 (Build): Build 163493; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉: Rust community servers: live readings and Rust PvE servers. Check: filters. On the server list it appears under these: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Occupancy

Where does 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 sit in the rankings?

Player hours over seven days put 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 at #15,479, in the top – of all ranked servers.

What is the population on 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉?

【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 is not responding; status offline, last seen 43 days 10 hours ago.

Server

Which location does 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 run from?

Check: location. No region tag comes from 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉, but the name points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 202.189.9.186:28024.

What Rust version is 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 on?

Rust network protocol 2633 and build 163493 on Windows is the build 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉, and is it online now?

【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 reports offline. The last reading came 43 days 10 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 14 September 2026.

Map and rules

What settings and rules apply on 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉?

No gather rate appears in the name: 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉. No limit is set beyond the default. Groups take up to 8 players. The mode is pve. Note the following: other players are not fought. Under Community in the server browser you will find it. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 on?

Check: map. Procedural, generated by the game, on 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉.

How to join

How can you get onto 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉?

Check: join. Open Rust, press F1, then enter client.connect 202.189.9.186:28024. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,^m,^p,gmvanilla,cs163493,ts8,^o

Game

gmvanilla
Game mode Survival on vanilla settings.
mp100
Max players 100 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163493
Build Build 163493.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.

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.