Rust Data

rustdata.spaceservers157.85.88.114:22244.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.88.114:22243 checked 9m ago

HAZMA

vanillamoddedoxidepve

Connect

srv = rust.server("157.85.88.114:22244")
print(srv.connect_command)

Right now

srv.summary()
players now 0/30 # 0% full
7-day average 0 # peak 1
rank #13,567 # top 61%
last wipe 23d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75111:0020:0005:0014:0000:0009:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040011:0020:0005:0014:0000:0009:00

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 17 Sep. 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
15k10k15k20k20 Sep27 Sep3 Oct10 Oct16 Oct29 Oct

Top 61% 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.

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 5 Oct, 13:20 UTC23d ago 2 NaN 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.

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

Map

3500 · seed 50000
Map of HAZMA
map
Procedural Map
size
3500
seed
50000
Open on RustMaps

Server

srv.info()
address
157.85.88.114:22243
region
–
max players
30
group limit
8, the default
wipe schedule
–
last wipe
5 Oct 2026, 13:20 UTC
hostname
–
first seen
13 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 253 on average116/2000
1[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 242 on average165/2000
2Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 107 on average22/200
3【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 58 on average78/200
4[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendlgroups of 30+ · monthly · 54 on average7/300
5TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 50 on average48/100

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does HAZMA rank?

Player hours over seven days put HAZMA at #13,567, in the top 61% of the ranked set.

How full does HAZMA run?

HAZMA reports 0 players at this refresh, with 30 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 11:00 UTC, mean 1 players.

About the server

How well does HAZMA perform?

Averaged over 48 hours: 222 server fps, never under 193. Buildings, deployables and all else in the world took the count as high as 67,469 entities. The memory field tops out at 4,104 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does HAZMA run?

Rust network protocol 2635 and build 168909 on Linux is what HAZMA runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is HAZMA, and is it online now?

Online is the state at the latest refresh for HAZMA. Count back 46 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 37 of 168, 22%. Rust Data logged it first on 13 September 2026.

Where does HAZMA sit?

There is no region published for HAZMA. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 157.85.88.114:22243.

Rules, settings, map

Which rules apply on HAZMA, and what settings?

You will not find a gather rate in the string HAZMA. The group limit sits at the default of 8 players. Recorded as pve, no combat between players. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. The description says vanilla, which here means untouched settings: rates, kits and rules as shipped. VAC, Valve's anti-cheat, is enabled.

What is the map on HAZMA?

The game generates the map on HAZMA: procedural, size 3,500, seed 50000. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

On what schedule does HAZMA wipe?

A rhythm cannot be read from the wipes of HAZMA on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 23 days 21 hours ago.

What is wipe day on HAZMA like?

Across recent wipes the busiest point averaged 2 players. 1 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Which Rust Data filters and lists contain HAZMA?

The Rust Data lists that HAZMA fits are: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Type: Vanilla and Modded; Game mode: PvE; Server tag: Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on HAZMA?

Read by the game's server browser, the tags HAZMA publishes are: gmrust (Game mode): Rust survival in its standard form; mp30 (Max players): 30 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

How can I connect to HAZMA?

Enter client.connect 157.85.88.114:22243 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp30,ptrak,$r?,v2635,^v,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp30
Max players 30 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Difficulty

^v
Vanilla Untouched settings: rates, kits and rules as shipped.

Gameplay

^p
PvE No player-versus-player combat; the danger comes from the world.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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 59,874 players 11,727 servers online