Working its way up from the back of the class: #8,497 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
9/ 100
F
Lost ground: down 6,904 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (C); momentum is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Rank
daily · 1 is best
RankRank in region
Top 38% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h.
The force wipe · high confidence
wipe-day peak16players, last three wipes
Coming wipes
7d 11hThu 5 Nov, 19:00 UTCFW
35d 11hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 16, 13 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 18:24 UTCFW27d ago
16
–
running
1
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 sit?
The name of 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 points to Asia, though no region tag is set. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 202.189.9.186:28067.
Is 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 up, and how steady is its uptime?
At this moment, 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 is offline; the last time it was seen was 17 days 17 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 15 September 2026.
On what Rust version does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 sit?
Rust network protocol 2634 and build 166494 on Windows is what 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 wipe, and how often?
【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 wipes with the force wipe and at no other time. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 27 days 13 hours have passed since this world was made. Its tags list a monthly wipe schedule.
What should you expect from wipe day on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
The average peak on its recent wipes was 16 players. Peak numbers came 13 hours into the latest wipe.
Player numbers
What position does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 hold in the rankings?
Over the last seven days, 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 has #8,497 for player hours, in the top 38% of all ranked servers.
Is 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 a busy server?
【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 is offline at the moment; the last time it was seen was 17 days 17 hours ago.
Lists and filters
What do 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉's tags stand for?
The game's browser takes its cue from the tags 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 has set: gmvanilla (Game mode): Survival, vanilla style; mp200 (Max players): 200 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): Build number: 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): The plugin framework in use is Oxide (uMod). Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
Rust Server Score lists that include 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉: Best community servers, graded and Rust PvE servers, graded. It shows under the following 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.
Rules and settings
Which rules does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 enforce, and what are its settings?
You will find no gather rate in the name of 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉. The group limit stays at the game's default of 8 players. It runs pve, no PvP between players. Under Community in the server browser you will find this community server. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 runs which map?
【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 runs a game-generated procedural map at size 5,000, seed 777840786. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
What is the way to join 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
To connect, start Rust, press F1, and type client.connect 202.189.9.186:28067. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://www.rustnm.com/.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,^m,^p,gmvanilla,cs166494,ts8,^o
Game
gmvanilla
Game modeSurvival, vanilla style.
mp200
Max players200 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildBuild number: 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxideThe plugin framework in use is 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.
A term to build on. Strongest in standing (C); momentum is the one to work on (F).