The count
Live coverage · Rust server
Secured by sentinel-id.com | Iron Reign: Kill or Be Killed
Offline Secured by sentinel-id.com | Iron Reign: Kill or Be Killed is not on the server list right now. The figures below are from when it was last seen, 24d ago.
Key points
- 0 of 64 players are on at the last check, 0% full.
- Over the last seven days it averages 0 players.
- It ranks #15,960, the top 71% of all ranked servers.
- The current map has been up 27d 16h, since Friday 2 October, 06:28 UTC, on a monthly schedule.
- The next wipe is expected Thursday 5 November at 19:00 UTC, in 6d 19h, with the force wipe.
Live coverage
newest first · every post is a reading of this serverEmbedded chart
Players on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
How the server is running
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. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Rank #15,960 today
Rank
daily · 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Next wipe in 6d 19h
Next wipe Thursday 5 November, 19:00 UTC, in 6d 19h. The force wipe
Wipes
newest firstNo wipe seen yet
This server has not put up a new map since the desk started watching it.
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageWipe schedule
How often does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed wipe, and at what times?
An estimate from the force wipe gives Secured by sentinel-id.com | Iron Reign: Kill or Be Killed's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe and one that hits every Rust server. 27 days 16 hours have passed since this world was generated. A monthly wipe schedule is published in its tags.
Lists and tags
Which Rust Live Stats filters and lists does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed show up in?
These are the Rust Live Stats lists Secured by sentinel-id.com | Iron Reign: Kill or Be Killed fits: Live Rust community servers and Vanilla Rust servers, live. You will find it on the server list under Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Monthly ^m, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
What meaning do the tags on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed carry?
The server browser reads gmrust (Game mode): Standard survival, in the Rust style; mp64 (Max players): The slot count is 64; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2634 (Protocol): Join only if your game is on protocol 2634; cs166652 (Build): This server runs game build 166652; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): The server sets no region code; ^m (Monthly): A single monthly wipe, set by Facepunch's force wipe; ^v (Vanilla): The rates, kits and rules are unchanged from what Facepunch ships; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server, which Secured by sentinel-id.com | Iron Reign: Kill or Be Killed publishes. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.
Player counts
What is the current population on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed?
Secured by sentinel-id.com | Iron Reign: Kill or Be Killed reads offline at the moment; the last sighting was 24 days 4 hours ago.
How does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed compare with other Rust servers in the rankings?
Ranked by seven-day player hours, Secured by sentinel-id.com | Iron Reign: Kill or Be Killed is #15,960, placing it in the top 71% of ranked servers.
Rules and settings
What rules does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed enforce, and which settings does it use?
No gather rate appears in the name Secured by sentinel-id.com | Iron Reign: Kill or Be Killed. No custom limit is set, so groups hold the default 8 players. survival is the mode, with the standard game: gather, build, raid. You can raid and fight other players. Community is its browser category. The plugin load is Oxide. Vanilla is its own label: the rates, kits and rules are unchanged from what Facepunch ships. Anti-cheat: VAC from Valve is enabled.
Can you tell me the map for Secured by sentinel-id.com | Iron Reign: Kill or Be Killed?
The map on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed is procedural, made by the game itself.
Server facts
Which region is Secured by sentinel-id.com | Iron Reign: Kill or Be Killed hosted in?
No region is published by Secured by sentinel-id.com | Iron Reign: Kill or Be Killed. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. You can reach it at 63.226.81.119:28015.
What version of Rust is running on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed?
The setup on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed is Rust network protocol 2634 and build 166652 with Windows. Steam updates it for you, but your game needs the same protocol to join.
Does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed stay online, and is it up right now?
At the time of this update, Secured by sentinel-id.com | Iron Reign: Kill or Be Killed is down, last seen 24 days 4 hours ago. It was online for 0 of 168 hours in the last 7 full days, or 0% of the time. On 2 October 2026, Rust Live Stats saw it for the first time.
Getting on
What steps connect you to Secured by sentinel-id.com | Iron Reign: Kill or Be Killed?
Enter client.connect 63.226.81.119:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.