Rust StatisticsWorking papers on every public Rust server · 99,188 players now

IRONHAVEN QA - staging (not public)

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 7d ago · 73.164.1.196:28315

Abstract

We describe the public Rust server IRONHAVEN QA - staging (not public), reached at 73.164.1.196:28315. It is offline at the last check, against a seven-day mean of 01. It ranks #15,327 of all servers, the top 69%. It last wiped 7d ago.

Keywordsmodded carbon

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/100% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,327top 69%
Last wipe7d agono schedule published
Next wipe3–too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: Server performance. 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.

4Rank

The server stands in the top 69% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k21 Sep29 Sep6 Oct14 Oct21 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap16.4 daysbetween real wipes
Wipe-day peak0players, last three wipes
Thu 22 OctTue 6 Oct
01234+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 22 Oct, 17:217d ago 0 – running 0
Tue 6 Oct, 07:2323d ago 0 – 16.4 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 5: The map: Procedural Map.
Table 4: The server's published settings.
Address73.164.1.196:28315
Region–
Max players10
Group limit8, the default
Wipe schedule–
Last wipe22 Oct 2026, 17:21 UTC
Hostname–
First seen21 Sep 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and predicted wipe schedule [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 151 on average81/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average130/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average144/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average55/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 91 on average141/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average347/350

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does IRONHAVEN QA - staging (not public) have?

There is no region published for IRONHAVEN QA - staging (not public). Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 73.164.1.196:28315.

A.2What is the online status and reliability of IRONHAVEN QA - staging (not public)?

IRONHAVEN QA - staging (not public) is currently offline, with the last sighting 7 days 2 hours ago. Its uptime over the last full days (7 days) was 11%, with 18 of 168 hours online. The first record of it by Rust Statistics dates to 21 September 2026.

A.3What is the Rust version for IRONHAVEN QA - staging (not public)?

The version of Rust on IRONHAVEN QA - staging (not public) is network protocol 2634 and build 167584, and the operating system is Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.4On what cycle does IRONHAVEN QA - staging (not public) wipe?

There are not yet enough recorded wipes for IRONHAVEN QA - staging (not public) to reveal its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. 7 days 3 hours have passed since the current world was generated.

A.5What happens on IRONHAVEN QA - staging (not public) when wipe day arrives?

Recent wipes saw an average peak of 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Player count

A.6How does IRONHAVEN QA - staging (not public) compare with other Rust servers in the rankings?

Ranked by player hours across seven days, IRONHAVEN QA - staging (not public) holds #15,327, in the top 69% of all ranked servers.

A.7How would you characterise the player activity on IRONHAVEN QA - staging (not public)?

IRONHAVEN QA - staging (not public) is not online now; 7 days 2 hours have passed since it was last seen. Averaged across the last seven days, the population is 0 players.

Tags, lists

A.8What do the tags associated with IRONHAVEN QA - staging (not public) signify?

Tags from IRONHAVEN QA - staging (not public), read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp10 (Max players): 10 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167584 (Build): This server runs game build 167584; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^z (Modded): Modded listing: plugins or settings modify the game; ^y (Carbon): The plugin framework is Carbon. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.9Where can IRONHAVEN QA - staging (not public) be found among the Rust Statistics lists and filters?

The Rust Statistics lists that IRONHAVEN QA - staging (not public) fits are: Modded Rust servers. It appears 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, settings, map

A.10What are the settings and rules that govern IRONHAVEN QA - staging (not public)?

The name of IRONHAVEN QA - staging (not public) states no gather rate. No cap is given beyond the game's default of 8 players per group. The mode is survival, which means gathering, building and raiding, as the game is usually played. Players may raid and fight one another. It appears under Modded in the browser: the game is changed by plugins or settings. Carbon plugins are running. VAC, Valve's anti-cheat, is enabled.

A.11On which map does IRONHAVEN QA - staging (not public) take place?

On IRONHAVEN QA - staging (not public) the terrain is procedural, built by the game itself.

How to join

A.12What is the process for joining IRONHAVEN QA - staging (not public)?

Press F1 inside Rust to open the console and enter client.connect 73.164.1.196:28315. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp10,ptrak,$r?,v2634,gmrust,cs167584,ts8,^z,^y.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp10Max players. 10 slots are available.
ts8Group limit. The team cap is 8, which is the game default.
v2634Protocol. Your game must run protocol 2634 to connect.
cs167584Build. This server runs game build 167584.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. A region code has not been set.
Mods and access
^zModded. Modded listing: plugins or settings modify the game.
^yCarbon. The plugin framework is 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.