RUST METRICSFlight deck · live data
Data live Servers11,716 Players55,754 Populated3,252 Fresh wipes 3 h168 Scan5 min
‹ All servers81.9.50.118:28015
Offline Full Queue Fresh wipe Wipe due No query

SoloServerRust

Offline 81.9.50.118:28015 checked 39d ago

COM 1 · connect

Server instruments

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

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#14,396no region published
Last wipe40d 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 Sep21 Sep22 Sep24 Sep25 Sep26 Sep
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 schedule

What wipe timing does SoloServerRust follow?

Its rhythm cannot be told from the wipes of SoloServerRust on record: there are too few. 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 40 days 17 hours ago.

Tag meanings

How should you read the tags on SoloServerRust?

These are the tags SoloServerRust publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): The server runs game build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does SoloServerRust appear in Rust Metrics lists and filters?

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

Occupancy

What position does SoloServerRust hold among Rust servers?

Ranking for SoloServerRust: #14,396 on seven-day player hours, top – of all ranked servers.

What is the population on SoloServerRust?

Reading for SoloServerRust: offline at this moment; last seen 39 days 14 hours ago.

Operator and location

Which location does SoloServerRust run from?

Reading: location. SoloServerRust gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 81.9.50.118:28015.

What Rust version is SoloServerRust on?

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

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

SoloServerRust reports offline. The last reading came 39 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 19 September 2026, recorded by Rust Metrics.

Map and rules

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

Reading the name gives no gather rate for SoloServerRust. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is SoloServerRust on?

The game generates a procedural map for SoloServerRust.

How to join

How do you connect to SoloServerRust?

Check: join. Open Rust, press F1, then enter client.connect 81.9.50.118: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?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players The server holds 1 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164530
Build The server runs game build 164530.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.