StatusLive Servers online11,669 Players34,137 Populated2,836 Wiped · 3 h86 Interval5 min Date29 OCT 2026

DWG RG-S3513Server sheetchecked 11m ago

24HG | Rust | Main #1

Online 91.99.37.118:28103 checked 11m ago

moddedoxide
Connect
Players now 1/ 200 0% full
7-day average1peak 5
Rank#3,513top 16%
Last wipe3d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
0246804:0013:0022:0007:0016:0002:00

Hourly average and peak, UTC.

Fig. 1Players on 24HG | Rust | Main #1
Fig. 2

Server performance

02040608004:0013:0022:0007:0016:0002:00

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 16% of all ranked servers. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap9.2 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak4players, last three wipes
crowd held33%else halves by day 4

The first 48 hours of its last wipes

Sun 25 OctThu 15 OctWed 14 Oct
01234+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 3, 4 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 25 Oct, 15:14 UTC3d ago 3 – running 0
Thu 15 Oct, 19:14 UTC13d ago 4 held half 9.8 days 0
Wed 14 Oct, 19:01 UTC14d ago 4 – 1 days 0
Sun 4 Oct, 07:36 UTC24d ago 3 halved by day 2 10.5 days 0
Fri 25 Sep, 18:20 UTC33d ago 2 halved by day 6 8.6 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 154 on average
26 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
130 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average
35 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average
11 / 700
05
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
3 / 200
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
1 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

How reliable is 24HG | Rust | Main #1, and is it online now?

At this moment 24HG | Rust | Main #1 is online. The uptime it reports puts the last restart at about 3 days 5 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. On 13 September 2026 is when Rust Graphs first saw it.

What does the recorded performance of 24HG | Rust | Main #1 show?

The last 48 hours give an average of 60 server fps and a floor of 60. Counted at its highest: 18,990 entities, buildings, deployables and the rest of the world included. Memory use peaked at 2,991 MB. Players feel low fps and a climbing entity count as lag.

What location is recorded for 24HG | Rust | Main #1?

A region is not published by 24HG | Rust | Main #1. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 91.99.37.118:28103 is its address.

On which Rust version is 24HG | Rust | Main #1 running?

On Linux, 24HG | Rust | Main #1 runs Rust network protocol 2635 and build 168909. The same protocol is required for joining, and Steam updates your game to it.

Player data

What does the population history show for 24HG | Rust | Main #1?

At the last refresh, 24HG | Rust | Main #1 recorded 1 players across 200 slots. Averaged across seven days, the player count is 1, with a peak of 5. Over the last 48 hours the busiest hour was 21:00 UTC, at an average of 5 players.

What rank has been recorded for 24HG | Rust | Main #1?

Over the last seven days, 24HG | Rust | Main #1 records #3,513 for player hours: the top 16% of all ranked servers.

Schedules

What happens on 24HG | Rust | Main #1 on the day of a wipe?

The recent wipes averaged a busiest count of 4 players. At 4 hours after the latest wipe the crowd was at its peak. The crowd stayed above half the peak until the next wipe in 33% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 4.

Which times and days are wipes plotted at on 24HG | Rust | Main #1?

There is no next wipe to predict at 24HG | Rust | Main #1, which wipes at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The current world has been in use since 3 days 6 hours ago.

Settings

Which rules and settings are recorded for 24HG | Rust | Main #1?

The name of 24HG | Rust | Main #1 records no gather rate. Eight players per group: the default for the game. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Listed as Modded in the server browser: the game is changed by plugins or settings. Plugins run: Oxide. VAC is on: that is Valve's anti-cheat.

On which map is 24HG | Rust | Main #1 played?

Seed 1337 and size 4,000 define the procedural map 24HG | Rust | Main #1 generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing. Recorded map name: Custom Map.

Tags

Where does 24HG | Rust | Main #1 appear among the Rust Graphs lists and filters?

These Rust Graphs lists include 24HG | Rust | Main #1: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

On 24HG | Rust | Main #1, what is meant by each tag?

Tags published by 24HG | Rust | Main #1, and read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp200 (Max players): The slot count is 200; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): 168909 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Connect

What is the way to connect to 24HG | Rust | Main #1?

Enter client.connect 91.99.37.118:28103 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. You will find its website at https://alpha.24hgaming.com/.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp200,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp200
Max players The slot count is 200.
ts8
Group limit Teams are capped at 8, the default setting.
v2635
Protocol Your game must match protocol 2635 to join.
cs168909
Build 168909 is the game build.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is 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.

KeyTag string decoded