RUST METRICSFlight deck · live data
Data live Servers11,684 Players38,205 Populated2,919 Fresh wipes 3 h95 Scan5 min
‹ All servers87.250.197.134:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 87.250.197.134:28015 checked 4d 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 avg7-day peak
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 average1peak 1
Rank#12,835top 58%
Last wipe5d 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
15k10k15k20k4 Oct9 Oct14 Oct19 Oct24 Oct29 Oct

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

usual gap19.3 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 23 OctSun 4 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 16:17 UTC5d ago 1 – running 0
Sun 4 Oct, 09:35 UTC24d ago 1 held half 19.3 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

Wipe schedule

What should you expect from wipe day on nameserver?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 19 hours. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.

What wipe timing does nameserver follow?

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. The world in play was created 5 days 10 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): 15 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from nameserver. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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; Last wipe: In the last week.

Occupancy

Where does nameserver sit in the rankings?

Player hours over seven days put nameserver at #12,835, in the top 58% of all ranked servers.

How full does nameserver get?

nameserver is not responding; status offline, last seen 4 days 7 hours ago. Check: players over seven days. Average 1, peak 1.

Server details

Which location does nameserver run from?

Reading: location. nameserver gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 87.250.197.134:28015.

What Rust version is nameserver on?

Version check: Rust network protocol 2635 and build 168909 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 4 days 7 hours ago. Reading: 1% uptime over the last 7 full days. It was up 2 of 168 hours. The first sighting on Rust Metrics was 4 October 2026.

Settings and map

What settings and rules apply on nameserver?

Check: gather rate. The name nameserver does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on nameserver?

Check: map. Procedural, generated by the game, on nameserver.

How to join

How can you get onto nameserver?

To join: start Rust, press F1 and type client.connect 87.250.197.134: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?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp15
Max players 15 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.