RUST METRICSFlight deck · live data
Data live Servers11,750 Players60,289 Populated3,494 Fresh wipes 3 h126 Scan5 min
‹ All servers212.32.192.252:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 212.32.192.252:28015 checked 20d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 4 6 8 PAX 0 /8

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#14,871top 67%
Last wipe25d 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
15k10k15k20k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

Top 67% 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 gap2.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctWed 30 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
Fri 2 Oct, 01:36 UTC25d ago 1 – running 1
Wed 30 Sep, 09:58 UTC27d ago 1 – 1.7 days 0
Sat 26 Sep, 16:32 UTC31d ago – – 3.7 days 1

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 should you expect from wipe day on nameserver?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

How often does nameserver wipe, and when?

There is no next wipe to predict: nameserver wipes at irregular times. 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 25 days 21 hours ago.

Tags

How should you read the tags on nameserver?

These are the tags nameserver publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp8 (Max players): Slots: 8; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166494 (Build): Game build reading: 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does nameserver appear in Rust Metrics lists and filters?

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

Occupancy

What position does nameserver hold among Rust servers?

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

How full does nameserver get?

Reading for nameserver: offline at this moment; last seen 20 days 2 hours ago.

Server

Where does nameserver sit?

No region tag on nameserver. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 212.32.192.252:28015.

What Rust version is nameserver on?

Version check: Rust network protocol 2634 and build 166494 on Windows, run by nameserver. Matching protocol is required to join. Let Steam update your game.

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

nameserver reports offline. The last reading came 20 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 16 September 2026, recorded by Rust Metrics.

Map and rules

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. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is nameserver on?

Check: map. Procedural, generated by the game, on nameserver.

Connection

What do you do to join nameserver?

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp8
Max players Slots: 8.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166494
Build Game build reading: 166494.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.