RUST METRICSFlight deck · live data
Data live Servers11,744 Players74,144 Populated3,692 Fresh wipes 3 h138 Scan5 min
‹ All servers159.224.231.48:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 159.224.231.48:28015 checked 3h ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 4 8 11 15 PAX 1 /15

Players now

7% full 7-day avg7-day peak
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 average1peak 1
Rank#6,979top 31%
Last wipe2d agono schedule published
Next wipe–too few wipes seen yet
Memory–48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75101:0003:0004:0006:0007:0009:00

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
15k10k15k20k19 Oct21 Oct23 Oct24 Oct26 Oct28 Oct

Top 31% 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.

usual gap5.2 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Mon 26 OctWed 21 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 07:25 UTC2d ago 1 – running 1
Wed 21 Oct, 02:22 UTC7d ago 0 – – 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 nameserver?

An average of 0 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 42 hours.

What wipe timing does nameserver follow?

Its rhythm cannot be told from the wipes of nameserver 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. The world it runs now was made 2 days 5 hours ago.

Lists and filters

How should you read the tags on nameserver?

Tags published by nameserver, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp15 (Max players): The server holds 15 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. 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 nameserver?

On Rust Metrics, nameserver sits in these lists: 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; Last wipe: In the last 3 days.

Occupancy

What position does nameserver hold among Rust servers?

Ranking for nameserver: #6,979 on seven-day player hours, top 31% of all ranked servers.

What is the population on nameserver?

Status for nameserver: offline. Last seen 3 hours ago. Seven-day check: 1 players on average. Peak reading: 1. The last 48 hours peaked at 02:00 UTC, averaging 1 players at that hour.

Server

Where does nameserver sit?

No region tag on nameserver. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 159.224.231.48:28015.

What Rust version is nameserver on?

Reading: nameserver, Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is nameserver up, and how often does it stay up?

Check: connection. nameserver is offline at this moment. Last contact was 3 hours ago. Reading: 5% uptime over the last 7 full days. It was up 9 of 168 hours. The first sighting on Rust Metrics was 19 October 2026.

Rules and settings

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

Reading the name gives no gather rate for nameserver. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is nameserver on?

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

How to join

How can you get onto nameserver?

Press F1 in Rust and enter client.connect 159.224.231.48:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp15,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp15
Max players The server holds 15 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.