Working its way up from the back of the class: #13,756 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
32/ 100
F
Lost ground: down 5,064 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.
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 62% 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 Friday 30 October, 12:48 UTC, in 17h.
Biweekly: 14 days after its last 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
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 123.185.208.144:28015.
Is 单人PVE up, and how steady is its uptime?
The server is down: 单人PVE is offline now, with the last sighting 22 days 14 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 2 October 2026.
On what Rust version does 单人PVE sit?
You will find 单人PVE on Rust network protocol 2634 and build 166586, 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?
biweekly: 14 days after its last wipe gives the basis for estimating 单人PVE's next wipe. Friday 30 October at 12:48 UTC is the date set for its next wipe. The world it runs now was created 27 days 6 hours. Its tags give a wipe schedule of every two weeks.
Player numbers
Where does 单人PVE sit among Rust servers?
In the top 62% of all ranked servers, 单人PVE sits at #13,756 for player hours over the last seven days.
What does the population on 单人PVE look like?
It has been 22 days 14 hours since 单人PVE was last seen, and it is offline right now.
Lists and filters
How should you read 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; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166586 (Build): The game build is 166586; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^b (Biweekly): The server wipes on a two-week cycle; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does 单人PVE appear in the Rust Server Score lists and filters?
These Rust Server Score lists count 单人PVE among them: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Map and rules
How is 单人PVE set up, and what rules does it keep?
Nothing in the name of 单人PVE states a gather rate. The group limit stays at the game's default of 8 players. You get pve here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. VAC, Valve's anti-cheat, is not enabled.
单人PVE runs which map?
单人PVE runs a procedural map, which the game generates.
Getting in
How do you get onto 单人PVE?
To connect, start Rust, press F1, and type client.connect 123.185.208.144:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,^b,^p,gmrust,cs166586,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166586
BuildThe game build is 166586.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^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. Even marks across the subjects, from F to F.