StatusLive Servers online11,806 Players74,886 Populated3,724 Wiped · 3 h106 Interval5 min Date28 OCT 2026

DWG RG-S12577Server sheetchecked 34d ago

【叶问PVE】硬核/禁科技树/慢节奏/养老/事件

Offline EA 43.142.161.97:29500 checked 34d ago

teams off biweekly wipes moddedoxidepvehardcore
Connect
Players now 2/ 100 2% full
7-day average0peak –
Rank#12,577top 56% · #447 in EA
Last wipe40d agobiweekly schedule
Next wipe1d 14hFri 30 Oct, 11:17 UTC
Fig. 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Fig. 1Players on 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件
Fig. 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep22 Sep24 Sep27 Sep29 Sep1 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 11:17 UTC, in 1d 14h. Its biweekly schedule tag · low confidence

wipe-day peak6players, last three wipes

Coming wipes

  1. 1d 14hFri 30 Oct, 11:17 UTC
  2. 7d 21hThu 5 Nov, 19:00 UTCFW
  3. 15d 14hFri 13 Nov, 11:17 UTC
  4. 29d 14hFri 27 Nov, 11:17 UTC
  5. 35d 21hThu 3 Dec, 19:00 UTCFW
  6. 43d 14hFri 11 Dec, 11:17 UTC

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 18 Sep, 11:17 UTC40d ago 6 – running 0

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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 60 on average
18 / 200
02
[JP][PvE]mameserver初心者おいで!EA · groups of 8+ · biweekly · 8 on average
1 / 65
03
JP 1x-10x PVE++|XPレベル1000|火山|ペット|NPCレイドEA · groups of 1000+ · 1x · biweekly · 7 on average
2 / 69
04
[喜相逢] PVE丨仿官原倍丨萌新养老EA · groups of 12+ · biweekly · 5 on average
1 / 100
05
[PVE][JP] そば鯖 Raidable Bases 初心者大歓迎EA · groups of 16+ · biweekly · 4 on average
0 / 50
06
『白云PVE』 原倍 | 模组 | 事件 | 萌新 | 养老EA · groups of 8+ · biweekly · 3 on average
2 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

How reliable is 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件, and is it online now?

Last seen 34 days 3 hours ago; right now 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件 is offline. 0 of 168 hours up over the last 7 full days, which is 0% of the time. First seen by Rust Graphs on 13 September 2026.

In which location is 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件 hosted?

In Asia 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件 lists itself, tagged EA. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 43.142.161.97:29500.

On which Rust version is 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件 running?

On Windows, 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件 runs Rust network protocol 2633 and build 162929. The same protocol is required for joining, and Steam updates your game to it.

Counts

What player count is recorded on 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件?

No response from 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件; the server was last seen 34 days 3 hours ago.

In the rankings, which position does 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件 hold?

The same seven-day player-hour count places 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件 at #447 within Asia, #12,577 across all ranked servers and in the top 56% of them.

Wipe data

What happens on 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件 on the day of a wipe?

An average of 6 players was recorded at the busiest point of its recent wipes. 26 hours after the latest wipe, the crowd peaked.

What wipe schedule has been recorded for 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件?

Too few of 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件's wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. Friday 30 October at 11:17 UTC is the date its next wipe is due. 40 days 9 hours ago the current world was made. Its tags give a wipe schedule of one wipe every two weeks.

Settings

Which rules and settings are recorded for 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件?

The name of 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件 records no gather rate. No group limit is published. hardcore, The hardest of Facepunch's modes, is the game mode. PvP and raiding are on. Listed as Modded in the server browser: the game is changed by plugins or settings. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is on.

What is the map for 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件?

Size 4,250: that is the procedural map 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件 generates in game.

Filters

Where does 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件 appear among the Rust Graphs lists and filters?

On Rust Graphs, 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件 is placed in these lists: Modded Rust servers and PvE Rust servers, plotted. These filters on the server list return it: Region: Asia; Type: Modded; Game mode: PvE and Hardcore; Server tag: Biweekly ^b, Hardcore ^h, PvE ^p, Modded ^z and Oxide ^o; Wipe schedule: Every two weeks.

On 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件, what is meant by each tag?

Tags published by 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件, and read by the game's server browser: gmhardcore (Game mode): A harsher ruleset: hardcore; mp100 (Max players): The slot count is 100; ts0 (Group limit): Team play is off; v2633 (Protocol): To join, your game must be on protocol 2633; cs162929 (Build): 162929 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^b (Biweekly): Every two weeks it wipes; ^h (Hardcore): Fewer helpers and harsher survival: Facepunch's hardcore mode; ^p (PvE): The world is the danger; players do not fight each other; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; EA (East Asia): The server browser lists it under East Asia. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Connect

By what method do you join 【叶问PVE】硬核/禁科技树/慢节奏/养老/事件?

In Rust, press F1 and type client.connect 43.142.161.97:29500 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. You will find its website at https://qun.qq.com/universal-share/share?ac=1&authKey=aewITgrL67hbs7B1JbAGS41KVp7%2BBDl6ZPqX%2BWp3i1sUVqY9l61K%2BkfyTj24tchU&busi_data=eyJncm91cENvZGUiOiI4NjA1ODc1MzMiLCJ0b2tlbiI6IjVGcXVDUmhmZmhpaHQ1aHZGOWhqWWQwc1o0QWhWS0ZZQjYybzdYNGdkZXd2V04rZVRpdE9nQW5oQzh6QkZ4RnUiLCJ1aW4iOiI2MjQzMjM5MDMifQ%3D%3D&data=_QqJMlI0BAMkR-bXSnTSQAlKTb23Ai2iOf2X6I4IkHdOvcExflgKjaHUCTdfn9_g76EyWbn9jDo6NtoC-2hbMeXyE_sNJqSvd6rMypxRbhU&svctype=5&tempid=h5_group_info.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,^b,^h,EA,^p,gmhardcore,cs162929,ts0,^o^z

Game

gmhardcore
Game mode A harsher ruleset: hardcore.
mp100
Max players The slot count is 100.
ts0
Group limit Team play is off.
v2633
Protocol To join, your game must be on protocol 2633.
cs162929
Build 162929 is the game build.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is recorded.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Difficulty

^h
Hardcore Fewer helpers and harsher survival: Facepunch's hardcore mode.

Gameplay

^p
PvE The world is the danger; players do not fight each other.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is Modded.

Region

EA
East Asia The server browser lists 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.

KeyTag string decoded