RUST METRICSFlight deck · live data
Data live Servers11,713 Players47,275 Populated3,205 Fresh wipes 3 h100 Scan5 min
‹ All servers193.35.51.86:28015
Offline Full Queue Fresh wipe Wipe due No query

namserver

Offline 193.35.51.86:28015 checked 18d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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#13,613top 62%
Last wipe18d 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
15k10k15k20k7 Oct9 Oct11 Oct13 Oct15 Oct17 Oct

Top 62% 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 gap1.7 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sat 10 OctThu 8 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 09:32 UTC18d ago 1 – running 0
Thu 8 Oct, 16:22 UTC20d ago 1 – 1.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

Wipe schedule

What should you expect from wipe day on namserver?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does namserver wipe, and when?

Its rhythm cannot be told from the wipes of namserver on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 18 days 14 hours ago.

Tags

How should you read the tags on namserver?

These are the tags namserver publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167231 (Build): The server runs game build 167231; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. 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 namserver?

These Rust Metrics lists carry namserver: 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 namserver hold among Rust servers?

Player hours over seven days put namserver at #13,613, in the top 62% of all ranked servers.

How full does namserver get?

Status for namserver: offline. Last seen 18 days 12 hours ago.

Operator and location

Where does namserver sit?

No region comes from namserver. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 193.35.51.86:28015.

What Rust version is namserver on?

Version check: Rust network protocol 2634 and build 167231 on Windows, run by namserver. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is namserver, and is it online now?

Reading: offline. namserver last answered 18 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 7 October 2026.

Rules and settings

What rules does namserver enforce, and what are its settings?

Reading the name gives no gather rate for namserver. 8 players per group, the default value. Mode check gives survival; 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. Anti-cheat reading: VAC on, Valve's system.

What map is namserver on?

Procedural map on namserver, made by the game's generator.

Join

How do you connect to namserver?

Check: join. Open Rust, press F1, then enter client.connect 193.35.51.86:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs167231,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players 1 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167231
Build The server runs game build 167231.
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.