On the class lists: C− (59), with population over 48 hours and no performance mark.
Players now0/ 1500% full
7-day average0peak 2
Rank#4,922top 22% · #841 in NA
Last wipe6d agoweekly schedule
Next wipe7d 8hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 150 on average. Plenty of space to grow.
Standingrank on player hours
78/ 100
B
Holds a respectable place: #4,922 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
33/ 100
F
Needs to work on its frame rate: 20 server fps on average.
Wipeskeeping the crowd after a wipe
60/ 100
C
Keeps a fair share of its players through a wipe: 60% of wipes kept half their crowd.
Momentumrank now against a week ago
60/ 100
C
Moving up: up 938 places this week.
A term to build on.
Strongest in uptime (A+); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 22% of all ranked servers, top 45% in NA, and #308 of the quad servers (top 37%). Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
···W···
···F···
···W···
···W···
···W···
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h.
The force wipe · high confidence
usual gap14 daysbetween real wipes
on rhythm80%of its recent wipes
wipe-day peak1players, last three wipes
crowd held60%else halves by day 1.5
Coming wipes
7d 8hThu 5 Nov, 19:00 UTCFW
21d 9hThu 19 Nov, 20:04 UTC
35d 8hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 22 OctThu 15 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 20:04 UTC6d ago
1
–
running
0
Thu 15 Oct, 22:18 UTC13d ago
2
✓ held half
6.9 days
1
Thu 8 Oct, 20:05 UTC20d ago
1
halved by day 2
7.1 days
0
Thu 1 Oct, 20:11 UTCFW27d ago
2
✓ held half
7 days
0
Thu 24 Sep, 20:12 UTC34d ago
3
halved by day 1
7 days
0
Thu 17 Sep, 20:16 UTC41d ago
2
✓ held half
7 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
Where in the world is [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad?
The NA tag places [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad in North America, and the region code is us1. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 185.141.204.9:28016.
Is [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad up, and how steady is its uptime?
You can join now: [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad is online. The uptime it reports puts the last restart at about 6 days 13 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
Does [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad perform well?
It never fell below 10 server fps in the last 48 hours, averaging 20. Up to 93,410 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 4,403 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad running?
The server [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad is on Rust network protocol 2635 and build 168909 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad wipe its map?
Wipes come every other Thursday at 20:04 UTC on [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 6 days 14 hours. Wipes are scheduled weekly, according to its tags.
What happens on [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad when wipe day arrives?
The average peak on its recent wipes was 1 players. Peak numbers came 3 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 60% of its recent wipes. The crowd dropped below half by day 1.5 in the wipes where it did not hold.
Player count
Where does [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad place in the wider field of Rust servers?
Over the last seven days, [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad has #4,922 for player hours, in the top 22% of all ranked servers and #841 in North America. It comes #308 among servers in the quad group.
What does the population on [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad look like?
With 150 slots available, [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad currently has 0 players. It peaked at 2 and averaged 0 players over the last seven days. The busiest time in the last 48 hours was 00:00 UTC, with an average of 1 players.
Tags and filters
How should you read the tags on [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad?
gmrust (Game mode): Rust survival, played by the standard rules; mp150 (Max players): Its slot count is 150; ts4 (Group limit): A team can hold 4 players at most; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $rus1 (Region code): Region code: us1; ^w (Weekly): It wipes weekly; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): The server browser lists it under North America; sc3 (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one are the tags [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad publishes, and the game's server browser reads them. 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 [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad: 2x Rust servers, graded, Modded Rust servers, graded and North America Rust servers, graded. It shows under the following filters on the server list: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Quad; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.
Server rules
Which rules does [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad enforce, and what are its settings?
Going by its name, [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad runs 2x gather. You can have up to 4 players in a group (quad). survival is the mode 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.
Which map is in play on [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad?
The game generates the procedural map on [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad at size 4,000 with seed 1367813147. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
What is the way to join [US] HellsGamers 2x #1 | Solo/Duo/Trio/Quad?
Enter client.connect 185.141.204.9:28016 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://discord.com/invite/nGwg8PcUVb.
Server tags
what each one means
Published asmp150,ptrak,$rus1,v2635,^w,NA,gmrust,cs168909,sc3,ts4,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp150
Max playersIts slot count is 150.
ts4
Group limitA team can hold 4 players at most.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$rus1
Region codeRegion code: us1.
Wipe schedule
^w
WeeklyIt wipes weekly.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
NA
North AmericaThe server browser lists it under North America.
Other
sc3
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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 uptime (A+); population is the one to work on (F).