Working its way up from the back of the class: #15,506 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
51/ 100
D
Moving up: up 344 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.
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
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 Thursday 5 November, 19:00 UTC, in 7d 1h.
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
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. Find it at 202.189.23.187:28015.
How dependable is 『微光』PVE|原倍|事件活动|萌新养老, and is it online at the moment?
You cannot join now: 『微光』PVE|原倍|事件活动|萌新养老 is offline, last seen 42 days 21 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 16 September 2026, Rust Server Score saw it for the first time.
Which Rust version is 『微光』PVE|原倍|事件活动|萌新养老 running?
You will find 『微光』PVE|原倍|事件活动|萌新养老 on Rust network protocol 2633 and build 162929, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does 『微光』PVE|原倍|事件活动|萌新养老 wipe its map?
the force wipe gives the basis for estimating 『微光』PVE|原倍|事件活动|萌新养老's next 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. The world it runs now was created 55 days 22 hours. Its tags list a monthly wipe schedule.
Player numbers
Where does 『微光』PVE|原倍|事件活动|萌新养老 sit among Rust servers?
Over the last seven days, 『微光』PVE|原倍|事件活动|萌新养老 has #15,506 for player hours, in the top 67% of all ranked servers.
What does the population on 『微光』PVE|原倍|事件活动|萌新养老 look like?
『微光』PVE|原倍|事件活动|萌新养老 is offline at the moment; the last time it was seen was 42 days 21 hours ago.
Tags and filters
What is meant by the tags on 『微光』PVE|原倍|事件活动|萌新养老?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs162929 (Build): This runs on build 162929; 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; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded 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.
Where does 『微光』PVE|原倍|事件活动|萌新养老 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include 『微光』PVE|原倍|事件活动|萌新养老: Modded Rust servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
How is 『微光』PVE|原倍|事件活动|萌新养老 set up, and what rules does it keep?
The name of 『微光』PVE|原倍|事件活动|萌新养老 gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
『微光』PVE|原倍|事件活动|萌新养老 runs which map?
The game generates a procedural map for 『微光』PVE|原倍|事件活动|萌新养老.
Getting in
How should you connect to 『微光』PVE|原倍|事件活动|萌新养老?
To connect, start Rust, press F1, and type client.connect 202.189.23.187: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,^m,gmrust,cs162929,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs162929
BuildThis runs on build 162929.
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.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under 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. Strongest in momentum (D); standing is the one to work on (F).