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

My Solo Server

Offline 58.29.54.65:28015 checked 3d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,426top 69%
Last wipe3d 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
15k10k15k20k25 Oct26 Oct27 Oct28 Oct

Top 69% 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 peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 25 Oct, 07:15 UTC3d ago 0 – 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 schedule

What happens on My Solo Server when wipe day comes?

An average of 0 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does My Solo Server follow?

Its rhythm cannot be told from the wipes of My Solo Server 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. 3 days 10 hours ago the current world was made.

Tags

How should you read the tags on My Solo Server?

These are the tags My Solo Server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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 My Solo Server appear in Rust Metrics lists and filters?

These Rust Metrics lists carry My Solo Server: 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; Last wipe: In the last week.

Player count

Where does My Solo Server sit in the rankings?

Player hours over seven days put My Solo Server at #15,426, in the top 69% of all ranked servers.

What player count does My Solo Server carry?

My Solo Server is not responding; status offline, last seen 3 days 10 hours ago. A seven-day average of 0 players is the reading.

Server details

Which location does My Solo Server run from?

No region comes from My Solo Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 58.29.54.65:28015.

What Rust version is My Solo Server on?

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

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

My Solo Server reports offline. The last reading came 3 days 10 hours ago. Uptime for the last 2 full days: 0 of 48 hours, or 0%. Reading: first seen 25 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on My Solo Server?

Check: gather rate. The name My Solo Server does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — 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 off.

What map is My Solo Server on?

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

Join

How do you connect to My Solo Server?

To join: start Rust, press F1 and type client.connect 58.29.54.65:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.