RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h90 Scan5 min
‹ All servers72.190.197.154:28015
Offline Full Queue Fresh wipe Wipe due No query

My Solo Rust

Offline 72.190.197.154:28015 checked 15d 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,408top 71%
Last wipe16d 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
15k10k15k20k12 Oct14 Oct15 Oct17 Oct18 Oct20 Oct

Top 71% 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 12 Oct, 00:44 UTC16d 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 happens on My Solo Rust when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

How often does My Solo Rust wipe, and when?

To tell the rhythm of My Solo Rust, 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 in play was created 16 days 15 hours ago.

Tag meanings

How should you read the tags on My Solo Rust?

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): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Game build reading: 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from My Solo Rust. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

These Rust Metrics lists carry My Solo Rust: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does My Solo Rust hold among Rust servers?

Player hours over seven days put My Solo Rust at #15,408, in the top 71% of all ranked servers.

How full does My Solo Rust get?

Reading for My Solo Rust: offline at this moment; last seen 15 days 13 hours ago.

Operator and location

What location is My Solo Rust hosted in?

No region tag on My Solo Rust. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 72.190.197.154:28015.

What Rust version is My Solo Rust on?

Reading: My Solo Rust, Rust network protocol 2634 and build 167398, Windows. Matching protocol is required to join. Let Steam update your game.

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

My Solo Rust reports offline. The last reading came 15 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 12 October 2026.

Settings and map

How is My Solo Rust configured, and what rules are in force?

No gather rate appears in the name: My Solo Rust. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is My Solo Rust on?

Check: map. Procedural, generated by the game, on My Solo Rust.

How to join

What do you do to join My Solo Rust?

Check: join. Open Rust, press F1, then enter client.connect 72.190.197.154: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,cs167398,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build Game build reading: 167398.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.