Working its way up from the back of the class: #11,957 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
10/ 100
F
Lost ground: down 9,586 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (D); momentum 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.
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 5 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 54% of all ranked servers, top 86% in EA. 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 15h.
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
Which region is 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 based in?
The EA tag on 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 puts it in Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 125.38.167.145:21015 is the address to use.
How reliable is 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶, and is it up?
The server is down: 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 is offline now, with the last sighting 17 days 4 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 4 October 2026, Rust Server Score saw it for the first time.
On what Rust version does 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 sit?
You will find 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 on Rust network protocol 2634 and build 166652, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 wipe its map?
The next wipe on 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 is a projection from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 27 days 9 hours. Its tags list a monthly wipe schedule.
Player count
Where does 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 place in the wider field of Rust servers?
Over the last seven days, 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 has #11,957 for player hours, in the top 54% of all ranked servers and #471 in Asia.
What does the population on 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 look like?
『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 is offline at the moment; the last time it was seen was 17 days 4 hours ago.
Tags
What do 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶's tags stand for?
You'll see 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 tagged with gmrust (Game mode): Survival in the standard Rust style; mp200 (Max players): 200 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): Oxide (uMod) provides the plugin framework here; EA (East Asia): The server browser lists it under East Asia in the browser, which picks them up from the server. 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.
Who is behind 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶?
A nmpve.top hostname is published by 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 and by 20 other tracked servers, which suggests one operator.
Where does 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶: Best community servers, graded and Rust PvE servers, graded. It shows under the following filters 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.
Rules and settings
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. pve is the mode here, no PvP between players. The server browser lists it under Community, as a community server. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 runs which map?
『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶 runs a game-generated procedural map at size 4,500, seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. The name of the map reads: Custom Map.
How to join
What is the way to join 『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶?
To connect, start Rust, press F1, and type client.connect 125.38.167.145:21015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://qm.qq.com/cgi-bin/qm/qr?k=Gj39lX2pQvKA2N-WKsDMRIHQMFws9F4g&authKey=wqNMdLBO6wyIuG50%2Fi7OU2hA%2BzAwXG96wsPKo8M2LnQUoLbHG5c%2FVyow6VJLE%2FEU&noverify=0&group_code=500022602.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,^m,EA,^p,gmrust,cs166652,ts8,^o
Game
gmrust
Game modeSurvival in the standard Rust style.
mp200
Max players200 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
Region
EA
East AsiaThe server browser lists it under East Asia.
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 (D); momentum is the one to work on (F).