RUST METRICSFlight deck · live data
Data live Servers11,618 Players39,799 Populated2,961 Fresh wipes 3 h88 Scan5 min
‹ All servers146.158.110.159:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 146.158.110.159:28015 checked 16d ago

COM 1 · connect
Launch Rust and join

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,547top 71%
Last wipe16d 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 Sep5 Oct14 Oct19 Oct

Top 71% 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 gap14.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Mon 12 OctSat 19 SepSun 13 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 10:41 UTC16d ago 0 – running 1
Sat 19 Sep, 13:17 UTC39d ago 2 held half 22.9 days 0
Sun 13 Sep, 14:24 UTC45d ago 0 – 6 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 happens on nameserver when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 100% of its recent wipes.

What wipe timing does nameserver follow?

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 16 days 20 hours ago.

Tags

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; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167584 (Build): Build 167584; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from nameserver. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show nameserver?

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

Player count

What position does nameserver hold among Rust servers?

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

What player count does nameserver carry?

Reading for nameserver: offline at this moment; last seen 16 days 19 hours ago.

Operator and location

Which location does nameserver run from?

No region tag on nameserver. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 146.158.110.159:28015.

What Rust version is nameserver on?

Version check: Rust network protocol 2634 and build 167584 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?

Check: connection. nameserver is offline at this moment. Last contact was 16 days 19 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on nameserver?

Reading the name gives no gather rate for nameserver. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is nameserver on?

The game generates a procedural map for nameserver.

Connection

What do you do to join nameserver?

To join: start Rust, press F1 and type client.connect 146.158.110.159: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,cs167584,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.
cs167584
Build Build 167584.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.