Rust Data

rustdata.spaceservers185.135.81.17:35008.ipynb

Run all rust-data · live

‹ All servers

Offline 185.135.81.17:35006 checked 9d ago

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

2x biweekly wipes vanillamoddedoxide

Connect

srv = rust.server("185.135.81.17:35008")
print(srv.connect_command)

Right now

srv.summary()
players now 0/200 # 0% full
7-day average 0 # peak –
rank #15,326 # top 69%
last wipe 14d ago # biweekly schedule
next wipe 6d 22h # Thu 5 Nov, 19:00 UTC FW
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 6d 22h. # 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

inatkind
06d 22hThu 5 Nov, 19:00 UTCFW force wipe
113d 11hThu 12 Nov, 08:40 UTCwipe
227d 11hThu 26 Nov, 08:40 UTCwipe
334d 22hThu 3 Dec, 19:00 UTCFW force wipe
441d 11hThu 10 Dec, 08:40 UTCwipe

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 15 Oct, 08:40 UTC14d ago 3 NaN running 0
1 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.

display(srv.map, srv.info())

Map

4000 · seed 897176852
Map of Hazma Rust #2 - Semi Vanilla 2x (Squad)
map
Procedural Map
size
4000
seed
897176852
Open on RustMaps

Server

srv.info()
address
185.135.81.17:35006
region
–
max players
200
group limit
8, the default
wipe schedule
biweekly
last wipe
15 Oct 2026, 08:40 UTC
hostname
–
first seen
4 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0SURVIVORS.GG #2 [ 2x Vanilla ] WIPED 27.10groups of 8+ · 2x · biweekly · 178 on average68/200
1Atlas - EU 2X Medium | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · biweekly · 140 on average1301/1450
2SURVIVORS.GG #7 [ 2x Vanilla ] WIPED 28.10groups of 30+ · 2x · biweekly · 117 on average199/225
3[SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10EA · groups of 8+ · 2x · biweekly · 84 on average22/115
4ДЛЯ НОВИЧКОВ | КЛАССИКА X2 |KARMA RUST 24.10EU · groups of 10+ · 2x · biweekly · 52 on average18/200
5PROSTOJ #6 | Ресурсы x2 | Компоненты x1EU · groups of 8+ · 2x · biweekly · 50 on average6/200

Quick answers

From the figures on this page.

Player counts

What position does Hazma Rust #2 - Semi Vanilla 2x (Squad) take in the server rankings?

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

What population does Hazma Rust #2 - Semi Vanilla 2x (Squad) carry?

Hazma Rust #2 - Semi Vanilla 2x (Squad) returns no live count at this refresh, having last been seen 9 days 23 hours ago.

Server data

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

Version Rust network protocol 2634 and build 166652 on Windows is reported by Hazma Rust #2 - Semi Vanilla 2x (Squad). The protocol has to match before you can join, and Steam does the updating.

Is Hazma Rust #2 - Semi Vanilla 2x (Squad) up, and what does its uptime show?

The latest sample has Hazma Rust #2 - Semi Vanilla 2x (Squad) offline, with a last sighting 9 days 23 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 4 October 2026.

Where does Hazma Rust #2 - Semi Vanilla 2x (Squad) sit?

No region is published by Hazma Rust #2 - Semi Vanilla 2x (Squad). Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 185.135.81.17:35006.

Settings and map

Which rules apply on Hazma Rust #2 - Semi Vanilla 2x (Squad), and what settings?

2x gather is what the name states, and the name is Hazma Rust #2 - Semi Vanilla 2x (Squad). The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Its own label is vanilla: untouched settings: rates, kits and rules as shipped. Anti-cheat status: VAC on.

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

The game generates the map on Hazma Rust #2 - Semi Vanilla 2x (Squad): procedural, size 4,000, seed 897176852. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

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

Too few wipes are on record for Hazma Rust #2 - Semi Vanilla 2x (Squad) to confirm its schedule, so the tag drives the prediction. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 14 days 12 hours ago. A fortnightly wipe schedule is published in its tags.

What is wipe day on Hazma Rust #2 - Semi Vanilla 2x (Squad) like?

Across recent wipes the busiest point averaged 4 players. 11 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 4.

Tags, lists

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

The Rust Data lists that Hazma Rust #2 - Semi Vanilla 2x (Squad) fits are: Modded Rust servers and 2x Rust servers. It appears under these filters on the server list: 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.

Which meanings do the tags on Hazma Rust #2 - Semi Vanilla 2x (Squad) hold?

Read by the game's server browser, the tags Hazma Rust #2 - Semi Vanilla 2x (Squad) publishes are: gmrust (Game mode): Survival play, standard Rust; mp200 (Max players): Slot count: 200; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^b (Biweekly): Two weeks between wipes; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

How can I connect to Hazma Rust #2 - Semi Vanilla 2x (Squad)?

In Rust, F1 opens the console: type client.connect 185.135.81.17:35006. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp200
Max players Slot count: 200.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs166652
Build Recorded game build: 166652.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Two weeks between wipes.

Difficulty

^v
Vanilla Untouched settings: rates, kits and rules as shipped.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 94,909 players 11,835 servers online