RUST METRICSFlight deck · live data
Data live Servers11,853 Players82,944 Populated3,958 Fresh wipes 3 h166 Scan5 min
‹ All servers176.59.145.83:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 176.59.145.83:28015 checked 7d 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,385top 70%
Last wipe13d agono schedule published
Next wipe–no wipe 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 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 wipe timing does nameserver follow?

The rhythm of nameserver's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 13 days 5 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): The game mode is plain Rust survival; mp15 (Max players): 15 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show nameserver?

On Rust Metrics, nameserver sits in these lists: 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; Last wipe: In the last 2 weeks.

Occupancy

Where does nameserver sit in the rankings?

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

How full does nameserver get?

Status for nameserver: offline. Last seen 7 days 5 hours ago. Seven-day reading: 0 players on average.

Operator and location

Where does nameserver sit?

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 176.59.145.83:28015.

What Rust version is nameserver on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by nameserver. To get in, your game needs the same protocol; Steam applies the update.

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

Check: connection. nameserver is offline at this moment. Last contact was 7 days 5 hours ago. Reading: 0% uptime over the last 6 full days. It was up 0 of 144 hours. Check: first contact. Rust Metrics logged it on 20 October 2026.

Map and rules

How is nameserver configured, and what rules are in force?

Check: gather rate. The name nameserver does not state one. 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. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is nameserver on?

The game generates a procedural map for nameserver.

Join

What do you do to join nameserver?

Press F1 in Rust and enter client.connect 176.59.145.83: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,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp15
Max players 15 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 167781.
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.