Rust Server TrendsSeismic network · station log
Recording Stations11,892 Players102,455 Active3,980 Wipes · 3 h459 48 h

Station XX-15327 · no signal

IRONHAVEN QA - staging (not public)

Offline 73.164.1.196:28315 checked 7d ago

moddedcarbon
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,327
top 69%
Last wipe
7d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15327 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k21 Sep29 Sep6 Oct14 Oct21 Oct29 Oct

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

Expected events

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.

usual gap
16.4 daysbetween real wipes
wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

Thu 22 OctTue 6 Oct
01234+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 22 Oct, 17:21 UTC7d ago M0.0steady 0 – – running 0
Tue 6 Oct, 07:23 UTC23d ago M0.0steady 0 – 16.4 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 151 on average
113/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
135/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
188/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 95 on average
72/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 90 on average
208/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 85 on average
349/ 350
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on IRONHAVEN QA - staging (not public)?

The map on IRONHAVEN QA - staging (not public) is procedural, produced by the game.

Which settings and rules apply on IRONHAVEN QA - staging (not public)?

You will find no gather rate in the name of IRONHAVEN QA - staging (not public). At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Carbon. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on IRONHAVEN QA - staging (not public)?

A reading taken now finds IRONHAVEN QA - staging (not public) offline; the most recent activity was 7 days 1 hours ago. The seven-day average for this server is 0 players.

How does IRONHAVEN QA - staging (not public) rank against other Rust servers?

On player hours for the past week, IRONHAVEN QA - staging (not public) sits at #15,327, which puts it inside the top 69% of every ranked server.

Operator and location

How reliably does IRONHAVEN QA - staging (not public) stay online?

No contact with IRONHAVEN QA - staging (not public) right now, and the last recorded contact was 7 days 1 hours ago. 18 of 168 hours in the last 7 full days were up time, 11% of the total. On 21 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does IRONHAVEN QA - staging (not public) run from?

A region is not published by IRONHAVEN QA - staging (not public). Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 73.164.1.196:28315.

What build of Rust does IRONHAVEN QA - staging (not public) use?

On Linux, IRONHAVEN QA - staging (not public) runs Rust network protocol 2634 and build 167584. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on IRONHAVEN QA - staging (not public)?

On average, the busiest point of its recent wipes drew 0 players. 0 hours after the latest wipe, the crowd peaked.

How often does IRONHAVEN QA - staging (not public) wipe, and on which days?

On record so far are too few of IRONHAVEN QA - staging (not public)'s wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 7 days 1 hours is how long the current world has been running.

Tags

What do the server tags on IRONHAVEN QA - staging (not public) mean?

These are the tags IRONHAVEN QA - staging (not public) publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167584 (Build): It runs game build 167584; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does IRONHAVEN QA - staging (not public) appear?

These Rust Server Trends lists include IRONHAVEN QA - staging (not public): Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Join the server

How do you connect to IRONHAVEN QA - staging (not public)?

Enter client.connect 73.164.1.196:28315 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167584,ts8,^z,^y

Game

gmrust
Game mode You'll find standard Rust survival here.
mp10
Max players The server has 10 slots.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167584
Build It runs game build 167584.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.