Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO R SRV11,644online PAX43,541playing OCC3,049with players WIPED 3H97
MODModded traffic
Callsign

HZM13569=

HAZMA

Online 157.85.88.114:22243 checked 12m ago

vanillamoddedoxidepve
Clearance · join
Players now 0/ 30 0% full
7-day average0peak 1
Rank#13,569top 61%
Last wipe23d agono schedule published
Next wipe–too few wipes seen yet
Track history

Players

AveragePeak
00.250.50.75110:0019:0004:0012:0022:0007:00

Hourly average and peak, UTC.

Server performance

010020030040010:0019:0004:0012:0022:0007: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
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.

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

Wipes

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

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign BRT016NA · no group limit · biweekly · 252 on average [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo
    Players 139/2000
  2. 02MOD
    Callsign BRT016EU · no group limit · biweekly · 242 on average [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo
    Players 126/2000
  3. 03MOD
    Callsign CHR017NA · groups of 8+ · biweekly · 106 on average Chrayntopia ♡ ︎PvE | RP | PvP
    Players 47/200
  4. 04MOD
    Callsign PVE016EA · groups of 16+ · biweekly · 58 on average 【炮炮PVE启蒙】纯净|特色|突袭|技能
    Players 63/200
  5. 05MOD
    Callsign RLC015groups of 30+ · monthly · 54 on average [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl
    Players 26/300
  6. 06MOD
    Callsign TRV010EU · groups of 30+ · biweekly · 50 on average TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10
    Players 7/100
ATIS · this server

Quick answers

From the figures on this page.

Tags

Which lists and filters on Rust Tracker show HAZMA?

PvE servers, tracked live and Modded servers, tracked live — the Rust Tracker lists that include HAZMA. On the server list, these filters bring it up: Type: Vanilla and Modded; Game mode: PvE; Server tag: Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

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

These tags are published by HAZMA for the game's server browser to read: gmrust (Game mode): Standard survival mode for Rust; mp30 (Max players): Capacity: 30 slots; ts8 (Group limit): Default team size: 8; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): No region code is set; ^v (Vanilla): As Facepunch ships it: rates, kits and rules are unchanged; ^p (PvE): No player fights — the world is the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.

Wipe Schedule

What should you expect on HAZMA when wipe day lands?

Recent wipes averaged a peak of 2 players. The peak on the latest wipe came 1 hours after it.

When does HAZMA wipe?

The record holds too few of HAZMA's wipes to show its rhythm. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. This world has been running 23 days 19 hours.

Location and Status

What is the uptime on HAZMA, and is it online?

Right now HAZMA is online. About 44 hours ago it restarted last, based on reported uptime. 37 of 168 hours up over the last 7 full days: 22% uptime. The first sighting by Rust Tracker was 13 September 2026.

Which Rust build is HAZMA running?

Confirmed for HAZMA: Rust network protocol 2635 and build 168909, Linux. The same protocol is required to join, and Steam updates it for you.

Is HAZMA holding performance?

Average server fps over the last 48 hours: 222, with a low of 193. Peak entity count: 67,469, covering buildings, deployables and all else in the world. Peak memory use: 4,104 MB. A climbing entity count and low fps are what register as lag for players.

Where does HAZMA sit?

Region: none published by HAZMA. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 157.85.88.114:22243.

Population

What is the player count on HAZMA?

HAZMA is at 0 players, capacity 30. Seven-day average 0 players; peak 1. Peak traffic in the last 48 hours came at 11:00 UTC, averaging 1 players.

Where does HAZMA sit in the server rankings?

Seven-day player hours put HAZMA at #13,569, within the top 61% of all ranked servers.

Settings

Which settings and rules are confirmed on HAZMA?

Nothing in HAZMA's name states a gather rate. Up to 8 players per group, the game's default. It runs pve, fighting between players is off. Plugins or settings change the game, and the server browser lists it under Modded. The plugin count stands at Oxide. Vanilla is its own label: as Facepunch ships it: rates, kits and rules are unchanged. On: VAC, Valve's anti-cheat.

What map is HAZMA on?

The map on HAZMA is procedural, size 3,500, seed 50000, generated by the game. Look at it on RustMaps from this page: equal size and seed return the same map.

Connect

How do you get onto HAZMA?

Open the console in Rust with F1 after starting the game, then type client.connect 157.85.88.114:22243. Alternatively, Launch Rust here opens Rust via Steam and connects you.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival mode for Rust.
mp30
Max players Capacity: 30 slots.
ts8
Group limit Default team size: 8.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code No region code is set.

Difficulty

^v
Vanilla As Facepunch ships it: rates, kits and rules are unchanged.

Gameplay

^p
PvE No player fights — the world is the danger.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it is 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.