RUST METRICSFlight deck · live data
Data live Servers11,601 Players32,197 Populated2,849 Fresh wipes 3 h68 Scan5 min
‹ All servers178.177.237.5:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 178.177.237.5: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,980top 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
15k10k15k20k23 Sep26 Sep29 Sep7 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 UTC25d 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

Wipe timing

How often does nameserver wipe, and when?

Its rhythm cannot be told from the wipes of nameserver on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 25 days 22 hours ago.

Tags

How should you read the tags on nameserver?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp15 (Max players): The server holds 15 slots; 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): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from nameserver. 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?

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?

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

What player count does nameserver carry?

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

Server

Where does nameserver sit?

No region tag on nameserver. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 178.177.237.5: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.

How reliable is nameserver, and is it online now?

nameserver reports offline. The last reading came 21 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 23 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. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on nameserver?

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 178.177.237.5: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,cs166494,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp15
Max players The server holds 15 slots.
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 Network layer: RakNet, the standard for the game.
$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.