RUST METRICSFlight deck · live data
Data live Servers11,908 Players102,404 Populated3,970 Fresh wipes 3 h409 Scan5 min
‹ All servers157.85.88.114:22243
Online Full Queue Fresh wipe Wipe due No query

HAZMA

Online 157.85.88.114:22243 checked 13m ago

vanillamoddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 16:00 UTC
0 8 15 22 30 PAX 0 /30

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 226 SERVER FPS

Server fps

48 h low 190 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 65,018 ×1000

Entities

48 h range 64,762–67,469 · memory 3,288 MB
1239 ET SINCE RESTART 2D 05H

Uptime

2 days 5 hours since its last restart, at the last reading
7-day average0peak 1
Rank#13,015top 58%
Last wipe24d agono schedule published
Next wipe–too few wipes seen yet
Memory3,288MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75118:0003:0012:0022:0007:0016:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040018:0003:0012:0022:0007:0016: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep3 Oct10 Oct16 Oct29 Oct

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

PLAN

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 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 13:20 UTC24d ago 2 – 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on HAZMA when wipe day comes?

At their busiest, its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 1 hours.

How often does HAZMA wipe, and when?

To tell the rhythm of HAZMA, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 24 days 4 hours ago.

Tag meanings

Which tags does HAZMA carry, and what do they mean?

Tags published by HAZMA, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp30 (Max players): Slots: 30; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show HAZMA?

On Rust Metrics, HAZMA sits in these lists: Modded Rust servers, checked live 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.

Population

Where does HAZMA sit in the rankings?

Ranking for HAZMA: #13,015 on seven-day player hours, top 58% of all ranked servers.

How full does HAZMA get?

Current headcount on HAZMA: 0 players, 30 slots available. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 0 players, at 10:00 UTC over the last 48 hours.

Operator and location

Where does HAZMA sit?

No region comes from HAZMA. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 157.85.88.114:22243.

What Rust version is HAZMA on?

Reading: HAZMA, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.

How does HAZMA perform?

Reading: 221 server fps on average across the last 48 hours. It never dropped below 190. Peak entity count: 67,469. Buildings, deployables and all else included. Reading: 4,150 MB of memory at the highest. Expect lag when fps falls and entities climb.

How reliable is HAZMA, and is it online now?

HAZMA reports online. Status: normal. By its reported uptime, the last restart was roughly 2 days 5 hours ago. Uptime for the last 7 full days: 37 of 168 hours, or 22%. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

What settings and rules apply on HAZMA?

Check: gather rate. The name HAZMA does not state one. 8 players per group, the default value. pve, other players are not fought — that is the game mode. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. It describes itself as vanilla. The meaning given: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Anti-cheat reading: VAC on, Valve's system.

What map is HAZMA on?

Check: map. Procedural, size 3,500, seed 50000, generated by the game on HAZMA. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How can you get onto HAZMA?

Press F1 in Rust and enter client.connect 157.85.88.114:22243. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp30
Max players Slots: 30.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Difficulty

^v
Vanilla Unmodified from Facepunch's release: no altered rates, no kits, no extra rules.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

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.