Not ranked yet, so there is no place in the school to report.
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
41/ 100
F
Slipped a little: down 2,361 places this week. Nothing a good wipe can't fix.
A term to build on.
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.
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
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 Sunday 1 November, 03:17 UTC, in 2d 4h.
Its biweekly schedule tag · low confidence
wipe-day peak1players, last three wipes
Coming wipes
2d 4hSun 1 Nov, 03:17 UTC
6d 20hThu 5 Nov, 19:00 UTCFW
16d 4hSun 15 Nov, 03:17 UTC
30d 4hSun 29 Nov, 03:17 UTC
34d 20hThu 3 Dec, 19:00 UTCFW
44d 4hSun 13 Dec, 03:17 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 20 Sep, 03:17 UTC39d ago
1
–
running
1
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. Rust Server Score takes the server's word for its location and does not trace the hardware. 123.185.209.177:28015 is the address to use.
Is 单人PVE up, and how steady is its uptime?
You cannot join now: 单人PVE is offline, last seen 39 days 17 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 18 September 2026.
On what Rust version does 单人PVE sit?
Rust network protocol 2633 and build 163794 on Windows is what 单人PVE runs. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does 单人PVE reset?
Its tag sets the prediction, as the record holds too few of 单人PVE's wipes to confirm its schedule. Expect the next wipe on Sunday 1 November at 03:17 UTC. It has been running its current world for 39 days 19 hours. Its tags give a wipe schedule of every two weeks.
What happens on 单人PVE when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does 单人PVE place in the wider field of Rust servers?
In the top – of all ranked servers, 单人PVE sits at #13,815 for player hours over the last seven days.
How many players does 单人PVE usually have?
单人PVE is offline at the moment; the last time it was seen was 39 days 17 hours ago.
Tags
How should you read the tags on 单人PVE?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): Its slot count is 10; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163794 (Build): Build number: 163794; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^b (Biweekly): A wipe happens once a fortnight; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags 单人PVE publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature 单人PVE?
These Rust Server Score lists count 单人PVE among them: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: 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
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 pve, 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.
Can you tell me which map 单人PVE uses?
单人PVE runs a procedural map, which the game generates.
Getting in
How do you get onto 单人PVE?
Enter client.connect 123.185.209.177: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 asmp10,ptrak,$r?,v2633,^b,^p,gmrust,cs163794,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersIts slot count is 10.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
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.