Working its way up from the back of the class: #15,150 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
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
52/ 100
D
Moving up: up 704 places this week.
A term to build on.
Strongest in momentum (D); standing is 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 5 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
In what location does Hazma Rust #3 - Fast 50x (NoLimit) sit?
You'll find no region listed by Hazma Rust #3 - Fast 50x (NoLimit). Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 185.135.81.76:35000.
How dependable is Hazma Rust #3 - Fast 50x (NoLimit), and is it online at the moment?
You cannot join now: Hazma Rust #3 - Fast 50x (NoLimit) is offline, last seen 12 days 22 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 5 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Hazma Rust #3 - Fast 50x (NoLimit) sit?
You will find Hazma Rust #3 - Fast 50x (NoLimit) on Rust network protocol 2634 and build 166652, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does Hazma Rust #3 - Fast 50x (NoLimit) wipe its map?
The record holds too few of Hazma Rust #3 - Fast 50x (NoLimit)'s wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 23 days 3 hours.
Population
Where does Hazma Rust #3 - Fast 50x (NoLimit) sit among Rust servers?
Over the last seven days, Hazma Rust #3 - Fast 50x (NoLimit) has #15,150 for player hours, in the top 70% of all ranked servers.
Is Hazma Rust #3 - Fast 50x (NoLimit) a busy server?
It has been 12 days 22 hours since Hazma Rust #3 - Fast 50x (NoLimit) was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on Hazma Rust #3 - Fast 50x (NoLimit)?
You'll see Hazma Rust #3 - Fast 50x (NoLimit) tagged with gmrust (Game mode): Survival in the standard Rust style; mp200 (Max players): The server holds 200 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as 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 #3 - Fast 50x (NoLimit) appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Hazma Rust #3 - Fast 50x (NoLimit): Rust servers above 10x gather rate and Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: More than 10x.
Server rules
What settings and rules apply on Hazma Rust #3 - Fast 50x (NoLimit)?
Hazma Rust #3 - Fast 50x (NoLimit) sets gather at 50x, as its name suggests. The group limit stays at the game's default of 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. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Hazma Rust #3 - Fast 50x (NoLimit) uses?
A procedural map of size 4,000 and seed 7681234, generated by the game, is what Hazma Rust #3 - Fast 50x (NoLimit) runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
How to join
What is the way to join Hazma Rust #3 - Fast 50x (NoLimit)?
To connect, start Rust, press F1, and type client.connect 185.135.81.76:35000. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp200
Max playersThe server holds 200 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 momentum (D); standing is the one to work on (F).