Working its way up from the back of the class: #14,156 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
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
29/ 100
F
Lost ground: down 5,958 places this week. A strong wipe could turn it round.
A fair term, with more to come.
Strongest in wipe hold (A+); momentum is the one to work on (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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 10 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 65% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
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.
usual gap2 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Mon 12 OctSat 10 Oct
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
Mon 12 Oct, 22:48 UTC15d ago
1
–
running
1
Sat 10 Oct, 22:33 UTC17d ago
1
✓ held half
2 days
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
In what location does Hostile Sector Solo PVE sit?
You'll find no region listed by Hostile Sector Solo PVE. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 91.98.178.181:28080.
How reliable is Hostile Sector Solo PVE, and is it up?
You cannot join now: Hostile Sector Solo PVE is offline, last seen 15 days 12 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 10 October 2026.
On what Rust version does Hostile Sector Solo PVE sit?
You will find Hostile Sector Solo PVE on Rust network protocol 2634 and build 167398, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does Hostile Sector Solo PVE wipe, and how often?
Hostile Sector Solo 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. It has been running its current world for 15 days 13 hours.
What happens on Hostile Sector Solo PVE when wipe day arrives?
Recent wipes have peaked at 1 players on average. 0 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 100% of its recent wipes.
Player count
Where does Hostile Sector Solo PVE sit among Rust servers?
Over the last seven days, Hostile Sector Solo PVE has #14,156 for player hours, in the top 65% of all ranked servers.
What does the population on Hostile Sector Solo PVE look like?
Hostile Sector Solo PVE is offline at the moment; the last time it was seen was 15 days 12 hours ago.
Tags
What do Hostile Sector Solo PVE's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167398 (Build): Build number: 167398; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon are the tags Hostile Sector Solo PVE publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Hostile Sector Solo PVE appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Hostile Sector Solo PVE: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Rules and settings
What settings and rules apply on Hostile Sector Solo PVE?
The name of Hostile Sector Solo PVE gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Hostile Sector Solo PVE uses?
The game generates the procedural map on Hostile Sector Solo PVE at size 4,500 with seed 1870104028. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to Hostile Sector Solo PVE?
To connect, start Rust, press F1, and type client.connect 91.98.178.181:28080. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2634,gmrust,cs167398,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167398
BuildBuild number: 167398.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it 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 fair term, with more to come. Strongest in wipe hold (A+); momentum is the one to work on (F).