RUST METRICSFlight deck · live data
Data live Servers11,669 Players52,726 Populated3,296 Fresh wipes 3 h86 Scan5 min
‹ All servers178.177.237.49:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 178.177.237.49:28015 checked 24d ago

COM 1 · connect

Server instruments

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

Players now

13% 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#12,318top 54%
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
15k10k15k20k21 Sep24 Sep27 Sep4 Oct7 Oct10 Oct

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

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 2, 27 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 06:22 UTC26d ago 2 – running 2

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 2 players came at the busiest on its recent wipes. 27 hours after the wipe, the crowd peaked on the latest wipe.

How often does nameserver wipe, and when?

Its rhythm cannot be told from the wipes of nameserver on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 26 days 3 hours ago the current world was made.

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): Survival, as standard Rust plays it; mp15 (Max players): 15 slots in total; ts8 (Group limit): Default limit in force: 8 per team; 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): 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.

Where does nameserver appear in Rust Metrics lists and filters?

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

Player count

What position does nameserver hold among Rust servers?

Ranking for nameserver: #12,318 on seven-day player hours, top 54% of all ranked servers.

What player count does nameserver carry?

Status for nameserver: offline. Last seen 24 days 23 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.49:28015.

What Rust version is nameserver on?

Reading: nameserver, Rust network protocol 2634 and build 166494, Windows. To get in, your game needs the same protocol; Steam applies the update.

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

nameserver reports offline. The last reading came 24 days 23 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 21 September 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on nameserver?

No gather rate appears in the name: nameserver. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. 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

What do you do to join nameserver?

To join: start Rust, press F1 and type client.connect 178.177.237.49: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 15 slots in total.
ts8
Group limit Default limit in force: 8 per team.
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 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.