RUST METRICSFlight deck · live data
Data live Servers11,721 Players48,587 Populated3,224 Fresh wipes 3 h110 Scan5 min
‹ All servers213.65.29.67:28015
Offline Full Queue Fresh wipe Wipe due No query

My Solo Server

Offline 213.65.29.67:28015 checked 13d ago

COM 1 · connect

Server instruments

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

Players now

10% 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#14,106top 65%
Last wipe13d 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
15k10k15k20k20 Sep22 Sep15 Oct17 Oct20 Oct22 Oct

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

usual gap28.2 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Thu 15 OctThu 17 Sep
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 15 Oct, 10:41 UTC13d ago 1 – running 1
Thu 17 Sep, 06:34 UTC41d ago 1 – 28.2 days 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 happens on My Solo Server when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

How often does My Solo Server wipe, and when?

To tell the rhythm of My Solo Server, 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 13 days 13 hours ago.

Lists and filters

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

These are the tags My Solo Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show My Solo Server?

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

Occupancy

Where does My Solo Server sit in the rankings?

Player hours over seven days put My Solo Server at #14,106, in the top 65% of all ranked servers.

What is the population on My Solo Server?

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

Server details

Where does My Solo Server sit?

Reading: location. My Solo Server gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 213.65.29.67:28015.

What Rust version is My Solo Server on?

Rust network protocol 2634 and build 167781 on Windows is the build My Solo Server runs. Matching protocol is required to join. Let Steam update your game.

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

Check: connection. My Solo Server is offline at this moment. Last contact was 13 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 16 September 2026, recorded by Rust Metrics.

Settings and map

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

Reading the name gives no gather rate for My Solo Server. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

Join

How can you get onto My Solo Server?

Press F1 in Rust and enter client.connect 213.65.29.67: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 mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build The server runs game build 167781.
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.