A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
66/ 100
C+
Working its way up from the back of the class: #7,492 on player hours.
Uptimehours on the list, last 48
56/ 100
C−
Attendance needs work: on the list only 27 of the last 48 hours.
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.
A term to build on.
Strongest in standing (C+); population 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
Every five minutes, from the Steam server list.
AveragePeakWipe
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 34% of all ranked servers. Ranked on player hours over the last seven days.
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
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 8d 11h.
The force wipe · high confidence
Coming wipes
8d 11hThu 5 Nov, 19:00 UTCFW
13d 15hTue 10 Nov, 22:43 UTC
27d 15hTue 24 Nov, 22:43 UTC
36d 11hThu 3 Dec, 19:00 UTCFW
41d 15hTue 8 Dec, 22:43 UTC
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 22:43 UTC8h ago
–
–
running
0
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
The name of 『微光』PVE|原倍|事件活动|萌新养老 points to Asia, though no region tag is set. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 27.45.44.6:28015.
How reliable is 『微光』PVE|原倍|事件活动|萌新养老, and is it up?
You can join now: 『微光』PVE|原倍|事件活动|萌新养老 is online. The first sighting by Rust Server Score was on 27 October 2026.
On what Rust version does 『微光』PVE|原倍|事件活动|萌新养老 sit?
Rust network protocol 2635 and build 168909 on Windows is what 『微光』PVE|原倍|事件活动|萌新养老 runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does 『微光』PVE|原倍|事件活动|萌新养老 wipe its map?
Its tag sets the prediction, as the record holds too few of 『微光』PVE|原倍|事件活动|萌新养老's wipes to confirm its schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 8 hours have passed since this world was made. A fortnightly wipe schedule appears in its tags.
Player count
What position does 『微光』PVE|原倍|事件活动|萌新养老 hold in the rankings?
Over the last seven days, 『微光』PVE|原倍|事件活动|萌新养老 has #7,492 for player hours, in the top 34% of all ranked servers.
How many players does 『微光』PVE|原倍|事件活动|萌新养老 usually have?
With 100 slots available, 『微光』PVE|原倍|事件活动|萌新养老 currently has 0 players. Averaging 0 players over seven days, it peaked at 1. Over the last 48 hours, the peak hour was 06:00 UTC, averaging 1 players.
Tags and filters
What is meant by the tags on 『微光』PVE|原倍|事件活动|萌新养老?
The game's browser takes its cue from the tags 『微光』PVE|原倍|事件活动|萌新养老 has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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|原倍|事件活动|萌新养老?
These Rust Server Score lists count 『微光』PVE|原倍|事件活动|萌新养老 among them: Modded Rust servers, graded. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.
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. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. 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.
Which map is in play on 『微光』PVE|原倍|事件活动|萌新养老?
The game generates a procedural map for 『微光』PVE|原倍|事件活动|萌新养老.
Connecting
How do you get onto 『微光』PVE|原倍|事件活动|萌新养老?
Enter client.connect 27.45.44.6: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 asmp100,ptrak,$r?,v2635,^b,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits 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 standing (C+); population is the one to work on (F).