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

SoloServerRust

Offline 81.9.50.246:28015 checked 38d 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#15,426no 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 Sep23 Sep24 Sep26 Sep27 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

When does SoloServerRust wipe?

Its rhythm cannot be told from the wipes of SoloServerRust 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 40 days 15 hours ago.

Tags

How should you read the tags on SoloServerRust?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): The server runs game build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from SoloServerRust. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does SoloServerRust appear in Rust Metrics lists and filters?

On Rust Metrics, SoloServerRust sits in these lists: 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?

Player hours over seven days put SoloServerRust at #15,426, in the top – of all ranked servers.

How full does SoloServerRust get?

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

Server

Where does SoloServerRust sit?

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

What Rust version is SoloServerRust on?

Version check: Rust network protocol 2633 and build 164530 on Windows, run by SoloServerRust. 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 38 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 20 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on SoloServerRust?

Reading the name gives no gather rate for SoloServerRust. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is SoloServerRust on?

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

Connection

How can you get onto SoloServerRust?

Press F1 in Rust and enter client.connect 81.9.50.246:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

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 1 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build The server runs game build 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.