RUST METRICSFlight deck · live data
Data live Servers11,621 Players32,314 Populated2,788 Fresh wipes 3 h65 Scan5 min
‹ All servers202.189.9.186:28027
Offline Full Queue Fresh wipe Wipe due No query

【双赢PVE】原倍/养老/突袭/死亡不掉

Offline 202.189.9.186:28027 checked 44d ago

monthly wipes oxidepve
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 50 100 150 200 PAX 5 /200

Players now

2% 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#8,899no region published
Last wipe55d agomonthly schedule
Next wipe7d 13hThu 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
12.5k5k7.5k10k20 Sep21 Sep
PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 7d 13h. The force wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 timing

What wipe timing does 【双赢PVE】原倍/养老/突袭/死亡不掉 follow?

From the force wipe, the next wipe of 【双赢PVE】原倍/养老/突袭/死亡不掉 is an estimate. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world it runs now was made 55 days 11 hours ago. A monthly wipe schedule is published in its tags.

Tag meanings

How should you read the tags on 【双赢PVE】原倍/养老/突袭/死亡不掉?

These are the tags 【双赢PVE】原倍/养老/突袭/死亡不掉 publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp200 (Max players): 200 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^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.

Which lists and filters on Rust Metrics show 【双赢PVE】原倍/养老/突袭/死亡不掉?

Rust Metrics lists featuring 【双赢PVE】原倍/养老/突袭/死亡不掉: Rust community servers: live readings and Rust PvE servers. Reading: server list filters. It comes up under 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.

Population

What position does 【双赢PVE】原倍/养老/突袭/死亡不掉 hold among Rust servers?

Player hours over seven days put 【双赢PVE】原倍/养老/突袭/死亡不掉 at #8,899, in the top – of all ranked servers.

What player count does 【双赢PVE】原倍/养老/突袭/死亡不掉 carry?

Status for 【双赢PVE】原倍/养老/突袭/死亡不掉: offline. Last seen 44 days 12 hours ago.

Server details

Where does 【双赢PVE】原倍/养老/突袭/死亡不掉 sit?

Check: location. No region tag comes from 【双赢PVE】原倍/养老/突袭/死亡不掉, but the name points to Asia. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 202.189.9.186:28027.

What Rust version is 【双赢PVE】原倍/养老/突袭/死亡不掉 on?

Version check: Rust network protocol 2633 and build 163794 on Windows, run by 【双赢PVE】原倍/养老/突袭/死亡不掉. Matching protocol is required to join. Let Steam update your game.

Is 【双赢PVE】原倍/养老/突袭/死亡不掉 up, and how often does it stay up?

Reading: offline. 【双赢PVE】原倍/养老/突袭/死亡不掉 last answered 44 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

What rules does 【双赢PVE】原倍/养老/突袭/死亡不掉 enforce, and what are its settings?

Reading the name gives no gather rate for 【双赢PVE】原倍/养老/突袭/死亡不掉. 8 players per group, the default value. pve, no combat against other players — that is the game mode. Listing: Community server. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is 【双赢PVE】原倍/养老/突袭/死亡不掉 on?

Procedural map on 【双赢PVE】原倍/养老/突袭/死亡不掉, made by the game's generator.

Join

How can you get onto 【双赢PVE】原倍/养老/突袭/死亡不掉?

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

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$r?,v2633,^m,^p,gmvanilla,cs163794,ts8,^o

Game

gmvanilla
Game mode Survival on vanilla settings.
mp200
Max players 200 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build The server runs game build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

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.