Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
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 14h.
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.9.186:28027.
Is 【双赢PVE】原倍/养老/突袭/死亡不掉 up, and how steady is its uptime?
The server is down: 【双赢PVE】原倍/养老/突袭/死亡不掉 is offline now, with the last sighting 44 days 12 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
What Rust version is 【双赢PVE】原倍/养老/突袭/死亡不掉 on?
Rust network protocol 2633 and build 163794 on Windows is what 【双赢PVE】原倍/养老/突袭/死亡不掉 runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does 【双赢PVE】原倍/养老/突袭/死亡不掉 wipe, and how often?
the force wipe gives the basis for estimating 【双赢PVE】原倍/养老/突袭/死亡不掉's next wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 55 days 11 hours have passed since this world was made. The tags show a monthly wipe schedule.
Population
Where does 【双赢PVE】原倍/养老/突袭/死亡不掉 sit among Rust servers?
In the top – of all ranked servers, 【双赢PVE】原倍/养老/突袭/死亡不掉 sits at #8,899 for player hours over the last seven days.
Is 【双赢PVE】原倍/养老/突袭/死亡不掉 a busy server?
The last sighting of 【双赢PVE】原倍/养老/突袭/死亡不掉 was 44 days 12 hours ago, and it is offline right now.
Lists and filters
What is meant by the tags on 【双赢PVE】原倍/养老/突袭/死亡不掉?
The game's browser takes its cue from the tags 【双赢PVE】原倍/养老/突袭/死亡不掉 has set: gmvanilla (Game mode): Survival, vanilla style; mp200 (Max players): Its slot count is 200; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): The game build is 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): Oxide (uMod) provides the plugin framework here. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show 【双赢PVE】原倍/养老/突袭/死亡不掉?
Rust Server Score lists that include 【双赢PVE】原倍/养老/突袭/死亡不掉: Best community servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: 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
How is 【双赢PVE】原倍/养老/突袭/死亡不掉 set up, and what rules does it keep?
The name of 【双赢PVE】原倍/养老/突袭/死亡不掉 gives no gather rate. With no change from the game default, groups take up to 8 players. pve is the mode here, no PvP between players. You will see it in the Community section of the server browser, since it is a community server. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on 【双赢PVE】原倍/养老/突袭/死亡不掉?
The game generates a procedural map for 【双赢PVE】原倍/养老/突袭/死亡不掉.
Connecting
How do you get onto 【双赢PVE】原倍/养老/突袭/死亡不掉?
Enter client.connect 202.189.9.186:28027 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2633,^m,^p,gmvanilla,cs163794,ts8,^o
Game
gmvanilla
Game modeSurvival, vanilla style.
mp200
Max playersIts slot count is 200.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildThe game build is 163794.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
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.
Not enough figures yet to write a report. Check back after a few days on the list.