Rust Server TrendsSeismic network · station log
Recording Stations11,617 Players33,246 Active2,800 Wipes · 3 h72 48 h

Station XX-8497 · no signal

【双赢PVE】原倍/事件/萌新/突袭/死亡不掉

Offline 202.189.9.186:28067 checked 17d 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
#8,497
top 38%
Last wipe
27d ago
monthly schedule
Next wipe
7d 12h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station XX-8497 · 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, measured since 17 Sep. 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 Sep26 Sep1 Oct7 Oct12 Oct18 Oct

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

Expected events

Wipe schedule

force wipes only

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

wipe-day peak
16players, last three wipes

Coming wipes

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

The first 48 hours of its last wipes

05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 16, 13 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 1 Oct, 18:24 UTC FW27d ago M1.2rising 16 – running 1

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
24/ 200
[SEA] RustEZ Pure PvE | Low Decay | No Killing | No Raiding EA · groups of 8+ · monthly · 17 on average
17/ 200
JP RustPvE kokuu Server No kill No raid beeginner EA · groups of 8+ · monthly · 16 on average
2/ 200
Kiyo Server JP PVE EA · groups of 20+ · monthly · 5 on average
5/ 30
[SEA] tRust SG PvE Monthly Vanilla EA · groups of 8+ · monthly · 5 on average
2/ 50
【旧梦PVE】 萌新学习 | 原版养老 | 禁抄家打架 EA · groups of 15+ · monthly · 5 on average
4/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?

Generated by the game, the map on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 is procedural, size 5,000 with seed 777840786. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?

You will find no gather rate in the name of 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉. At the game's default, groups can have up to 8 players. It plays in pve mode, no player-versus-player fighting. The server browser lists it under Community, as a community server. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Player counts

How many players are recorded on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 right now?

A reading taken now finds 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 offline; the most recent activity was 17 days 16 hours ago.

How does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 rank against other Rust servers?

Over the last seven days, 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 recorded enough player hours to reach #8,497 worldwide, placing it in the top 38% of all ranked servers.

Server facts

How reliably does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 stay online?

【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 is down at the moment; the last recorded contact was 17 days 16 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 15 September 2026.

Where in the world is 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 hosted?

The name of 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 points to Asia, even though it 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 202.189.9.186:28067.

What build of Rust does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 use?

On Windows, 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 runs Rust network protocol 2634 and build 166494. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?

16 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 13 hours after the wipe.

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

Once a month 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 wipes, at the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. It has run its current world for 27 days 11 hours. Its tags state a monthly wipe schedule.

Lists and tags

What do the server tags on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 mean?

The game's server browser reads the tags 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 publishes: gmvanilla (Game mode): You'll find vanilla survival here; mp200 (Max players): The server has 200 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166494 (Build): The game build is 166494; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): Oxide (uMod) is the plugin framework running here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 appear?

The Rust Server Trends lists that take in 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 are: Rust community servers without the side modes and Rust PvE servers. On the server list, the filters it matches are: 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 202.189.9.186:28067 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. For the website, go to https://www.rustnm.com/.

Instrument codes

Server tags

what each one means

Published as mp200,ptrak,$r?,v2634,^m,^p,gmvanilla,cs166494,ts8,^o

Game

gmvanilla
Game mode You'll find vanilla survival here.
mp200
Max players The server has 200 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs166494
Build The game build is 166494.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Wipe schedule

^m
Monthly Once a month it wipes, with the force wipe from Facepunch.

Gameplay

^p
PvE There's no player combat; the world provides the threat.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running 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.