RUST METRICSFlight deck · live data
Data live Servers11,752 Players57,724 Populated3,422 Fresh wipes 3 h129 Scan5 min
‹ All servers79.173.248.242:28015
Offline Full Queue Fresh wipe Wipe due No query

Mortal Server

Offline 79.173.248.242:28015 checked 7d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

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,409top 69%
Last wipe26d 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
15k10k15k20k26 Sep2 Oct8 Oct15 Oct21 Oct27 Oct

Top 69% 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 peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 15:08 UTC26d ago 1 – running 1

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 timing

What should you expect from wipe day on Mortal Server?

An average of 1 players came at the busiest on its recent wipes. 22 hours after the wipe, the crowd peaked on the latest wipe.

How often does Mortal Server wipe, and when?

Its rhythm cannot be told from the wipes of Mortal Server on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 26 days 7 hours ago.

Tag meanings

Which tags does Mortal Server carry, and what do they mean?

These are the tags Mortal Server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Mortal Server?

Rust Metrics lists featuring Mortal Server: 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.

Population

What position does Mortal Server hold among Rust servers?

Player hours over seven days put Mortal Server at #15,409, in the top 69% of all ranked servers.

How full does Mortal Server get?

Status for Mortal Server: offline. Last seen 7 days 22 hours ago.

Operator and location

Which location does Mortal Server run from?

No region tag on Mortal Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 79.173.248.242:28015.

What Rust version is Mortal Server on?

Reading: Mortal Server, Rust network protocol 2634 and build 167781, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is Mortal Server up, and how often does it stay up?

Check: connection. Mortal Server is offline at this moment. Last contact was 7 days 22 hours ago. Reading: 1% uptime over the last 7 full days. It was up 1 of 168 hours. The first sighting on Rust Metrics was 26 September 2026.

Settings and map

How is Mortal Server configured, and what rules are in force?

Check: gather rate. The name Mortal Server does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Mortal Server?

Procedural map on Mortal Server, made by the game's generator.

Connection

How do you connect to Mortal Server?

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

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players Slots: 500.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.