Working its way up from the back of the class: #16,347 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
26/ 100
F
Lost ground: down 7,967 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 68% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WW··
·······
·······
·······
·······
··
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.
usual gap0.9 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Fri 25 SepThu 24 Sep
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
Fri 25 Sep, 20:37 UTC32d ago
1
–
running
1
Thu 24 Sep, 22:07 UTC33d ago
1
–
0.9 days
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
No region is published for HARDCORE PVP SOLO. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 201.32.206.136:28015.
How dependable is HARDCORE PVP SOLO, and is it online at the moment?
The server is down: HARDCORE PVP SOLO is offline now, with the last sighting 28 days 1 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 22 September 2026.
What Rust version is HARDCORE PVP SOLO on?
Rust network protocol 2633 and build 165217 on Windows is what HARDCORE PVP SOLO runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does HARDCORE PVP SOLO wipe its map?
The record holds too few of HARDCORE PVP SOLO's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 31 days 22 hours.
What happens on HARDCORE PVP SOLO when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 0 hours into the latest wipe.
Player count
Where does HARDCORE PVP SOLO sit among Rust servers?
In the top 68% of all ranked servers, HARDCORE PVP SOLO sits at #16,347 for player hours over the last seven days.
Is HARDCORE PVP SOLO a busy server?
HARDCORE PVP SOLO is offline at the moment; the last time it was seen was 28 days 1 hours ago.
Tags
How should you read the tags on HARDCORE PVP SOLO?
The game's browser takes its cue from the tags HARDCORE PVP SOLO has set: gmhardcore (Game mode): A harsher ruleset, hardcore; mp15 (Max players): Its slot count is 15; ts0 (Group limit): Teams are disabled; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here. 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.
Where does HARDCORE PVP SOLO appear in the Rust Server Score lists and filters?
These Rust Server Score lists count HARDCORE PVP SOLO among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: Hardcore.
Rules and settings
What settings and rules apply on HARDCORE PVP SOLO?
The name of HARDCORE PVP SOLO gives no gather rate. It publishes no limit on group size. hardcore is the mode here, Facepunch's most punishing mode. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. You are not covered by VAC, Valve's anti-cheat.
HARDCORE PVP SOLO runs which map?
A procedural map, generated by the game, is what HARDCORE PVP SOLO runs.
Connecting
What is the way to join HARDCORE PVP SOLO?
Enter client.connect 201.32.206.136: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 asmp15,ptrak,$r?,v2633,gmhardcore,cs165217,ts0
Game
gmhardcore
Game modeA harsher ruleset, hardcore.
mp15
Max playersIts slot count is 15.
ts0
Group limitTeams are disabled.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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.