RUST METRICSFlight deck · live data
Data live Servers11,751 Players67,203 Populated3,396 Fresh wipes 3 h207 Scan5 min
‹ All servers122.167.112.226:28015
Offline Full Queue Fresh wipe Wipe due No query

My Private Solo World

Offline 122.167.112.226:28015 checked 23d 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,767top 61%
Last wipe24d 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 Oct6 Oct8 Oct9 Oct11 Oct13 Oct

Top 61% 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
Mon 5 Oct, 17:01 UTC24d ago 1 – running 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 timing

What should you expect from wipe day on My Private Solo World?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does My Private Solo World follow?

To tell the rhythm of My Private Solo World, too few of its wipes 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 it runs now was made 24 days 6 hours ago.

Tags

Which tags does My Private Solo World carry, and what do they mean?

Tags published by My Private Solo World, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): The server runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $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 My Private Solo World appear in Rust Metrics lists and filters?

These Rust Metrics lists carry My Private Solo World: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does My Private Solo World sit in the rankings?

Ranking for My Private Solo World: #13,767 on seven-day player hours, top 61% of all ranked servers.

How full does My Private Solo World get?

Status for My Private Solo World: offline. Last seen 23 days 9 hours ago.

Operator and location

Which location does My Private Solo World run from?

No region tag on My Private Solo World. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 122.167.112.226:28015.

What Rust version is My Private Solo World on?

Rust network protocol 2634 and build 166652 on Windows is the build My Private Solo World runs. To get in, your game needs the same protocol; Steam applies the update.

Is My Private Solo World up, and how often does it stay up?

My Private Solo World reports offline. The last reading came 23 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 4 October 2026.

Map and rules

What rules does My Private Solo World enforce, and what are its settings?

Reading the name gives no gather rate for My Private Solo World. 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. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on My Private Solo World?

Procedural map on My Private Solo World, made by the game's generator.

How to join

What do you do to join My Private Solo World?

Press F1 in Rust and enter client.connect 122.167.112.226: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?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build The server runs game build 166652.
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.