RUST METRICSFlight deck · live data
Data live Servers11,682 Players55,436 Populated3,376 Fresh wipes 3 h102 Scan5 min
‹ All servers37.29.41.16:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 37.29.41.16:28015 checked 8d ago

COM 1 · connect

Server instruments

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

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,345top 70%
Last wipe12d 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
15k10k15k20k24 Sep29 Sep3 Oct8 Oct22 Oct27 Oct

Top 70% 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 gap10.2 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak3players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 07:13 UTC12d ago – – running 3
Fri 2 Oct, 06:22 UTC26d ago 3 – 14 days 3
Fri 25 Sep, 23:23 UTC32d ago 3 held half 6.3 days 3

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

The busiest point of its recent wipes drew 3 players on average. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

When does nameserver wipe?

No next wipe can be predicted for nameserver, which wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 12 days 3 hours ago the current world was made.

Tags

How should you read the tags on nameserver?

These are the tags nameserver publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp15 (Max players): The server holds 15 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. 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 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 2 weeks.

Player count

Where does nameserver sit in the rankings?

Ranking for nameserver: #15,345 on seven-day player hours, top 70% of all ranked servers.

How full does nameserver get?

nameserver is not responding; status offline, last seen 8 days 5 hours ago.

Server details

Where does nameserver sit?

Reading: location. nameserver gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 37.29.41.16:28015.

What Rust version is nameserver on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by nameserver. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is nameserver, and is it online now?

Reading: offline. nameserver last answered 8 days 5 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 24 September 2026.

Map and rules

What settings and rules apply on nameserver?

Check: gather rate. The name nameserver does not state one. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC off, Valve's system.

What map is nameserver on?

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

Join

What do you do to join nameserver?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp15
Max players The server holds 15 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.