Working its way up from the back of the class: #12,988 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
20/ 100
F
Lost ground: down 7,772 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 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 59% 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 Friday 30 October, 00:59 UTC, in 17h.
Its weekly schedule tag · low confidence
usual gap5.9 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 2
Coming wipes
17hFri 30 Oct, 00:59 UTC
7d 11hThu 5 Nov, 19:00 UTCFW
7d 17hFri 6 Nov, 00:59 UTC
14d 17hFri 13 Nov, 00:59 UTC
21d 17hFri 20 Nov, 00:59 UTC
28d 17hFri 27 Nov, 00:59 UTC
35d 11hThu 3 Dec, 19:00 UTCFW
35d 17hFri 4 Dec, 00:59 UTC
The first 48 hours of its last wipes
Fri 9 OctSat 3 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 10 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 9 Oct, 00:59 UTC20d ago
2
–
running
0
Sat 3 Oct, 02:50 UTC26d ago
1
halved by day 2
5.9 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 · weekly · 129 on average
24 / 100
Quick answers
from the figures on this page
Server details
Which region is Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) based in?
Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 185.135.81.17:35000.
Is Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) up, and how steady is its uptime?
The server is down: Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) is offline now, with the last sighting 10 days 10 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 3 October 2026.
On what Rust version does Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) sit?
You will find Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) on Rust network protocol 2634 and build 166652, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) wipe, and how often?
Too few wipes on Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) are recorded to confirm the schedule, so its tag guides the prediction. Expect the next wipe on Friday 30 October at 00:59 UTC. 20 days 6 hours have passed since this world was made. Its tags state that it wipes weekly.
What should you expect from wipe day on Hazma Rust #1 - Modded 2x (Solo/Duo/Trio)?
Across its recent wipes, the busiest moments averaged 2 players. The crowd on the latest wipe was largest 10 hours after it began. Half the peak held until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 2 in the wipes where it did not hold.
Player numbers
Where does Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) place in the wider field of Rust servers?
Over the last seven days, Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) has #12,988 for player hours, in the top 59% of all ranked servers.
How many players does Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) usually have?
It has been 10 days 10 hours since Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on Hazma Rust #1 - Modded 2x (Solo/Duo/Trio)?
You'll see Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^w (Weekly): A wipe happens every week; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Hazma Rust #1 - Modded 2x (Solo/Duo/Trio): 2x Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Gather rate: 2x.
Rules and settings
What settings and rules apply on Hazma Rust #1 - Modded 2x (Solo/Duo/Trio)?
The name of Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) points to a 2x gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) uses?
A procedural map of size 4,000 and seed 621411223, generated by the game, is what Hazma Rust #1 - Modded 2x (Solo/Duo/Trio) runs. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
Getting in
How should you connect to Hazma Rust #1 - Modded 2x (Solo/Duo/Trio)?
To connect, start Rust, press F1, and type client.connect 185.135.81.17:35000. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^w,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyA wipe happens every week.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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).