RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h4 Scan5 min
‹ All servers37.29.88.10:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 37.29.88.10:28015 checked 24d 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#12,029top 53%
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
15k10k15k20k25 Sep28 Sep1 Oct5 Oct8 Oct11 Oct

Top 53% 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 gap6.3 daysbetween real wipes
wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctFri 25 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 06:22 UTC26d ago 2 – running 0
Fri 25 Sep, 23:23 UTC32d ago – – 6.3 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 should you expect from wipe day on nameserver?

The busiest point of its recent wipes drew 2 players on average. 27 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does nameserver follow?

To tell the rhythm of nameserver, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 26 days 13 hours ago.

Tags

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

These are the tags nameserver publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp15 (Max players): Slots: 15; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166494 (Build): Game build reading: 166494; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does nameserver appear in Rust Metrics lists and filters?

On Rust Metrics, nameserver sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does nameserver hold among Rust servers?

Ranking for nameserver: #12,029 on seven-day player hours, top 53% of all ranked servers.

How full does nameserver get?

nameserver is not responding; status offline, last seen 24 days 6 hours ago.

Operator and location

Where does nameserver sit?

No region comes from nameserver. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 37.29.88.10:28015.

What Rust version is nameserver on?

Rust network protocol 2634 and build 166494 on Windows is the build nameserver runs. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: offline. nameserver last answered 24 days 6 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 25 September 2026, recorded by Rust Metrics.

Rules and settings

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

Reading the name gives no gather rate for nameserver. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on nameserver?

The game generates a procedural map for nameserver.

Join

What do you do to join nameserver?

Press F1 in Rust and enter client.connect 37.29.88.10: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?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp15
Max players Slots: 15.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166494
Build Game build reading: 166494.
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.