Working its way up from the back of the class: #15,477 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
38/ 100
F
Slipped a little: down 3,784 places this week. Nothing a good wipe can't fix.
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.
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
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 6d 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. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 119.183.132.140:28015.
Is 『微光』PVE|原倍|事件活动|萌新养老 up, and how steady is its uptime?
At this moment, 『微光』PVE|原倍|事件活动|萌新养老 is offline; the last time it was seen was 36 days 4 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 15 September 2026.
Which Rust version is 『微光』PVE|原倍|事件活动|萌新养老 running?
You will find 『微光』PVE|原倍|事件活动|萌新养老 on Rust network protocol 2633 and build 163207, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does 『微光』PVE|原倍|事件活动|萌新养老 wipe, and how often?
The estimate for 『微光』PVE|原倍|事件活动|萌新养老's next wipe comes from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 44 days 11 hours. Its tags list a monthly wipe schedule.
Player count
Where does 『微光』PVE|原倍|事件活动|萌新养老 sit among Rust servers?
Over the last seven days, 『微光』PVE|原倍|事件活动|萌新养老 has #15,477 for player hours, in the top 71% of all ranked servers.
Is 『微光』PVE|原倍|事件活动|萌新养老 a busy server?
『微光』PVE|原倍|事件活动|萌新养老 is offline at the moment; the last time it was seen was 36 days 4 hours ago.
Lists and filters
How should you read the tags on 『微光』PVE|原倍|事件活动|萌新养老?
gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163207 (Build): This runs on build 163207; 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; ^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 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|原倍|事件活动|萌新养老: 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.
Server rules
Which rules does 『微光』PVE|原倍|事件活动|萌新养老 enforce, and what are its settings?
Nothing in the name of 『微光』PVE|原倍|事件活动|萌新养老 states a gather rate. The group limit stays at the game's default of 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. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on 『微光』PVE|原倍|事件活动|萌新养老?
A procedural map, generated by the game, is what 『微光』PVE|原倍|事件活动|萌新养老 runs.
Connecting
What is the way to join 『微光』PVE|原倍|事件活动|萌新养老?
To connect, start Rust, press F1, and type client.connect 119.183.132.140: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,cs163207,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max players100 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163207
BuildThis runs on build 163207.
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.
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.