On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 2000% full
7-day average0peak –
Rank#15,353top 69%
Last wipe13d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 200 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,353 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
100/ 100
A+
Runs smoothly: 125 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 228 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 01:00 UTC13d ago
0
–
running
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
No region is published for 24HG | Rust | Main #2. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 91.99.37.118:28107.
How reliable is 24HG | Rust | Main #2, and is it up?
The server is up: 24HG | Rust | Main #2 is online now. The uptime it reports puts the last restart at about 13 days 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 24HG | Rust | Main #2 perform well?
It never fell below 76 server fps in the last 48 hours, averaging 125. Buildings, deployables and everything else in the world added up to as many as 114,045 entities. Up to 6,333 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is 24HG | Rust | Main #2 on?
You will find 24HG | Rust | Main #2 on Rust network protocol 2634 and build 167781, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does 24HG | Rust | Main #2 reset?
24HG | Rust | Main #2 has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 13 days 1 hours.
What happens on 24HG | Rust | Main #2 when wipe day arrives?
The average peak on its recent wipes was 0 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does 24HG | Rust | Main #2 sit among Rust servers?
In the top 69% of all ranked servers, 24HG | Rust | Main #2 sits at #15,353 for player hours over the last seven days.
What does the population on 24HG | Rust | Main #2 look like?
With 200 slots available, 24HG | Rust | Main #2 currently has 0 players. For the last seven days, the average number of players was 0.
Lists and filters
What is meant by the tags on 24HG | Rust | Main #2?
You'll see 24HG | Rust | Main #2 tagged with gmvanilla (Game mode): Survival, vanilla style; mp200 (Max players): Its slot count is 200; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show 24HG | Rust | Main #2?
Rust Server Score lists that include 24HG | Rust | Main #2: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules and settings
Which rules does 24HG | Rust | Main #2 enforce, and what are its settings?
The name of 24HG | Rust | Main #2 gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. The server runs Valve's anti-cheat, VAC.
24HG | Rust | Main #2 runs which map?
A procedural map of size 4,500 and seed 2037386420, generated by the game, is what 24HG | Rust | Main #2 runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How do you get onto 24HG | Rust | Main #2?
Enter client.connect 91.99.37.118:28107 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://alpha.24hgaming.com/.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,gmvanilla,cs167781,ts8,^z,^y
Game
gmvanilla
Game modeSurvival, vanilla style.
mp200
Max playersIts slot count is 200.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: Carbon.
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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).