Working its way up from the back of the class: #13,321 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
19/ 100
F
Lost ground: down 8,392 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); 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.
No daily history yet.
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 61% 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 21h.
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
No region tag appears for 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉, but the name suggests Asia. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 202.189.4.147:28215.
Is 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 up, and how steady is its uptime?
At this moment, 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 is offline; the last time it was seen was 16 days 3 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 12 October 2026, Rust Server Score saw it for the first time.
Which Rust version is 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 running?
The server 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 is on Rust network protocol 2634 and build 166494 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 wipe, and how often?
The estimate for 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉's next wipe comes from the force 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. 27 days 2 hours have passed since this world was made. Its tags list a monthly wipe schedule.
Player numbers
What position does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 hold in the rankings?
Over the last seven days, 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 has #13,321 for player hours, in the top 61% of all ranked servers.
Is 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 a busy server?
It has been 16 days 3 hours since 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 was last seen, and it is offline right now.
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): This is vanilla survival; mp200 (Max players): The server holds 200 slots; 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): This runs on build 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $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): This is player against world: players do not fight each other; ^o (Oxide): Oxide (uMod) provides the plugin framework here. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
These Rust Server Score lists count 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 among them: 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.
Server rules
Which rules does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 enforce, and what are its settings?
The name of 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 gives no gather rate. The default of 8 players applies as the group cap. You get pve here, no PvP between players. The server browser lists it under Community, as a community server. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 runs which map?
【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 runs a procedural map, which the game generates.
Connecting
How should you connect to 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
To connect, start Rust, press F1, and type client.connect 202.189.4.147: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 playersThe server holds 200 slots.
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
BuildThis runs on build 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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
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.
A term to build on. Strongest in standing (F); momentum is the one to work on (F).