RUST METRICSFlight deck · live data
Data live Servers11,711 Players58,911 Populated3,347 Fresh wipes 3 h176 Scan5 min
‹ All servers81.249.188.58:28015
Offline Full Queue Fresh wipe Wipe due No query

Rust Solo Prive

Offline 81.249.188.58:28015 checked 6d 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 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#11,033top 50%
Last wipe6d 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
15k10k15k20k22 Oct23 Oct25 Oct26 Oct28 Oct29 Oct

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

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
Thu 22 Oct, 20:48 UTC6d ago 1 – running 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

Reset cycle

What should you expect from wipe day on Rust Solo Prive?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does Rust Solo Prive follow?

The rhythm of Rust Solo Prive's wipes cannot be told yet: too few are on record. 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 6 days 14 hours ago.

Tag meanings

How should you read the tags on Rust Solo Prive?

Tags published by Rust Solo Prive, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): The server holds 1 slots; 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): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Rust Solo Prive appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Rust Solo Prive: 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.

Player count

What position does Rust Solo Prive hold among Rust servers?

Player hours over seven days put Rust Solo Prive at #11,033, in the top 50% of all ranked servers.

What player count does Rust Solo Prive carry?

Rust Solo Prive is not responding; status offline, last seen 6 days 2 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Server details

What location is Rust Solo Prive hosted in?

No region comes from Rust Solo Prive. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 81.249.188.58:28015.

What Rust version is Rust Solo Prive on?

Reading: Rust Solo Prive, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

How reliable is Rust Solo Prive, and is it online now?

Check: connection. Rust Solo Prive is offline at this moment. Last contact was 6 days 2 hours ago. Reading: 1% uptime over the last 6 full days. It was up 1 of 144 hours. The first sighting on Rust Metrics was 22 October 2026.

Rules and settings

What rules does Rust Solo Prive enforce, and what are its settings?

No gather rate appears in the name: Rust Solo Prive. 8 players per group, the default value. 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. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is Rust Solo Prive on?

Procedural map on Rust Solo Prive, made by the game's generator.

How to join

How do you connect to Rust Solo Prive?

Press F1 in Rust and enter client.connect 81.249.188.58: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?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players The server holds 1 slots.
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 Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is 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.