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

nameserver

Offline 37.29.41.8:28015 checked 21d 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,986top 71%
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
15k10k15k20k20 Sep23 Sep27 Sep6 Oct10 Oct13 Oct

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

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 06:22 UTC26d ago – – running 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

When does nameserver wipe?

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

How should you read the tags on nameserver?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; 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): The server runs game build 166494; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from nameserver. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does nameserver appear in Rust Metrics lists and filters?

These Rust Metrics lists carry nameserver: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does nameserver sit in the rankings?

Player hours over seven days put nameserver at #15,986, in the top 71% of all ranked servers.

What is the population on nameserver?

Status for nameserver: offline. Last seen 21 days 23 hours ago.

Operator and location

What location is nameserver hosted in?

Reading: location. nameserver gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 37.29.41.8:28015.

What Rust version is nameserver on?

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

How reliable is nameserver, and is it online now?

nameserver reports offline. The last reading came 21 days 23 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 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. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on nameserver?

The game generates a procedural map for nameserver.

Connection

How can you get onto nameserver?

Press F1 in Rust and enter client.connect 37.29.41.8: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 The game mode is plain Rust survival.
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 The server runs game build 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.