Rust Data

rustdata.spaceservers63.226.81.119:28018.ipynb

Run all rust-data · live

‹ All servers

Offline 63.226.81.119:28015 checked 23d ago

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

monthly wipes vanillaoxide

Connect

srv = rust.server("63.226.81.119:28018")
print(srv.connect_command)

Right now

srv.summary()
players now 0/64 # 0% full
7-day average 0 # peak –
rank #15,960 # top 71%
last wipe 27d ago # monthly schedule
next wipe 7d 3h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k2 Oct4 Oct6 Oct8 Oct10 Oct12 Oct

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

Wipe schedule

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h. # The force wipe

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · 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. 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
63.226.81.119:28015
region
–
max players
64
group limit
8, the default
wipe schedule
monthly
last wipe
2 Oct 2026, 06:28 UTC
hostname
–
first seen
2 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average441/475
1Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 214 on average258/300
2[EU East] Facepunch 4EU · groups of 8+ · monthly · 166 on average114/350
3[EU] Facepunch 1EU · groups of 8+ · monthly · 161 on average160/400
4Rustopia.gg - US LargeNA · groups of 16+ · monthly · 128 on average59/200
5Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 126 on average91/125

Quick answers

From the figures on this page.

Population

How does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed compare in the rankings?

Rank #15,960 on seven-day player hours for Secured by sentinel-id.com | Iron Reign: Kill or Be Killed, within the top 71% of all ranked servers.

How full does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed run?

Offline now for Secured by sentinel-id.com | Iron Reign: Kill or Be Killed, with the last sample 23 days 20 hours ago.

Server facts

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

Version Rust network protocol 2634 and build 166652 on Windows is reported by Secured by sentinel-id.com | Iron Reign: Kill or Be Killed. Joining needs the same protocol on your game; Steam handles the update.

How reliable is Secured by sentinel-id.com | Iron Reign: Kill or Be Killed, and is it online now?

The latest sample has Secured by sentinel-id.com | Iron Reign: Kill or Be Killed offline, with a last sighting 23 days 20 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 2 October 2026.

In which location is Secured by sentinel-id.com | Iron Reign: Kill or Be Killed hosted?

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 Data shows; the machine's actual location is not looked up. You can reach it at 63.226.81.119:28015.

Map and rules

Which settings and rules does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed run?

You will not find a gather rate in the string Secured by sentinel-id.com | Iron Reign: Kill or Be Killed. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. It is a community server, and the browser files it under Community. Plugins installed: Oxide. Its own label is vanilla: no changed rates, kits or rules: the game as Facepunch ships it. VAC is running: Valve's anti-cheat is on.

Which map has Secured by sentinel-id.com | Iron Reign: Kill or Be Killed selected?

The game generates its map: procedural, on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed.

Wipes and dates

When does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed wipe, and how often?

The next wipe for Secured by sentinel-id.com | Iron Reign: Kill or Be Killed is an estimate, drawn from the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 27 days 8 hours ago. Its tags carry a monthly wipe schedule.

Tags and filters

Which Rust Data filters and lists contain Secured by sentinel-id.com | Iron Reign: Kill or Be Killed?

These Rust Data lists include Secured by sentinel-id.com | Iron Reign: Kill or Be Killed: Rust community servers, unfiltered and Vanilla Rust servers. These filters bring it up on the server list: 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.

Which meanings do the tags on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed hold?

Read by the game's server browser, the tags Secured by sentinel-id.com | Iron Reign: Kill or Be Killed publishes are: gmrust (Game mode): Rust survival in its standard form; mp64 (Max players): 64 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Build number: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): The plugin framework in use is Oxide (uMod). The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

How can I connect to Secured by sentinel-id.com | Iron Reign: Kill or Be Killed?

The manual route: launch Rust, F1, then client.connect 63.226.81.119:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp64,ptrak,$r?,v2634,^m,^v,gmrust,cs166652,ts8,^o

Game

gmrust
Game mode Rust survival in its standard form.
mp64
Max players 64 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs166652
Build Build number: 166652.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Wipes follow the monthly force wipe from Facepunch.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).

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.

Rust Data 90,153 players 11,869 servers online