RUST METRICSFlight deck · live data
Data live Servers11,829 Players74,965 Populated3,733 Fresh wipes 3 h252 Scan5 min
‹ All servers62.33.111.56:28015
Offline Full Queue Fresh wipe Wipe due No query

Solo

Offline 62.33.111.56:28015 checked 3d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 1 /500

Players now

0% full 7-day avg7-day peak
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 average1peak 1
Rank#8,707top 39%
Last wipe7d 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
12.5k5k7.5k10k21 Oct23 Oct24 Oct26 Oct27 Oct29 Oct

Top 39% 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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 21 Oct, 17:42 UTC7d 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 schedule

What happens on Solo when wipe day comes?

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

How often does Solo wipe, and when?

To tell the rhythm of Solo, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 7 days 20 hours ago.

Lists and filters

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): Team cap of 8, which is the game default; 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): The region field is empty from Solo. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Solo appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Solo: 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.

Player count

Where does Solo sit in the rankings?

Player hours over seven days put Solo at #8,707, in the top 39% of all ranked servers.

How full does Solo get?

Reading for Solo: offline at this moment; last seen 3 days 20 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Server details

Which location does Solo run from?

Reading: location. Solo gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 62.33.111.56:28015.

What Rust version is Solo on?

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

How reliable is Solo, and is it online now?

Solo reports offline. The last reading came 3 days 20 hours ago. Uptime for the last 7 full days: 7 of 168 hours, or 4%. Reading: first seen 21 October 2026, recorded by Rust Metrics.

Rules and settings

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

Reading the name gives no gather rate for Solo. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is Solo on?

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

Connection

How can you get onto Solo?

Press F1 in Rust and enter client.connect 62.33.111.56: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 mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players The server holds 500 slots.
ts8
Group limit Team cap of 8, which is the game default.
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 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.