Rust Data

rustdata.spaceservers91.98.178.181:28015.ipynb

Run all rust-data · live

‹ All servers

Offline 91.98.178.181:28080 checked 15d ago

Hostile Sector Solo PVE

moddedcarbon

Connect

srv = rust.server("91.98.178.181:28015")
print(srv.connect_command)

Right now

srv.summary()
players now 0/1 # 0% full
7-day average 0 # peak –
rank #14,156 # top 65%
last wipe 15d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k10 Oct12 Oct14 Oct15 Oct17 Oct19 Oct

Top 65% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 12 Oct, 22:48 UTC15d ago 1 NaN running 1
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.

display(srv.map, srv.info())

Map

4500 · seed 1870104028
Map of Hostile Sector Solo PVE
map
Procedural Map
size
4500
seed
1870104028
Open on RustMaps

Server

srv.info()
address
91.98.178.181:28080
region
–
max players
1
group limit
8, the default
wipe schedule
–
last wipe
12 Oct 2026, 22:48 UTC
hostname
–
first seen
10 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 162 on average35/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average128/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average50/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 87 on average39/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average7/200
5CSL Scenery Budget Testgroups of 8+ · 85 on average0/500

Quick answers

From the figures on this page.

Population data

What position does Hostile Sector Solo PVE take in the server rankings?

Player hours over seven days put Hostile Sector Solo PVE at #14,156, in the top 65% of the ranked set.

How many players does Hostile Sector Solo PVE hold at once?

Hostile Sector Solo PVE returns no live count at this refresh, having last been seen 15 days 2 hours ago.

Server facts

What Rust version does Hostile Sector Solo PVE run?

The build is Rust network protocol 2634 and build 167398 on Windows, run by Hostile Sector Solo PVE. The protocol has to match before you can join, and Steam does the updating.

Is Hostile Sector Solo PVE up, and what does its uptime show?

Hostile Sector Solo PVE is offline at this refresh; the last response came 15 days 2 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 10 October 2026.

Where does Hostile Sector Solo PVE sit?

No region is published by Hostile Sector Solo PVE. Rust Data does not look up where the machine stands; it shows where a server says it is. 91.98.178.181:28080 is its address.

Rules, settings, map

Which rules apply on Hostile Sector Solo PVE, and what settings?

You will not find a gather rate in the string Hostile Sector Solo PVE. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.

Which map has Hostile Sector Solo PVE loaded?

Size 4,500, seed 1870104028: the procedural map on Hostile Sector Solo PVE, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

When does Hostile Sector Solo PVE wipe, and how often?

Too few wipes are on record for Hostile Sector Solo PVE to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 15 days 2 hours ago.

What is wipe day on Hostile Sector Solo PVE like?

Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.

Tags and filters

Which lists on Rust Data hold Hostile Sector Solo PVE, and which filters?

These Rust Data lists include Hostile Sector Solo PVE: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Which meanings do the tags on Hostile Sector Solo PVE hold?

Read by the game's server browser, the tags Hostile Sector Solo PVE publishes are: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into Hostile Sector Solo PVE?

In Rust, F1 opens the console: type client.connect 91.98.178.181:28080. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp1,ptrak,$r?,v2634,gmrust,cs167398,ts8,^z,^y

Game

gmrust
Game mode Rust survival in its standard form.
mp1
Max players The server lists 1 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167398
Build Recorded game build: 167398.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^z
Modded The Modded section lists it, because plugins or settings change the game.
^y
Carbon The 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.

Rust Data 48,284 players 11,675 servers online