RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h7 Scan5 min
‹ All servers79.177.159.97:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 79.177.159.97:28015 checked 27d ago

COM 1 · connect

Server instruments

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

Players now

7% 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,281top 60%
Last wipe28d 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
15k10k15k20k21 Sep24 Sep28 Sep1 Oct5 Oct8 Oct

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

The first 48 hours of its last wipes

Wed 30 SepTue 22 SepMon 21 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
Wed 30 Sep, 18:20 UTC28d ago 1 – running 1
Tue 22 Sep, 08:55 UTC36d ago 1 – 8.4 days 1
Mon 21 Sep, 16:16 UTC37d ago 1 – 0.7 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

Reset cycle

What should you expect from wipe day on nameserver?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does nameserver follow?

No next wipe can be predicted for nameserver, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 28 days 1 hours ago the current world was made.

Lists and filters

How should you read the tags on nameserver?

Check: tags. The game's server browser reads 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; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from nameserver. 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?

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.

Player count

Where does nameserver sit in the rankings?

Ranking for nameserver: #14,281 on seven-day player hours, top 60% of all ranked servers.

What player count does nameserver carry?

Status for nameserver: offline. Last seen 27 days 9 hours ago.

Server

Where does nameserver sit?

Reading: location. nameserver gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 79.177.159.97:28015.

What Rust version is nameserver on?

Rust network protocol 2633 and build 165217 on Windows is the build nameserver runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on nameserver, and is it online?

Reading: offline. nameserver last answered 27 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 21 September 2026, recorded by Rust Metrics.

Settings and map

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: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

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 79.177.159.97: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?,v2633,gmrust,cs165217,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.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Game build reading: 165217.
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.