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 19h.
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. You can connect at 110.42.36.220:28015.
How dependable is 【双赢PVE】原倍/养老/突袭/死亡不掉, and is it online at the moment?
The server is down: 【双赢PVE】原倍/养老/突袭/死亡不掉 is offline now, with the last sighting 44 days 19 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 13 September 2026.
On what Rust version does 【双赢PVE】原倍/养老/突袭/死亡不掉 sit?
The server 【双赢PVE】原倍/养老/突袭/死亡不掉 is on Rust network protocol 2633 and build 162929 under Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does 【双赢PVE】原倍/养老/突袭/死亡不掉 reset?
the force wipe gives the basis for estimating 【双赢PVE】原倍/养老/突袭/死亡不掉's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 55 days 5 hours have passed since this world was made. Its tags list a monthly wipe schedule.
Player count
Where does 【双赢PVE】原倍/养老/突袭/死亡不掉 sit among Rust servers?
In the top – of all ranked servers, 【双赢PVE】原倍/养老/突袭/死亡不掉 sits at #9,016 for player hours over the last seven days.
How many players does 【双赢PVE】原倍/养老/突袭/死亡不掉 usually have?
The last sighting of 【双赢PVE】原倍/养老/突袭/死亡不掉 was 44 days 19 hours ago, and it is offline right now.
Tags and filters
What do 【双赢PVE】原倍/养老/突袭/死亡不掉's tags stand for?
You'll see 【双赢PVE】原倍/养老/突袭/死亡不掉 tagged with gmvanilla (Game mode): This is vanilla survival; mp200 (Max players): 200 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs162929 (Build): Build number: 162929; 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): This is player against world: players do not fight each other; ^o (Oxide): The plugin framework in use is Oxide (uMod) in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the 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. 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.
Rules and settings
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. 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. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
【双赢PVE】原倍/养老/突袭/死亡不掉 runs which map?
The game generates a procedural map for 【双赢PVE】原倍/养老/突袭/死亡不掉.
Connecting
How should you connect to 【双赢PVE】原倍/养老/突袭/死亡不掉?
Enter client.connect 110.42.36.220:28015 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,cs162929,ts8,^o
Game
gmvanilla
Game modeThis is vanilla survival.
mp200
Max players200 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs162929
BuildBuild number: 162929.
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
PvEThis is player against world: players do not fight each other.
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.
Not enough figures yet to write a report. Check back after a few days on the list.