RUST METRICSFlight deck · live data
Data live Servers11,711 Players67,607 Populated3,578 Fresh wipes 3 h107 Scan5 min
‹ All servers46.53.229.82:28015
Offline Full Queue Fresh wipe Wipe due No query

ALIVE4DEATH

Offline 46.53.229.82:28015 checked 19d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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,842top 72%
Last wipe19d agono schedule published
Next wipe–too few wipes seen yet
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
15k10k15k20k8 Oct9 Oct11 Oct12 Oct14 Oct15 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 23:14 UTC19d ago 0 – running 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.

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 happens on ALIVE4DEATH when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does ALIVE4DEATH follow?

Its rhythm cannot be told from the wipes of ALIVE4DEATH on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 19 days 12 hours ago the current world was made.

Tags

Which tags does ALIVE4DEATH carry, and what do they mean?

These are the tags ALIVE4DEATH publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167231 (Build): Game build reading: 167231; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show ALIVE4DEATH?

Rust Metrics lists featuring ALIVE4DEATH: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does ALIVE4DEATH hold among Rust servers?

Player hours over seven days put ALIVE4DEATH at #15,842, in the top 72% of all ranked servers.

What is the population on ALIVE4DEATH?

Status for ALIVE4DEATH: offline. Last seen 19 days 12 hours ago.

Server details

Where does ALIVE4DEATH sit?

No region tag on ALIVE4DEATH. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 46.53.229.82:28015.

What Rust version is ALIVE4DEATH on?

Rust network protocol 2634 and build 167231 on Windows is the build ALIVE4DEATH runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is ALIVE4DEATH, and is it online now?

Reading: offline. ALIVE4DEATH last answered 19 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 8 October 2026.

Settings and map

What rules does ALIVE4DEATH enforce, and what are its settings?

Check: gather rate. The name ALIVE4DEATH does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

Which map is live on ALIVE4DEATH?

Check: map. Procedural, generated by the game, on ALIVE4DEATH.

Connection

How do you connect to ALIVE4DEATH?

To join: start Rust, press F1 and type client.connect 46.53.229.82:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167231,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players Slots: 100.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167231
Build Game build reading: 167231.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

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.