Working its way up from the back of the class: #14,176 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
29/ 100
F
Lost ground: down 5,828 places this week. A strong wipe could turn it round.
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.
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 64% 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
No region is published for Nangyun's PVE Rust. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 223.143.242.115:28015.
Is Nangyun's PVE Rust up, and how steady is its uptime?
The server is down: Nangyun's PVE Rust is offline now, with the last sighting 20 days 20 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 8 October 2026, Rust Server Score saw it for the first time.
Which Rust version is Nangyun's PVE Rust running?
The server Nangyun's PVE Rust is on Rust network protocol 2634 and build 167231 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does Nangyun's PVE Rust wipe its map?
There are too few wipes on record for Nangyun's PVE Rust to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 22 days 22 hours have passed since this world was made.
Player count
Where does Nangyun's PVE Rust place in the wider field of Rust servers?
Over the last seven days, Nangyun's PVE Rust has #14,176 for player hours, in the top 64% of all ranked servers.
Is Nangyun's PVE Rust a busy server?
Nangyun's PVE Rust is offline at the moment; the last time it was seen was 20 days 20 hours ago.
Lists and filters
What is meant by the tags on Nangyun's PVE Rust?
gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): 2 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167231 (Build): This runs on build 167231; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^p (PvE): This is player against world: players do not fight each other are the tags Nangyun's PVE Rust 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 Nangyun's PVE Rust appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Nangyun's PVE Rust among them: Best community servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Rules and settings
Which rules does Nangyun's PVE Rust enforce, and what are its settings?
The name of Nangyun's PVE Rust gives no gather rate. The group limit stays at the game's default of 8 players. pve is the mode here, no PvP between players. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Nangyun's PVE Rust?
Nangyun's PVE Rust runs a procedural map, which the game generates.
How to join
What is the way to join Nangyun's PVE Rust?
Enter client.connect 223.143.242.115: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 asmp2,ptrak,$r?,v2634,^p,gmrust,cs167231,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp2
Max players2 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167231
BuildThis runs on build 167231.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
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.