Working its way up from the back of the class: #13,034 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,742 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 59% 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
Personal Rust PvE leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 186.247.38.91:28015 is the address to use.
Is Personal Rust PvE up, and how steady is its uptime?
At this moment, Personal Rust PvE is offline; the last time it was seen was 10 days 11 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 19 October 2026, Rust Server Score saw it for the first time.
What Rust version is Personal Rust PvE on?
You will find Personal Rust PvE on Rust network protocol 2634 and build 167781, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Personal Rust PvE wipe, and how often?
Personal Rust PvE has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 10 days 12 hours have passed since this world was made.
Population
Where does Personal Rust PvE sit among Rust servers?
Over the last seven days, Personal Rust PvE has #13,034 for player hours, in the top 59% of all ranked servers.
How many players does Personal Rust PvE usually have?
The last sighting of Personal Rust PvE was 10 days 11 hours ago, and it is offline right now.
Lists and filters
How should you read the tags on Personal Rust PvE?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): The server holds 10 slots; 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; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^p (PvE): Players do not fight one another here; the world is the danger are the tags Personal Rust PvE 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.
Which Rust Server Score filters and lists feature Personal Rust PvE?
Rust Server Score lists that include Personal Rust PvE: Best community servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules and settings
Which rules does Personal Rust PvE enforce, and what are its settings?
Nothing in the name of Personal Rust PvE states a gather rate. The default of 8 players applies as the group cap. 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.
Personal Rust PvE runs which map?
A procedural map, generated by the game, is what Personal Rust PvE runs.
Getting in
How should you connect to Personal Rust PvE?
To connect, start Rust, press F1, and type client.connect 186.247.38.91: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,^p,gmrust,cs167781,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersThe server holds 10 slots.
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.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
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.