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.
AveragePeakWipe
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
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h.
The force wipe · high confidence
wipe-day peak3players, last three wipes
Coming wipes
7d 4hThu 5 Nov, 19:00 UTCFW
35d 4hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 7 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 14 Sep, 07:20 UTC45d ago
3
–
running
1
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 takes the server's word for its location and does not trace the hardware. 202.189.9.186:28024 is the address to use.
How reliable is 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉, and is it up?
At this moment, 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 is offline; the last time it was seen was 43 days 9 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 14 September 2026, Rust Server Score saw it for the first time.
Which Rust version is 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 running?
The server 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 is on Rust network protocol 2633 and build 163493 under Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
When does 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 wipe, and how often?
【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 wipes with the force wipe and at no other time. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 45 days 6 hours have passed since this world was made. The tags show a monthly wipe schedule.
What should you expect from wipe day on 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉?
Across its recent wipes, the busiest moments averaged 3 players. 7 hours after the latest wipe began, the crowd hit its peak.
Player numbers
What position does 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 hold in the rankings?
Over the last seven days, 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 has #15,479 for player hours, in the top – of all ranked servers.
Is 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 a busy server?
It has been 43 days 9 hours since 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 was last seen, and it is offline right now.
Tags
What is meant by the tags on 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉?
gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): Its slot count is 100; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs163493 (Build): Build number: 163493; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^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): Oxide (uMod) provides the plugin framework here are the tags 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 publishes, and the game's server browser reads them. 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 Rust Server Score filters and lists feature 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉?
These Rust Server Score lists count 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 among them: 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.
Server rules
How is 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 set up, and what rules does it keep?
Nothing in the name of 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 states a 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. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 uses?
A procedural map, generated by the game, is what 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉 runs.
How to join
How should you connect to 【晴天PVE】原倍|萌新|养老|突袭|死亡不掉?
To connect, start Rust, press F1, and type client.connect 202.189.9.186:28024. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,^m,^p,gmvanilla,cs163493,ts8,^o
Game
gmvanilla
Game modeThis is vanilla survival.
mp100
Max playersIts slot count is 100.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163493
BuildBuild number: 163493.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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
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.