StatusLive Servers online11,790 Players66,598 Populated3,624 Wiped · 3 h126 Interval5 min Date28 OCT 2026

DWG RG-S10447Server sheetchecked 8m ago

末日仙途|死亡不掉|玩家数据一年清理一次|免

Online 153.35.147.23:10066 checked 8m ago

monthly wipes vanillaoxidepve
Connect
Players now 0/ 100 0% full
7-day average0peak 2
Rank#10,447top 47%
Last wipe26d agomonthly schedule
Next wipe7d 21hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

AveragePeak
00.511.5222:0007:0016:0001:0010:0020:00

Hourly average and peak, UTC.

Fig. 1Players on 末日仙途|死亡不掉|玩家数据一年清理一次|免
Fig. 2

Server performance

025507510022:0007:0016:0001:0010:0020: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 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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 47% of all ranked servers. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

force wipes only

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

wipe-day peak1players, last three wipes

Coming wipes

  1. 7d 21hThu 5 Nov, 19:00 UTCFW
  2. 35d 21hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

00.250.50.751+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 1, 30 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 22:18 UTC FW26d ago 1 – 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 30+ · monthly · 22 on average
4 / 200
02
[SEA] RustEZ Pure PvE | Low Decay | No Killing | No RaidingEA · groups of 8+ · monthly · 17 on average
7 / 200
03
JP RustPvE kokuu Server No kill No raid beeginnerEA · groups of 8+ · monthly · 16 on average
3 / 200
04
Kiyo Server JP PVEEA · groups of 20+ · monthly · 5 on average
1 / 30
05
[SEA] tRust SG PvE Monthly VanillaEA · groups of 8+ · monthly · 5 on average
1 / 50
06
【旧梦PVE】 萌新学习 | 原版养老 | 禁抄家打架EA · groups of 15+ · monthly · 5 on average
4 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

Is 末日仙途|死亡不掉|玩家数据一年清理一次|免 online, and what uptime has been recorded?

At this moment 末日仙途|死亡不掉|玩家数据一年清理一次|免 is online. About 19 hours ago is when it last restarted, measured from the uptime it reports. 168 of 168 hours up over the last 7 full days, which is 100% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.

What does the recorded performance of 末日仙途|死亡不掉|玩家数据一年清理一次|免 show?

The last 48 hours give an average of 68 server fps and a floor of 44. Counted at its highest: 139,735 entities, buildings, deployables and the rest of the world included. Memory use peaked at 3,929 MB. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for 末日仙途|死亡不掉|玩家数据一年清理一次|免?

Asia is where the name of 末日仙途|死亡不掉|玩家数据一年清理一次|免 points, with no region tag published. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 153.35.147.23:10066.

On which Rust version is 末日仙途|死亡不掉|玩家数据一年清理一次|免 running?

The platform is Windows and the version is Rust network protocol 2635 and build 168909 on 末日仙途|死亡不掉|玩家数据一年清理一次|免. To join, your game must be on the same protocol; Steam handles the update.

Population

What player count is recorded on 末日仙途|死亡不掉|玩家数据一年清理一次|免?

0 of 100 slots on 末日仙途|死亡不掉|玩家数据一年清理一次|免 are taken at the latest refresh. Averaged across seven days, the player count is 0, with a peak of 2. The 48-hour peak falls at 11:00 UTC, averaging 1 players.

In the rankings, which position does 末日仙途|死亡不掉|玩家数据一年清理一次|免 hold?

Over the last seven days, 末日仙途|死亡不掉|玩家数据一年清理一次|免 records #10,447 for player hours: the top 47% of all ranked servers.

Schedules

On 末日仙途|死亡不掉|玩家数据一年清理一次|免, what does the data show for wipe day?

At their busiest, its recent wipes drew 1 players on average. At 30 hours after the latest wipe the crowd was at its peak.

On 末日仙途|死亡不掉|玩家数据一年清理一次|免, when do wipes occur?

The force wipe is the only wipe at 末日仙途|死亡不掉|玩家数据一年清理一次|免, once a month. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The world it runs now was made 26 days 23 hours ago. A wipe every month is the schedule its tags set out.

Rules and settings

Which settings does 末日仙途|死亡不掉|玩家数据一年清理一次|免 run, and what rules?

Gather rate for 末日仙途|死亡不掉|玩家数据一年清理一次|免: not stated in the name. The group limit is 9 players. It runs the pve game mode, no fighting other players. The server browser lists it under Community. Plugins run: Oxide. It describes itself as vanilla, by which it means rates, kits and rules are unchanged from Facepunch's release. Anti-cheat: VAC, from Valve, is off.

What is the map for 末日仙途|死亡不掉|玩家数据一年清理一次|免?

末日仙途|死亡不掉|玩家数据一年清理一次|免 runs a procedural map of size 4,500 with seed 1337, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Filters

On Rust Graphs, which lists and filters contain 末日仙途|死亡不掉|玩家数据一年清理一次|免?

These Rust Graphs lists include 末日仙途|死亡不掉|玩家数据一年清理一次|免: Rust community servers, plotted, PvE Rust servers, plotted and Vanilla Rust servers. It is returned by these filters on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v, PvE ^p and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Which meaning is attached to each tag on 末日仙途|死亡不掉|玩家数据一年清理一次|免?

Tags published by 末日仙途|死亡不掉|玩家数据一年清理一次|免, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp100 (Max players): Slots: 100; ts9 (Group limit): The team limit is 9; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^m (Monthly): Facepunch's force wipe brings a monthly wipe; ^v (Vanilla): Rates, kits and rules are unchanged from Facepunch's release; ^p (PvE): Player fights are off; the world supplies the danger; ^o (Oxide): Plugin framework: Oxide (uMod). Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

By whom is 末日仙途|死亡不掉|玩家数据一年清理一次|免 run?

The same operator most likely runs 末日仙途|死亡不掉|玩家数据一年清理一次|免 and 8 other servers we track, since all publish a 2ust.cn hostname.

How to join

How is 末日仙途|死亡不掉|玩家数据一年清理一次|免 joined?

Connect with client.connect 153.35.147.23:10066: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. You will find its website at https://68509.cn.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp100
Max players Slots: 100.
ts9
Group limit The team limit is 9.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Wipe schedule

^m
Monthly Facepunch's force wipe brings a monthly wipe.

Difficulty

^v
Vanilla Rates, kits and rules are unchanged from Facepunch's release.

Gameplay

^p
PvE Player fights are off; the world supplies the danger.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).

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