Working its way up from the back of the class: #13,215 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
43/ 100
F
Slipped a little: down 1,881 places this week. Nothing a good wipe can't fix.
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 57% 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 tag appears for 我的本地 Rust｜单人 PvE, but the name suggests Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 43.198.224.177:28015.
How reliable is 我的本地 Rust｜单人 PvE, and is it up?
You cannot join now: 我的本地 Rust｜单人 PvE is offline, last seen 37 days 7 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 22 September 2026.
What Rust version is 我的本地 Rust｜单人 PvE on?
You will find 我的本地 Rust｜单人 PvE on Rust network protocol 2633 and build 165217, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does 我的本地 Rust｜单人 PvE wipe, and how often?
The record holds too few of 我的本地 Rust｜单人 PvE's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 39 days 4 hours have passed since this world was made.
Population
What position does 我的本地 Rust｜单人 PvE hold in the rankings?
Over the last seven days, 我的本地 Rust｜单人 PvE has #13,215 for player hours, in the top 57% of all ranked servers.
Is 我的本地 Rust｜单人 PvE a busy server?
It has been 37 days 7 hours since 我的本地 Rust｜单人 PvE was last seen, and it is offline right now.
Lists and filters
What do 我的本地 Rust｜单人 PvE's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): 1 slots are available; 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; cs165217 (Build): This runs on build 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^p (PvE): Players do not fight one another here; the world is the danger; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags 我的本地 Rust｜单人 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.
Where does 我的本地 Rust｜单人 PvE appear in the Rust Server Score lists and filters?
These Rust Server Score lists count 我的本地 Rust｜单人 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: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.
Server rules
How is 我的本地 Rust｜单人 PvE set up, and what rules does it keep?
You will find no gather rate in the name of 我的本地 Rust｜单人 PvE. With no change from the game default, groups take up to 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. The plugin count runs to Carbon. You are covered by VAC, Valve's anti-cheat.
我的本地 Rust｜单人 PvE runs which map?
我的本地 Rust｜单人 PvE runs a procedural map, which the game generates.
How to join
How do you get onto 我的本地 Rust｜单人 PvE?
Enter client.connect 43.198.224.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 asmp1,ptrak,$r?,v2633,^z,^y,^p,gmrust,cs165217,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max players1 slots are available.
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.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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.