RUST METRICSFlight deck · live data
Data live Servers11,814 Players74,934 Populated3,774 Fresh wipes 3 h145 Scan5 min
‹ All servers37.29.41.7:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 37.29.41.7: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,998top 71%
Last wipe25d 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 Sep25 Sep29 Sep4 Oct8 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.

usual gap6.3 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 3, 10 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 06:22 UTC25d ago 3 – running 0
Fri 25 Sep, 23:23 UTC31d ago 2 held half 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

Wipe schedule

What happens on nameserver when wipe day comes?

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

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 it runs now was made 25 days 15 hours ago.

Lists and filters

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): Slots: 15; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166494 (Build): Game build reading: 166494; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. 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?

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: #15,998 on seven-day player hours, top 71% of all ranked servers.

How full does nameserver get?

nameserver is not responding; status offline, last seen 21 days 4 hours ago.

Operator and location

What location is nameserver hosted in?

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

What Rust version is nameserver on?

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

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

nameserver reports offline. The last reading came 21 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 19 September 2026.

Settings and map

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. The mode is survival. Note the following: gather, build and raid, as the game normally runs. 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.

Which map is live on nameserver?

The game generates a procedural map for nameserver.

How to join

How can you get onto nameserver?

Check: join. Open Rust, press F1, then enter client.connect 37.29.41.7: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?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp15
Max players Slots: 15.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166494
Build Game build reading: 166494.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.