RUST METRICSFlight deck · live data
Data live Servers11,720 Players60,549 Populated3,378 Fresh wipes 3 h181 Scan5 min
‹ All servers37.32.73.156:28015
Offline Full Queue Fresh wipe Wipe due No query

My Solo Rust

Offline 37.32.73.156:28015 checked 33d 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,973top 61%
Last wipe34d 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 Sep24 Sep26 Sep28 Sep30 Sep2 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
Thu 24 Sep, 14:07 UTC34d 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

Wipe timing

What happens on My Solo Rust when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does My Solo Rust wipe?

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. 34 days 21 hours ago the current world was made.

Tags

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

These are the tags My Solo Rust publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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

On Rust Metrics, My Solo Rust sits in these lists: 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.

Player count

Where does My Solo Rust sit in the rankings?

Player hours over seven days put My Solo Rust at #13,973, in the top 61% of all ranked servers.

What is the population on My Solo Rust?

Status for My Solo Rust: offline. Last seen 33 days 18 hours ago.

Server

Which location does My Solo Rust run from?

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

What Rust version is My Solo Rust on?

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

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

Check: connection. My Solo Rust is offline at this moment. Last contact was 33 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 22 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on My Solo Rust?

Reading the name gives no gather rate for My Solo Rust. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is My Solo Rust on?

The game generates a procedural map for My Solo Rust.

How to join

What do you do to join My Solo Rust?

Press F1 in Rust and enter client.connect 37.32.73.156: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,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players The server holds 1 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Game build reading: 165217.
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.