RUST METRICSFlight deck · live data
Data live Servers11,623 Players39,438 Populated2,939 Fresh wipes 3 h88 Scan5 min
‹ All servers109.252.56.206:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 109.252.56.206:28015 checked 30d 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 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#14,084top 59%
Last wipe30d agono schedule published
Next wipe–no rhythm it keeps
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 Sep28 Sep30 Sep2 Oct4 Oct6 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.2 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Tue 29 SepMon 28 SepSat 26 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 29 Sep, 04:51 UTC30d ago 1 – running 0
Mon 28 Sep, 20:51 UTC30d ago 1 – 0.3 days 1
Sat 26 Sep, 20:27 UTC32d ago 1 held half 2 days 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

Reset cycle

What happens on nameserver when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

What wipe timing does nameserver follow?

There is no next wipe to predict: nameserver wipes at irregular times. 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 30 days 2 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): Slots: 15; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none 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 nameserver?

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

Occupancy

Where does nameserver sit in the rankings?

Player hours over seven days put nameserver at #14,084, in the top 59% of all ranked servers.

What player count does nameserver carry?

nameserver is not responding; status offline, last seen 30 days 2 hours ago.

Server

Where does nameserver sit?

No region comes from nameserver. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 109.252.56.206:28015.

What Rust version is nameserver on?

Reading: nameserver, Rust network protocol 2633 and build 165217, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on nameserver, and is it online?

Check: connection. nameserver is offline at this moment. Last contact was 30 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 26 September 2026.

Settings and map

How is nameserver configured, and what rules are in force?

Check: gather rate. The name nameserver does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.

How to join

How do you connect to nameserver?

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

PLACARDS

Server tags

what each one means

Published as mp15,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp15
Max players Slots: 15.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.