RUST METRICSFlight deck · live data
Data live Servers11,633 Players40,937 Populated2,826 Fresh wipes 3 h115 Scan5 min
‹ All servers63.226.81.119:28015
Offline Full Queue Fresh wipe Wipe due No query

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

Offline 63.226.81.119:28015 checked 24d ago

monthly wipes vanillaoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 16 32 48 64 PAX 0 /64

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,960top 71%
Last wipe27d agomonthly schedule
Next wipe6d 14hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

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.

REC 3

Rank

daily · 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.

PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 6d 14h. The force wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What wipe timing does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed follow?

From the force wipe, the next wipe of Secured by sentinel-id.com | Iron Reign: Kill or Be Killed is an estimate. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 27 days 21 hours ago the current world was made. Its tags carry a monthly wipe schedule.

Tag meanings

How should you read the tags on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed?

Tags published by Secured by sentinel-id.com | Iron Reign: Kill or Be Killed, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp64 (Max players): 64 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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

On Rust Metrics, Secured by sentinel-id.com | Iron Reign: Kill or Be Killed sits in these lists: Rust community servers: live readings and Vanilla Rust servers, live. Reading: server list filters. It comes up 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.

Population

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

Player hours over seven days put Secured by sentinel-id.com | Iron Reign: Kill or Be Killed at #15,960, in the top 71% of all ranked servers.

What player count does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed carry?

Status for Secured by sentinel-id.com | Iron Reign: Kill or Be Killed: offline. Last seen 24 days 9 hours ago.

Operator and location

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

No region comes from Secured by sentinel-id.com | Iron Reign: Kill or Be Killed. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 63.226.81.119:28015.

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

Rust network protocol 2634 and build 166652 on Windows is the build Secured by sentinel-id.com | Iron Reign: Kill or Be Killed runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed, and is it online?

Check: connection. Secured by sentinel-id.com | Iron Reign: Kill or Be Killed is offline at this moment. Last contact was 24 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 2 October 2026, recorded by Rust Metrics.

Settings and map

What rules does Secured by sentinel-id.com | Iron Reign: Kill or Be Killed enforce, and what are its settings?

Check: gather rate. The name Secured by sentinel-id.com | Iron Reign: Kill or Be Killed does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. Plugin count: Oxide. The server calls itself vanilla, with this meaning: the stock game: Facepunch's rates, kits and rules, unchanged. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Secured by sentinel-id.com | Iron Reign: Kill or Be Killed?

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

Connection

How can you get onto Secured by sentinel-id.com | Iron Reign: Kill or Be Killed?

Check: join. Open Rust, press F1, then enter client.connect 63.226.81.119:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp64
Max players 64 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Game build reading: 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.

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.