Rust Server TrendsSeismic network · station log
Recording Stations11,756 Players64,636 Active3,440 Wipes · 3 h196 48 h

Station XX-9016 · no signal

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

Offline 110.42.36.220:28015 checked 45d ago

monthly wipes oxidepve
Connect
Players now
9/ 200
4% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#9,016
no region published
Last wipe
55d ago
monthly schedule
Next wipe
7d 7h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station XX-9016 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
9of 200 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep21 Sep
Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍 EA · groups of 30+ · monthly · 22 on average
41/ 200
[SEA] RustEZ Pure PvE | Low Decay | No Killing | No Raiding EA · groups of 8+ · monthly · 17 on average
25/ 200
JP RustPvE kokuu Server No kill No raid beeginner EA · groups of 8+ · monthly · 16 on average
32/ 200
Kiyo Server JP PVE EA · groups of 20+ · monthly · 5 on average
8/ 30
[SEA] tRust SG PvE Monthly Vanilla EA · groups of 8+ · monthly · 5 on average
8/ 50
【旧梦PVE】 萌新学习 | 原版养老 | 禁抄家打架 EA · groups of 15+ · monthly · 5 on average
8/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

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

A procedural map runs on 【双赢PVE】原倍/养老/突袭/死亡不掉, generated by the game.

Which settings and rules apply on 【双赢PVE】原倍/养老/突袭/死亡不掉?

The name of 【双赢PVE】原倍/养老/突袭/死亡不掉 gives no gather rate. Groups hold up to 8 players, which is the default for the game. pve is the game mode, no combat against other players. It is a community server, and the browser lists it under Community. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Population

How many players are recorded on 【双赢PVE】原倍/养老/突袭/死亡不掉 right now?

【双赢PVE】原倍/养老/突袭/死亡不掉 is not responding at this moment and is offline, last seen 45 days 7 hours ago.

How does 【双赢PVE】原倍/养老/突袭/死亡不掉 rank against other Rust servers?

Over the last seven days, 【双赢PVE】原倍/养老/突袭/死亡不掉 recorded enough player hours to reach #9,016 worldwide, placing it in the top – of all ranked servers.

Server facts

How reliably does 【双赢PVE】原倍/养老/突袭/死亡不掉 stay online?

【双赢PVE】原倍/养老/突袭/死亡不掉 is down at the moment; the last recorded contact was 45 days 7 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 13 September 2026 is when Rust Server Trends first recorded it.

Where in the world is 【双赢PVE】原倍/养老/突袭/死亡不掉 hosted?

Its name points to Asia, but 【双赢PVE】原倍/养老/突袭/死亡不掉 publishes no region tag. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 110.42.36.220:28015.

What build of Rust does 【双赢PVE】原倍/养老/突袭/死亡不掉 use?

【双赢PVE】原倍/养老/突袭/死亡不掉 is running Rust network protocol 2633 and build 162929 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

How often does 【双赢PVE】原倍/养老/突袭/死亡不掉 wipe, and on which days?

From the force wipe the next wipe of 【双赢PVE】原倍/养老/突袭/死亡不掉 is estimated. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. It has run its current world for 55 days 17 hours. A monthly wipe schedule is published in its tags.

Server tags

What do the server tags on 【双赢PVE】原倍/养老/突袭/死亡不掉 mean?

These are the tags 【双赢PVE】原倍/养老/突袭/死亡不掉 publishes for the browser to read: gmvanilla (Game mode): Survival in vanilla mode; mp200 (Max players): 200 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs162929 (Build): Game build: 162929; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^m (Monthly): Wipes happen monthly, at the same time as Facepunch's force wipe; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): A plugin framework, Oxide (uMod), runs here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does 【双赢PVE】原倍/养老/突袭/死亡不掉 appear?

You will find 【双赢PVE】原倍/养老/突袭/死亡不掉 on the following Rust Server Trends lists: Rust community servers without the side modes and Rust PvE servers. You will find it under these filters on the server list: 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.

How to join

How do you connect to 【双赢PVE】原倍/养老/突袭/死亡不掉?

You can connect by pressing F1 in Rust and typing client.connect 110.42.36.220:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmvanilla
Game mode Survival in vanilla mode.
mp200
Max players 200 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs162929
Build Game build: 162929.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

Wipe schedule

^m
Monthly Wipes happen monthly, at the same time as Facepunch's force wipe.

Gameplay

^p
PvE The danger comes from the world, not from other players.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.