Rust StatisticsWorking papers on every public Rust server · 69,100 players now

Secured by sentinel-id.com | Iron Reign: Kill or Be Killed

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 23d ago · 63.226.81.119:28015

Abstract

We describe the public Rust server Secured by sentinel-id.com | Iron Reign: Kill or Be Killed, reached at 63.226.81.119:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,960 of all servers, the top 71%. It last wiped 27d ago on a published monthly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.

Keywordsmonthly wipes vanilla oxide

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/640% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,960top 71%
Last wipe27d agomonthly schedule
Next wipe37d 6hThu 5 Nov, 19:00 UTCfw

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 71% 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
15k10k15k20k2 Oct4 Oct6 Oct8 Oct10 Oct12 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

The next wipe is expected Thursday 5 November, 19:00 UTC, in 7d 6h. The force wipe.

5.2History

Table 2: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
No wipe seen yet.

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 4: The map: Procedural Map.
Table 3: The server's published settings.
Address63.226.81.119:28015
Region–
Max players64
Group limit8, the default
Wipe schedulemonthly
Last wipe2 Oct 2026, 06:28 UTC
Hostname–
First seen2 Oct 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 rust community servers listed [2], 1x rust servers [3] and predicted wipe schedule [4].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average423/450
Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 215 on average252/300
[EU East] Facepunch 4EU · groups of 8+ · monthly · 170 on average91/350
[EU] Facepunch 1EU · groups of 8+ · monthly · 161 on average145/400
Rustopia.gg - US LargeNA · groups of 16+ · monthly · 129 on average46/200
Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 127 on average82/100

Appendix AQuick answers

From the figures on this page.

Server details

A.1What location does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed have?

No region is published by Secured by sentinel-id.com | Iron Reign: Kill or Be Killed. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 63.226.81.119:28015 is its address.

A.2What is the reliability of Secured by sentinel-id.com | Iron Reign: Kill or Be Killed, and is it online?

At the present moment, Secured by sentinel-id.com | Iron Reign: Kill or Be Killed is offline; it was last seen 23 days 18 hours ago. The server was up 0% of the time over the last 7 full days, 0 of 168 hours. Its first appearance in Rust Statistics's records is 2 October 2026.

A.3What version of Rust is run on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed?

The version of Rust on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed is network protocol 2634 and build 166652, and the operating system is Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.4On what cycle does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed wipe?

The estimate of Secured by sentinel-id.com | Iron Reign: Kill or Be Killed's next wipe comes from the force wipe. On Thursday 5 November at 19:00 UTC the force wipe occurs, and that is when every Rust server, including this one, next wipes. 27 days 6 hours have passed since the current world was generated. The tags show that the server wipes monthly.

Player count

A.5What is the rank of Secured by sentinel-id.com | Iron Reign: Kill or Be Killed among Rust servers?

The seven-day player-hours ranking puts Secured by sentinel-id.com | Iron Reign: Kill or Be Killed at #15,960, within the top 71% of ranked servers.

A.6At what level does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed operate in terms of players?

Secured by sentinel-id.com | Iron Reign: Kill or Be Killed is not online now; 23 days 18 hours have passed since it was last seen.

Tags and filters

A.7What do the tags associated with Secured by sentinel-id.com | Iron Reign: Kill or Be Killed signify?

Tags from Secured by sentinel-id.com | Iron Reign: Kill or Be Killed, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp64 (Max players): The slot count is 64; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Facepunch's force wipe sets the schedule: wipes take place once a month; ^v (Vanilla): Rates, kits and rules are unchanged from the game Facepunch ships; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.8Where can Secured by sentinel-id.com | Iron Reign: Kill or Be Killed be found among the Rust Statistics lists and filters?

Rust community servers, measured and Vanilla Rust servers are the Rust Statistics lists that Secured by sentinel-id.com | Iron Reign: Kill or Be Killed fits. These filters on the server list return it: 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.

Rules, settings, map

A.9Which settings and rules are in force on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed?

No gather rate appears in the name of Secured by sentinel-id.com | Iron Reign: Kill or Be Killed. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; the standard mode, in which you gather, build and raid. Players may raid and fight one another. Community is its category in the server browser. The plugin count is Oxide. The server's own description is vanilla: rates, kits and rules are unchanged from the game Facepunch ships. The server has VAC on, Valve's anti-cheat.

A.10On which map does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed take place?

On Secured by sentinel-id.com | Iron Reign: Kill or Be Killed the terrain is procedural, built by the game itself.

Connection

A.11What steps are required to join Secured by sentinel-id.com | Iron Reign: Kill or Be Killed?

Enter client.connect 63.226.81.119:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp64,ptrak,$r?,v2634,^m,^v,gmrust,cs166652,ts8,^o.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp64Max players. The slot count is 64.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2634Protocol. The game protocol is 2634; your client must match it to join.
cs166652Build. The game build is 166652.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. No region code is set.
Wipe schedule
^mMonthly. Facepunch's force wipe sets the schedule: wipes take place once a month.
Difficulty
^vVanilla. Rates, kits and rules are unchanged from the game Facepunch ships.
Mods and access
^oOxide. Oxide (uMod), a plugin framework, runs on this 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Rust community servers listed. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. 1x rust servers. ruststatistics.org/top-vanilla-rust-servers.
  4. [4]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.