RUST METRICSFlight deck · live data
Data live Servers11,605 Players47,288 Populated3,053 Fresh wipes 3 h111 Scan5 min
‹ All servers103.45.137.53:28015
Offline Full Queue Fresh wipe Wipe due No query

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

Offline EA 103.45.137.53:28015 checked 1d ago

monthly wipes vanillamoddedoxidepve
COM 1 · connect

Server instruments

last reading Wed 08:00 UTC
0 25 50 75 100 PAX 2 /100

Players now

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

Server fps

48 h low 43 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 132,848 ×1000

Entities

48 h range 132,848–132,848 · memory 4,660 MB
1239 ET SINCE RESTART 4D 13H

Uptime

4 days 13 hours since its last restart, at the last reading
7-day average1peak 5
Rank#4,525top 20% · #331 in EA
Last wipe28d agomonthly schedule
Next wipe6d 11hThu 5 Nov, 19:00 UTC FW
Memory4,660MB48 h peak 2 players
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, measured since 25 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k25 Sep2 Oct9 Oct16 Oct23 Oct30 Oct

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

PLAN

Wipe schedule

force wipes only

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

usual gap3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak6players, last three wipes
crowd held100%of its cycles kept half the crowd

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC6d 11hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC34d 11hFW

The first 48 hours of its last wipes

Thu 1 OctSat 26 SepFri 25 Sep
02468+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 18:29 UTC FW28d ago 6 – running 0
Sat 26 Sep, 07:57 UTC33d ago 6 held half 5.4 days 0
Fri 25 Sep, 18:38 UTC34d ago 6 – 0.6 days 4

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

Reset cycle

What should you expect from wipe day on 【光头强PVE】原倍/突袭/死亡不掉?

At their busiest, its recent wipes drew 6 players on average. Peak crowd on the latest wipe: 19 hours in. Until the next wipe, the crowd stayed above half that peak in 100% of its recent wipes.

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

Once a month 【光头强PVE】原倍/突袭/死亡不掉 wipes, with the force wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 28 days 13 hours ago. The tags state a wipe schedule of one wipe a month.

Lists and filters

Which tags does 【光头强PVE】原倍/突袭/死亡不掉 carry, and what do they mean?

These are the tags 【光头强PVE】原倍/突袭/死亡不掉 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; 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; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game; EA (East Asia): The server browser files it under East Asia. 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?

On Rust Metrics, 【光头强PVE】原倍/突袭/死亡不掉 sits in these lists: Modded Rust servers, checked live and Rust PvE servers. These filters bring it up on the server list: 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.

Player count

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

Ranked by seven-day player hours, 【光头强PVE】原倍/突袭/死亡不掉 sits at #4,525 and #331 in Asia, inside the top 20%.

What player count does 【光头强PVE】原倍/突袭/死亡不掉 carry?

【光头强PVE】原倍/突袭/死亡不掉 is not responding; status offline, last seen 47 hours ago. Seven-day check: 1 players on average. Peak reading: 5. Check: 48-hour peak. 08:00 UTC, 1 players on average.

Server details

Which location does 【光头强PVE】原倍/突袭/死亡不掉 run from?

【光头强PVE】原倍/突袭/死亡不掉 gives Asia as its location, with the EA tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 103.45.137.53:28015.

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

Reading: 【光头强PVE】原倍/突袭/死亡不掉, Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: 43 server fps on average across the last 48 hours. It never dropped below 43. Reading: 132,848 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 4,660 MB. What players call lag comes from low fps and an entity count on the rise.

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

Check: connection. 【光头强PVE】原倍/突袭/死亡不掉 is offline at this moment. Last contact was 47 hours ago. By its reported uptime, the last restart was roughly 4 days 13 hours ago. Reading: 77% uptime over the last 7 full days. It was up 129 of 168 hours. The first sighting on Rust Metrics was 25 September 2026.

Map and rules

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

No gather rate appears in the name: 【光头强PVE】原倍/突袭/死亡不掉. The group cap is 8 players, which is the default in the game. 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. Check: plugins. It runs Oxide of them. Vanilla is the label it uses: rates, kits and rules are exactly as Facepunch ships them. Anti-cheat reading: VAC off, Valve's system.

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

Size 4,500 and seed 1516028690: the game generates the procedural map on 【光头强PVE】原倍/突袭/死亡不掉 from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

What do you do to join 【光头强PVE】原倍/突袭/死亡不掉?

To join: start Rust, press F1 and type client.connect 103.45.137.53:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^m,^v,EA,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players 100 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
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.

Difficulty

^v
Vanilla Rates, kits and rules are exactly as Facepunch ships them.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

Region

EA
East Asia The server browser files it under East Asia.

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.