Working its way up from the back of the class: #9,901 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
27/ 100
F
Lost ground: down 4,491 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.
AveragePeak
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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.
Rank
daily · 1 is best
RankRank in region
Top 45% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 13h.
The force wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
The name of 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 points to Asia, though no region tag is set. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 202.189.16.87:28215.
Is 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 up, and how steady is its uptime?
You cannot join now: 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 is offline, last seen 17 days 1 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 11 October 2026.
What Rust version is 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 on?
You will find 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 on Rust network protocol 2634 and build 166494, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 wipe its map?
The next wipe on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 is a projection from the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. The world it runs now was created 27 days 11 hours. The tags show a monthly wipe schedule.
Player count
What position does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 hold in the rankings?
In the top 45% of all ranked servers, 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 sits at #9,901 for player hours over the last seven days.
Is 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 a busy server?
The last sighting of 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 was 17 days 1 hours ago, and it is offline right now.
Tags and filters
What is meant by the tags on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
You'll see 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 tagged with gmvanilla (Game mode): This is vanilla survival; mp200 (Max players): 200 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^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): Oxide (uMod) provides the plugin framework here in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 appear in the Rust Server Score lists and filters?
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
What settings and rules apply on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
You will find no gather rate in the name of 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉. With no change from the game default, groups take up to 8 players. It runs pve, no PvP between players. The server browser lists it under Community, as a community server. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 runs which map?
A procedural map, generated by the game, is what 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 runs.
Connecting
How do you get onto 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
To connect, start Rust, press F1, and type client.connect 202.189.16.87:28215. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,^m,^p,gmvanilla,cs166494,ts8,^o
Game
gmvanilla
Game modeThis is vanilla survival.
mp200
Max players200 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166494
BuildBuild number: 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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
OxideOxide (uMod) provides the plugin framework 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.
A term to build on. Strongest in standing (C−); momentum is the one to work on (F).