RUST METRICSFlight deck · live data
Data live Servers11,672 Players34,284 Populated2,842 Fresh wipes 3 h85 Scan5 min
‹ All servers91.99.37.118:28103
Online Full Queue Fresh wipe Wipe due No query

24HG | Rust | Main #1

Online 91.99.37.118:28103 checked 8m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Thu 02:00 UTC
0 50 100 150 200 PAX 1 /200

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 60 SERVER FPS

Server fps

48 h low 60 · below 20 is lag, below 10 is bad
0 10 20 30 40 ENT 18,841 ×1000

Entities

48 h range 5,617–18,990 · memory 2,892 MB
1239 ET SINCE RESTART 3D 05H

Uptime

3 days 5 hours since its last restart, at the last reading
7-day average1peak 5
Rank#3,513top 16%
Last wipe3d agono schedule published
Next wipe–no rhythm it keeps
Memory2,892MB48 h peak 5 players
REC 1

Players

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

Hourly average and peak, UTC.

REC 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.

REC 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.

PLAN

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

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

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on 24HG | Rust | Main #1 when wipe day comes?

The busiest point of its recent wipes drew 4 players on average. 4 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 33% of recent wipes. When it didn't hold, by day 4 it fell below half.

How often does 24HG | Rust | Main #1 wipe, and when?

No next wipe can be predicted for 24HG | Rust | Main #1, which wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 3 days 6 hours ago.

Lists and filters

How should you read the tags on 24HG | Rust | Main #1?

Check: tags. The game's server browser reads gmvanilla (Game mode): The mode is vanilla survival; mp200 (Max players): The server holds 200 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server from 24HG | Rust | Main #1. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does 24HG | Rust | Main #1 appear in Rust Metrics lists and filters?

On Rust Metrics, 24HG | Rust | Main #1 sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Population

Where does 24HG | Rust | Main #1 sit in the rankings?

Player hours over seven days put 24HG | Rust | Main #1 at #3,513, in the top 16% of all ranked servers.

How full does 24HG | Rust | Main #1 get?

Current headcount on 24HG | Rust | Main #1: 1 players, 200 slots available. Check: players over seven days. Average 1, peak 5. Check: 48-hour peak. 21:00 UTC, 5 players on average.

Operator and location

Which location does 24HG | Rust | Main #1 run from?

Reading: location. 24HG | Rust | Main #1 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 91.99.37.118:28103.

What Rust version is 24HG | Rust | Main #1 on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by 24HG | Rust | Main #1. To get in, your game needs the same protocol; Steam applies the update.

Is performance on 24HG | Rust | Main #1 within range?

Reading: 60 server fps on average across the last 48 hours. It never dropped below 60. Peak entity count: 18,990. Buildings, deployables and all else included. Reading: 2,991 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on 24HG | Rust | Main #1, and is it online?

Check: connection. 24HG | Rust | Main #1 is online at this moment. Reading: uptime. About 3 days 5 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

How is 24HG | Rust | Main #1 configured, and what rules are in force?

No gather rate appears in the name: 24HG | Rust | Main #1. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on 24HG | Rust | Main #1?

Size 4,000 and seed 1337: the game generates the procedural map on 24HG | Rust | Main #1 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Read the map name: Custom Map.

Connection

What do you do to join 24HG | Rust | Main #1?

To join: start Rust, press F1 and type client.connect 91.99.37.118:28103. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://alpha.24hgaming.com/.

PLACARDS

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 server holds 200 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Plugins or settings make this a modded server.

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.