Rust Server TrendsSeismic network · station log
Recording Stations11,654 Players43,996 Active2,908 Wipes · 3 h99 48 h

Station XX-13005 · recording

HAZMA

Online 157.85.88.114:22243 checked 7m ago

vanillamoddedoxidepve
Connect
Players now
0/ 30
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#13,005
top 58%
Last wipe
24d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-13005 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 30 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+0into Thu 10:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75104:0013:0023:0008:0017:0002:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040004:0013:0023:0008:0017:0002: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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep4 Oct10 Oct17 Oct30 Oct

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

Expected events

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 peak
2players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 5 Oct, 13:20 UTC24d ago M0.3rising 2 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo NA · no group limit · biweekly · 245 on average
264/ 2000
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo EU · no group limit · biweekly · 242 on average
71/ 2000
Chrayntopia ♡ ︎PvE | RP | PvP NA · groups of 8+ · biweekly · 102 on average
92/ 200
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 59 on average
36/ 200
[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl groups of 30+ · monthly · 53 on average
47/ 300
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 EU · groups of 30+ · biweekly · 50 on average
8/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on HAZMA?

The procedural map on HAZMA is size 3,500 with seed 50000, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on HAZMA?

You will find no gather rate in the name of HAZMA. The group limit is 8 players, the game's default. It plays in pve mode, no combat against other players. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. Vanilla is the label it uses for itself: no changed rates, kits or rules: this is the game as Facepunch ships it. VAC, Valve's anti-cheat, is switched on.

Player counts

What is the current population on HAZMA?

At this moment, HAZMA records 0 players across 30 slots. Averaged across the last seven days the population was 0 players, reaching a peak of 1. The last 48 hours show their highest activity at 10:00 UTC, averaging 0 players.

How does HAZMA rank against other Rust servers?

Over the last seven days, HAZMA recorded enough player hours to reach #13,005 worldwide, placing it in the top 58% of all ranked servers.

Operator and location

How reliably does HAZMA stay online?

Right now, you can reach HAZMA. Going by the uptime figure it reports, it restarted about 2 days 15 hours ago. 61 of 168 hours in the last 7 full days were up time, 36% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

How well does HAZMA perform under load?

The 48-hour average is 217 server fps; 137 is the lowest observed. At its highest, it carried 67,469 entities: buildings, deployables and the world's other contents. It reached a ceiling of 4,500 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Where in the world is HAZMA hosted?

No region is published by HAZMA. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 157.85.88.114:22243.

Which Rust version is HAZMA running?

HAZMA is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

What does wipe day look like on HAZMA?

The recent wipes averaged a busiest count of 2 players. 1 hours after the latest wipe, the crowd peaked.

On what timetable does HAZMA run its wipes?

On record so far are too few of HAZMA's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 24 days 14 hours.

Lists and tags

What do the server tags on HAZMA mean?

Tags published by HAZMA and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp30 (Max players): Slots: 30; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does HAZMA appear?

The Rust Server Trends lists that take in HAZMA are: Modded Rust servers, tracked live and Rust PvE servers. You will find it under these filters 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.

Connecting

How do you connect to HAZMA?

Enter client.connect 157.85.88.114:22243 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode You'll find standard Rust survival here.
mp30
Max players Slots: 30.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Difficulty

^v
Vanilla No changed rates, kits or rules: this is the game as Facepunch ships it.

Gameplay

^p
PvE There's no player combat; the world provides the threat.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.