RUST METRICSFlight deck · live data
Data live Servers11,692 Players54,249 Populated3,144 Fresh wipes 3 h123 Scan5 min
‹ All servers185.135.81.17:35006
Offline Full Queue Fresh wipe Wipe due No query

Hazma Rust #2 - Semi Vanilla 2x (Squad)

Offline 185.135.81.17:35006 checked 10d ago

2x biweekly wipes vanillamoddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 50 100 150 200 PAX 0 /200

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,326top 69%
Last wipe14d agobiweekly schedule
Next wipe6d 17hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct8 Oct13 Oct17 Oct22 Oct26 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 6d 17h. The force wipe · high confidence

usual gap10.8 daysbetween real wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 4

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC6d 17hFW
  2. WPT 2Thu 12 Nov, 08:40 UTC13d 7h
  3. WPT 3Thu 26 Nov, 08:40 UTC27d 7h
  4. WPT 4Thu 3 Dec, 19:00 UTC34d 17hFW
  5. WPT 5Thu 10 Dec, 08:40 UTC41d 7h

The first 48 hours of its last wipes

Thu 15 OctSun 4 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 11 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 08:40 UTC14d ago 3 – running 0
Sun 4 Oct, 12:21 UTC25d ago 5 halved by day 4 10.8 days 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 Rust #2 - Semi Vanilla 2x (Squad) when wipe day comes?

At their busiest, its recent wipes drew 4 players on average. Peak crowd on the latest wipe: 11 hours in. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. When it didn't hold, by day 4 it fell below half.

How often does Hazma Rust #2 - Semi Vanilla 2x (Squad) wipe, and when?

The prediction follows its tag, because too few of Hazma Rust #2 - Semi Vanilla 2x (Squad)'s wipes are on record to confirm its schedule. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 14 days 16 hours ago the current world was made. Its tags publish a wipe schedule of one wipe every two weeks.

Lists and filters

Which tags does Hazma Rust #2 - Semi Vanilla 2x (Squad) carry, and what do they mean?

Tags published by Hazma Rust #2 - Semi Vanilla 2x (Squad), read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp200 (Max players): The server holds 200 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): The server runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Hazma Rust #2 - Semi Vanilla 2x (Squad) appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Hazma Rust #2 - Semi Vanilla 2x (Squad): 2x Rust servers, checked live and Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Gather rate: 2x.

Player count

What position does Hazma Rust #2 - Semi Vanilla 2x (Squad) hold among Rust servers?

Player hours over seven days put Hazma Rust #2 - Semi Vanilla 2x (Squad) at #15,326, in the top 69% of all ranked servers.

What is the population on Hazma Rust #2 - Semi Vanilla 2x (Squad)?

Reading for Hazma Rust #2 - Semi Vanilla 2x (Squad): offline at this moment; last seen 10 days 4 hours ago.

Operator and location

Which location does Hazma Rust #2 - Semi Vanilla 2x (Squad) run from?

Reading: location. Hazma Rust #2 - Semi Vanilla 2x (Squad) gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 185.135.81.17:35006.

What Rust version is Hazma Rust #2 - Semi Vanilla 2x (Squad) on?

Rust network protocol 2634 and build 166652 on Windows is the build Hazma Rust #2 - Semi Vanilla 2x (Squad) runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Hazma Rust #2 - Semi Vanilla 2x (Squad), and is it online now?

Check: connection. Hazma Rust #2 - Semi Vanilla 2x (Squad) is offline at this moment. Last contact was 10 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 4 October 2026.

Settings and map

How is Hazma Rust #2 - Semi Vanilla 2x (Squad) configured, and what rules are in force?

The name carries the rate: 2x gather on Hazma Rust #2 - Semi Vanilla 2x (Squad). The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. The server calls itself vanilla, with this meaning: rates, kits and rules are exactly as Facepunch ships them. VAC is on. That is Valve's anti-cheat.

What map is Hazma Rust #2 - Semi Vanilla 2x (Squad) on?

From seed 897176852, the game generates the procedural map on Hazma Rust #2 - Semi Vanilla 2x (Squad). Its size is 4,000. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How do you connect to Hazma Rust #2 - Semi Vanilla 2x (Squad)?

To join: start Rust, press F1 and type client.connect 185.135.81.17:35006. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$r?,v2634,^b,^v,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp200
Max players The server holds 200 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build The server runs game build 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Difficulty

^v
Vanilla Rates, kits and rules are exactly as Facepunch ships them.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter 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.