Rust StatisticsWorking papers on every public Rust server · 48,164 players now

HAZMA

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 10m ago · 157.85.88.114:22243

Abstract

We describe the public Rust server HAZMA, reached at 157.85.88.114:22243. At the last check it held 0 of 30 places, against a seven-day mean of 0 and a peak of 11. It ranks #13,568 of all servers, the top 61%. It last wiped 23d ago.

Keywordsvanilla modded oxide pve

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/300% full
In the queue0no queue
Seven-day mean0peak 1, 48 h peak 1
Rank2#13,568top 61%
Last wipe23d agono schedule published
Next wipe3–too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
00.250.50.75110:0019:0004:0012:0022:0007:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
010020030040010:0019:0004:0012:0022:0007:00
Figure 2: Server performance. 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.

4Rank

The server stands in the top 61% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep27 Sep3 Oct10 Oct16 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak2players, last three wipes
00.511.52+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Mon 5 Oct, 13:2023d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of HAZMA
Figure 5: The map: Procedural Map, size 3500, seed 50000. Open on RustMaps.
Table 4: The server's published settings.
Address157.85.88.114:22243
Region–
Max players30
Group limit8, the default
Wipe schedule–
Last wipe5 Oct 2026, 13:20 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size3500
Seed50000

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded server list with rates [2], pve wipes and settings [3] and Rust wipe forecast [4].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 253 on average116/2000
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 242 on average122/2000
Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 106 on average40/200
【炮炮PVE启蒙】纯净｜特色｜突袭｜技能EA · groups of 16+ · biweekly · 58 on average67/200
[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendlgroups of 30+ · monthly · 54 on average27/300
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 50 on average34/100

Appendix AQuick answers

From the figures on this page.

Server details

A.1How well does HAZMA run?

The server fps averaged 222 over the last 48 hours, never dropping below 193. Its entity count reached a maximum of 67,469, including buildings, deployables and all other world objects. Memory use peaked at 4,104 MB. Players experience lag when fps is low and the entity count is rising.

A.2In which location is HAZMA based?

There is no region published for HAZMA. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 157.85.88.114:22243.

A.3What is the online status and reliability of HAZMA?

HAZMA is online at this time. It last restarted around 44 hours ago, according to its reported uptime. Its uptime over the last full days (7 days) was 22%, with 37 of 168 hours online. It was first observed on 13 September 2026 by Rust Statistics.

A.4What version of Rust is run on HAZMA?

The version of Rust on HAZMA is network protocol 2635 and build 168909, and the operating system is Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.5On what cycle does HAZMA wipe?

There are not yet enough recorded wipes for HAZMA to reveal its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. The world currently in use was created 23 days 19 hours ago.

A.6How would you describe wipe day on HAZMA?

Across its recent wipes, the average peak population was 2 players. The peak on the latest wipe came 1 hours after it began.

Population

A.7What is the rank of HAZMA among Rust servers?

Ranked by player hours across seven days, HAZMA holds #13,568, in the top 61% of all ranked servers.

A.8How would you characterise the player activity on HAZMA?

On HAZMA, 0 of the 30 slots are occupied at present. Averaged over the last seven days: 0 players; the same period peaks at 1. Averaging 1 players, 11:00 UTC was the busiest hour of the past 48.

Tags and filters

A.9How should the tags on HAZMA be interpreted?

gmrust (Game mode): Survival on standard Rust rules; mp30 (Max players): The slot count is 30; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset; ^v (Vanilla): This is the game as Facepunch ships it, with rates, kits and rules unaltered; ^p (PvE): The threat is the world, not other players; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags HAZMA publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.10Where can HAZMA be found among the Rust Statistics lists and filters?

These Rust Statistics lists include HAZMA: Modded Rust servers and Rust PvE servers: live list. You will find it on the server list filtered by: Type: Vanilla and Modded; Game mode: PvE; Server tag: Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Settings and map

A.11What are the settings and rules that govern HAZMA?

The name of HAZMA states no gather rate. At 8 players, the group limit equals the game's default. The mode is pve, which means fighting other players is excluded. Plugins or settings change the game; the browser files it under Modded. Oxide plugins are running. It describes itself as vanilla, which is to say this is the game as Facepunch ships it, with rates, kits and rules unaltered. The server has VAC on, Valve's anti-cheat.

A.12On which map does HAZMA take place?

Size 3,500 and seed 50000 define the procedural, game-generated map on HAZMA. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.

Connection

A.13What steps are required to join HAZMA?

Enter client.connect 157.85.88.114:22243 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp30,ptrak,$r?,v2635,^v,^p,gmrust,cs168909,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp30Max players. The slot count is 30.
ts8Group limit. 8 per team, the value the game sets by default.
v2635Protocol. Joining requires the same game version: protocol 2635.
cs168909Build. Build 168909 is the one running.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. The region code is unset.
Difficulty
^vVanilla. This is the game as Facepunch ships it, with rates, kits and rules unaltered.
Gameplay
^pPvE. The threat is the world, not other players.
Mods and access
^oOxide. Oxide (uMod), a plugin framework, runs on this server.
^zModded. Modded listing: plugins or settings modify 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Pve wipes and settings. ruststatistics.org/top-rust-pve-servers.
  4. [4]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.