RUST METRICSFlight deck · live data
Data live Servers11,700 Players43,056 Populated3,055 Fresh wipes 3 h102 Scan5 min
‹ All servers202.189.5.26:28075
Online Full Queue Fresh wipe Wipe due No query

【光头强PVE】原倍/突袭/死亡不掉

Online EA 202.189.5.26:28075 checked 10m ago

monthly wipes vanillamoddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 00:00 UTC
0 38 75 112 150 PAX 0 /150

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 67 SERVER FPS

Server fps

48 h low 48 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 142,821 ×1000

Entities

48 h range 140,756–143,316 · memory 4,663 MB
1239 ET SINCE RESTART 6D 12H

Uptime

6 days 12 hours since its last restart, at the last reading
7-day average0peak 1
Rank#14,336top 64% · #490 in EA
Last wipe6d agomonthly schedule
Next wipe7d 17hThu 5 Nov, 19:00 UTC FW
Memory4,663MBat the last reading
REC 1

Players

AveragePeak
0123402:0011:0020:0005:0014:0000:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608002:0011:0020:0005:0014:0000: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 22 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k22 Oct23 Oct25 Oct26 Oct28 Oct29 Oct

Top 64% of all ranked servers, top 88% in EA. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 7d 17h. 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 schedule

When does 【光头强PVE】原倍/突袭/死亡不掉 wipe?

The estimate for 【光头强PVE】原倍/突袭/死亡不掉's next wipe comes from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 6 days 13 hours ago the current world was made. The tags state a wipe schedule of one wipe a month.

Tags

How should you read the tags on 【光头强PVE】原倍/突袭/死亡不掉?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp150 (Max players): The server holds 150 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; EA (East Asia): East Asia is the browser category it sits in from 【光头强PVE】原倍/突袭/死亡不掉. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does 【光头强PVE】原倍/突袭/死亡不掉 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring 【光头强PVE】原倍/突袭/死亡不掉: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Region: Asia; Type: Vanilla and Modded; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.

Player count

Where does 【光头强PVE】原倍/突袭/死亡不掉 sit in the rankings?

Player hours over the last seven days put 【光头强PVE】原倍/突袭/死亡不掉 at #14,336, #490 in Asia, in the top 64% of all ranked servers.

What is the population on 【光头强PVE】原倍/突袭/死亡不掉?

Current headcount on 【光头强PVE】原倍/突袭/死亡不掉: 0 players, 150 slots available. Seven-day check: 0 players on average. Peak reading: 1.

Operator and location

Where does 【光头强PVE】原倍/突袭/死亡不掉 sit?

Its EA tag places 【光头强PVE】原倍/突袭/死亡不掉 in Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 202.189.5.26:28075.

What Rust version is 【光头强PVE】原倍/突袭/死亡不掉 on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by 【光头强PVE】原倍/突袭/死亡不掉. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for 【光头强PVE】原倍/突袭/死亡不掉?

Over the last 48 hours the average was 61 server fps; the floor was 48. Check: entities. The peak was 143,316, counting buildings, deployables and the rest of the world. Memory peak: 5,026 MB. Expect lag when fps falls and entities climb.

How reliable is 【光头强PVE】原倍/突袭/死亡不掉, and is it online now?

Reading: online. 【光头强PVE】原倍/突袭/死亡不掉 answers right now. By its reported uptime, the last restart was roughly 6 days 12 hours ago. Uptime for the last 6 full days: 143 of 144 hours, or 99%. Reading: first seen 22 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does 【光头强PVE】原倍/突袭/死亡不掉 enforce, and what are its settings?

Reading the name gives no gather rate for 【光头强PVE】原倍/突袭/死亡不掉. No limit is set beyond the default. Groups take up to 8 players. Mode check gives pve; other players are not fought. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Vanilla is the label it uses: the stock game: Facepunch's rates, kits and rules, unchanged. Check: anti-cheat. VAC, Valve's system, is on.

What map is 【光头强PVE】原倍/突袭/死亡不掉 on?

From seed 1, the game generates the procedural map on 【光头强PVE】原倍/突袭/死亡不掉. Its size is 5,000. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How can you get onto 【光头强PVE】原倍/突袭/死亡不掉?

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

PLACARDS

Server tags

what each one means

Published as mp150,ptrak,$r?,v2634,^m,^v,EA,^p,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp150
Max players The server holds 150 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

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

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Gameplay

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

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Region

EA
East Asia East Asia is the browser category it sits in.

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.