On the class lists: D (50), with population over 48 hours and no performance mark.
Players now0/ 2000% full
7-day average0peak 2
Rank#9,612top 43%
Last wipe2d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 200 on average. Plenty of space to grow.
Standingrank on player hours
57/ 100
C−
Working its way up from the back of the class: #9,612 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 66 server fps on average.
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 fair term, with more to come.
Strongest in performance (A+); 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 43% 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
Where in the world is 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉?
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. Find it at 202.189.5.26:28085.
Is 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 up, and how steady is its uptime?
The server is up: 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 is online now. The uptime it reports puts the last restart at about 2 days 7 hours ago. It was up 98% of the time over the last 2 full days, 47 of 48 hours. The first sighting by Rust Server Score was on 26 October 2026.
Does 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 perform well?
It never fell below 45 server fps in the last 48 hours, averaging 66. At its peak, it held 124,717 entities, including buildings, deployables and all else in the world. Memory use reached up to 4,038 MB. Players feel lag when fps drops and entities pile up.
Which Rust version is 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 running?
You will find 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 on Rust network protocol 2635 and build 168909, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 wipe its map?
The record holds too few of 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 2 days 11 hours.
Population
What position does 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 hold in the rankings?
Over the last seven days, 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 has #9,612 for player hours, in the top 43% of all ranked servers.
Is 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 a busy server?
Right now, 0 players are on 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉, which has 200 slots. Averaging 0 players over seven days, it peaked at 2. The highest average in the last 48 hours came at 17:00 UTC, with 0 players.
Tags and filters
What is meant by the tags on 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp200 (Max players): Its slot count is 200; 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): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^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. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
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: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Rules and settings
Which rules does 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 enforce, and what are its settings?
Nothing in the name of 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 runs which map?
The game generates the procedural map on 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉 at size 4,500 with seed 1082509869. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to 【萤火】PVE/萌新/纯净/养老/种植/突袭/死亡不掉?
To connect, start Rust, press F1, and type client.connect 202.189.5.26:28085. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp200
Max playersIts slot count is 200.
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
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).