Offline 73.164.1.196:28315 checked 7d ago
IRONHAVEN QA - staging (not public)
Connect
srv = rust.server("73.164.1.196:28317")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 17:21 UTC7d ago | 0 | NaN | running | 0 |
| 1 | Tue 6 Oct, 07:23 UTC23d ago | 0 | NaN | 16.4 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 73.164.1.196:28315
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 17:21 UTC
- hostname
- –
- first seen
- 21 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 113/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 188/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 72/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 208/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 349/350 |
Quick answers
From the figures on this page.
Player counts
How does IRONHAVEN QA - staging (not public) compare in the rankings?
Player hours over seven days put IRONHAVEN QA - staging (not public) at #15,327, in the top 69% of the ranked set.
What population does IRONHAVEN QA - staging (not public) carry?
Offline now for IRONHAVEN QA - staging (not public), with the last sample 7 days 1 hours ago. Over the last seven days it averaged 0 players.
About the server
What is the Rust version on IRONHAVEN QA - staging (not public)?
Version Rust network protocol 2634 and build 167584 on Linux is reported by IRONHAVEN QA - staging (not public). Steam updates your game for you, but the protocol must match to join.
How reliable is IRONHAVEN QA - staging (not public), and is it up?
IRONHAVEN QA - staging (not public) is offline at this refresh; the last response came 7 days 1 hours ago. Over the last 7 full days the hours up number 18 of 168, 11%. Rust Data logged it first on 21 September 2026.
Where does IRONHAVEN QA - staging (not public) sit?
No region is published by IRONHAVEN QA - staging (not public). Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 73.164.1.196:28315 is its address.
Rules, settings, map
Which settings and rules does IRONHAVEN QA - staging (not public) run?
You will not find a gather rate in the string IRONHAVEN QA - staging (not public). No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. VAC is running: Valve's anti-cheat is on.
What is the map on IRONHAVEN QA - staging (not public)?
The game generates its map: procedural, on IRONHAVEN QA - staging (not public).
Wipe schedule
When does IRONHAVEN QA - staging (not public) wipe, and on what schedule?
Too few wipes are on record for IRONHAVEN QA - staging (not public) to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 7 days 1 hours ago.
On IRONHAVEN QA - staging (not public), what happens on wipe day?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.
Tags and filters
Where does IRONHAVEN QA - staging (not public) appear among Rust Data lists and filters?
On Rust Data, IRONHAVEN QA - staging (not public) appears in these lists: Modded Rust servers. These filters bring it up 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.
How should you read the server tags on IRONHAVEN QA - staging (not public)?
The game's server browser reads these tags from IRONHAVEN QA - staging (not public): gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167584 (Build): The server runs build 167584; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join IRONHAVEN QA - staging (not public)?
The manual route: launch Rust, F1, then client.connect 73.164.1.196:28315. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.