Working its way up from the back of the class: #15,479 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
52/ 100
D
Moving up: up 474 places this week.
A term to build on.
Strongest in momentum (D); standing 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 71% 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 10h.
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 reports the location a server gives; it does not check where the machine actually is. 202.189.5.134:28025 is the address to use.
How dependable is 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉, and is it online at the moment?
At this moment, 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 is offline; the last time it was seen was 16 days 12 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 12 October 2026, Rust Server Score saw it for the first time.
On what Rust version does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 sit?
You will find 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 on Rust network protocol 2634 and build 166494, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
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. It has been running its current world for 27 days 14 hours. Its tags record that it wipes monthly.
Player count
Where does 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 sit among Rust servers?
In the top 71% of all ranked servers, 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 sits at #15,479 for player hours over the last seven days.
Is 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 a busy server?
It has been 16 days 12 hours since 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 was last seen, and it is offline right now.
Tags and filters
How should you read the tags on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
gmvanilla (Game mode): You play vanilla survival here; mp200 (Max players): The server holds 200 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; 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): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Plugin framework: Oxide (uMod) are the tags 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 publishes, and the game's server browser reads them. 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 Rust Server Score filters and lists feature 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
Rust Server Score lists that include 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉: Best community servers, graded and Rust PvE servers, graded. These filters bring it up 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.
Map and rules
What settings and rules apply on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
You will find no gather rate in the name of 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉. The default of 8 players applies as the group cap. 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. The server runs Valve's anti-cheat, VAC.
Which map is in play on 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
A procedural map, generated by the game, is what 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉 runs.
How to join
How do you get onto 【双赢PVE】原倍/事件/萌新/突袭/死亡不掉?
Enter client.connect 202.189.5.134:28025 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?,v2634,^m,^p,gmvanilla,cs166494,ts8,^o
Game
gmvanilla
Game modeYou play vanilla survival here.
mp200
Max playersThe server holds 200 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
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 codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxidePlugin framework: 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 momentum (D); standing is the one to work on (F).