Working its way up from the back of the class: #15,541 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
39/ 100
F
Slipped a little: down 3,554 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 70% of all ranked servers. Ranked on player hours over the last seven days.
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
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 8 Oct, 16:20 UTC20d ago
1
–
running
0
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 Solo PVE. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 107.136.237.168:28015 is the address to use.
How dependable is Solo PVE, and is it online at the moment?
You cannot join now: Solo PVE is offline, last seen 20 days 17 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 8 October 2026.
Which Rust version is Solo PVE running?
The server Solo PVE is on Rust network protocol 2634 and build 167231 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does Solo PVE wipe its map?
There are too few wipes on record for Solo PVE to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 20 days 17 hours have passed since this world was made.
What happens on Solo PVE when wipe day arrives?
Recent wipes have peaked at 1 players on average. 2 hours after the latest wipe began, the crowd hit its peak.
Population
Where does Solo PVE sit among Rust servers?
Over the last seven days, Solo PVE has #15,541 for player hours, in the top 70% of all ranked servers.
Is Solo PVE a busy server?
Solo PVE is offline at the moment; the last time it was seen was 20 days 17 hours ago.
Tags
What do Solo PVE's tags stand for?
You'll see Solo PVE tagged with gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167231 (Build): The game build is 167231; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^p (PvE): The danger comes from the world, not from other players; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon in the browser, which picks them up from the server. 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 Solo PVE appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Solo PVE among them: Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.
Server rules
How is Solo PVE set up, and what rules does it keep?
You will find no gather rate in the name of Solo PVE. The group limit stays at the game's default of 8 players. It runs pve, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Solo PVE uses?
The game generates a procedural map for Solo PVE.
Connecting
How should you connect to Solo PVE?
To connect, start Rust, press F1, and type client.connect 107.136.237.168:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,^z,^y,^p,gmrust,cs167231,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp2
Max playersThe server holds 2 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167231
BuildThe game build is 167231.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: 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.