Working its way up from the back of the class: #15,452 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 7,261 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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 67% 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 Monday 2 November, 01:10 UTC, in 3d 11h.
Biweekly: 14 days after its last 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
You won't find a region tag on 『影子』PVE|原倍|事件活动|萌新养老, but its name indicates Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 209.9.203.197:28015 is the address to use.
How reliable is 『影子』PVE|原倍|事件活动|萌新养老, and is it up?
You cannot join now: 『影子』PVE|原倍|事件活动|萌新养老 is offline, last seen 37 days 21 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 21 September 2026, Rust Server Score saw it for the first time.
On what Rust version does 『影子』PVE|原倍|事件活动|萌新养老 sit?
The server 『影子』PVE|原倍|事件活动|萌新养老 is on Rust network protocol 2633 and build 164530 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does 『影子』PVE|原倍|事件活动|萌新养老 wipe, and how often?
The estimate for 『影子』PVE|原倍|事件活动|萌新养老's next wipe comes from biweekly: 14 days after its last wipe. It is due to wipe next on Monday 2 November at 01:10 UTC. It has been running its current world for 38 days 12 hours. A fortnightly wipe schedule appears in its tags.
Player numbers
Where does 『影子』PVE|原倍|事件活动|萌新养老 sit among Rust servers?
In the top 67% of all ranked servers, 『影子』PVE|原倍|事件活动|萌新养老 sits at #15,452 for player hours over the last seven days.
What does the population on 『影子』PVE|原倍|事件活动|萌新养老 look like?
『影子』PVE|原倍|事件活动|萌新养老 is offline at the moment; the last time it was seen was 37 days 21 hours ago.
Tags and filters
What is meant by the tags on 『影子』PVE|原倍|事件活动|萌新养老?
You'll see 『影子』PVE|原倍|事件活动|萌新养老 tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): This runs on build 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^b (Biweekly): A wipe happens once a fortnight; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show 『影子』PVE|原倍|事件活动|萌新养老?
Rust Server Score lists that include 『影子』PVE|原倍|事件活动|萌新养老: Modded Rust servers, graded. You can find it under these server-list filters: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Server rules
Which rules does 『影子』PVE|原倍|事件活动|萌新养老 enforce, and what are its settings?
You will find no gather rate in the name of 『影子』PVE|原倍|事件活动|萌新养老. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is not enabled.
Can you tell me which map 『影子』PVE|原倍|事件活动|萌新养老 uses?
『影子』PVE|原倍|事件活动|萌新养老 runs a procedural map, which the game generates.
How to join
How should you connect to 『影子』PVE|原倍|事件活动|萌新养老?
To connect, start Rust, press F1, and type client.connect 209.9.203.197:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,^b,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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. Even marks across the subjects, from F to F.