Working its way up from the back of the class: #15,326 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
15/ 100
F
Lost ground: down 10,855 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); wipes are the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
···W···
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h.
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
6d 20hThu 5 Nov, 19:00 UTCFW
13d 10hThu 12 Nov, 08:40 UTC
27d 10hThu 26 Nov, 08:40 UTC
34d 20hThu 3 Dec, 19:00 UTCFW
41d 10hThu 10 Dec, 08:40 UTC
The first 48 hours of its last wipes
Thu 15 OctSun 4 Oct
Players each hour, from the hour of the wipe. The latest peaked at 3, 11 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
EU · groups of 300+ · 2x · biweekly · 50 on average
292 / 350
Quick answers
from the figures on this page
About the server
Which region is Hazma Rust #2 - Semi Vanilla 2x (Squad) based in?
No region is published for Hazma Rust #2 - Semi Vanilla 2x (Squad). The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 185.135.81.17:35006.
Is Hazma Rust #2 - Semi Vanilla 2x (Squad) up, and how steady is its uptime?
The server is down: Hazma Rust #2 - Semi Vanilla 2x (Squad) is offline now, with the last sighting 10 days 1 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 4 October 2026.
Which Rust version is Hazma Rust #2 - Semi Vanilla 2x (Squad) running?
Rust network protocol 2634 and build 166652 on Windows is what Hazma Rust #2 - Semi Vanilla 2x (Squad) runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does Hazma Rust #2 - Semi Vanilla 2x (Squad) wipe, and how often?
Too few wipes on Hazma Rust #2 - Semi Vanilla 2x (Squad) are recorded to confirm the schedule, so its tag guides the prediction. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 14 days 13 hours have passed since this world was made. Its tags give a wipe schedule of every two weeks.
What happens on Hazma Rust #2 - Semi Vanilla 2x (Squad) when wipe day arrives?
Across its recent wipes, the busiest moments averaged 4 players. Peak numbers came 11 hours into the latest wipe. Half the peak held until the next wipe in 0% of its recent wipes. Day 4 is when it sank below half in the wipes that did not hold.
Player numbers
Where does Hazma Rust #2 - Semi Vanilla 2x (Squad) sit among Rust servers?
Over the last seven days, Hazma Rust #2 - Semi Vanilla 2x (Squad) has #15,326 for player hours, in the top 69% of all ranked servers.
How many players does Hazma Rust #2 - Semi Vanilla 2x (Squad) usually have?
It has been 10 days 1 hours since Hazma Rust #2 - Semi Vanilla 2x (Squad) was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on Hazma Rust #2 - Semi Vanilla 2x (Squad)?
The game's browser takes its cue from the tags Hazma Rust #2 - Semi Vanilla 2x (Squad) has set: gmrust (Game mode): Survival in the standard Rust style; mp200 (Max players): Its slot count is 200; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^b (Biweekly): A wipe happens once a fortnight; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Hazma Rust #2 - Semi Vanilla 2x (Squad)?
Rust Server Score lists that include Hazma Rust #2 - Semi Vanilla 2x (Squad): 2x Rust servers, graded and Modded Rust servers, graded. These filters bring it up 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.
Server rules
Which rules does Hazma Rust #2 - Semi Vanilla 2x (Squad) enforce, and what are its settings?
Hazma Rust #2 - Semi Vanilla 2x (Squad) sets gather at 2x, as its name suggests. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. Vanilla is what it calls itself: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Hazma Rust #2 - Semi Vanilla 2x (Squad)?
A procedural map of size 4,000 and seed 897176852, generated by the game, is what Hazma Rust #2 - Semi Vanilla 2x (Squad) runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to Hazma Rust #2 - Semi Vanilla 2x (Squad)?
Enter client.connect 185.135.81.17:35006 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,^b,^v,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp200
Max playersIts slot count is 200.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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.
A term to build on. Strongest in standing (F); wipes are the one to work on (F).