RUST METRICSFlight deck · live data
Data live Servers11,682 Players55,436 Populated3,376 Fresh wipes 3 h102 Scan5 min
‹ All servers90.150.253.35:28015
Offline Full Queue Fresh wipe Wipe due No query

Solo

Offline 90.150.253.35:28015 checked 25d 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,792top 60%
Last wipe25d 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
15k10k15k20k1 Oct3 Oct4 Oct6 Oct7 Oct9 Oct

Top 60% 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 gap0.6 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctThu 1 Oct
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
Fri 2 Oct, 11:33 UTC25d ago 1 – running 0
Thu 1 Oct, 21:10 UTC FW26d ago 1 – 0.6 days 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

Reset cycle

What happens on Solo 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 Solo wipe, and when?

Its rhythm cannot be told from the wipes of Solo on record: there are too few. 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 25 days 22 hours ago.

Tag meanings

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

These are the tags Solo publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): Game build reading: 166586; ptrak (Networking): Network layer: RakNet, the standard for the game; $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 Solo appear in Rust Metrics lists and filters?

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

Population

What position does Solo hold among Rust servers?

Player hours over seven days put Solo at #13,792, in the top 60% of all ranked servers.

What is the population on Solo?

Reading for Solo: offline at this moment; last seen 25 days 21 hours ago.

Server

Where does Solo sit?

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

What Rust version is Solo on?

Version check: Rust network protocol 2634 and build 166586 on Windows, run by Solo. Matching protocol is required to join. Let Steam update your game.

How reliable is Solo, and is it online now?

Reading: offline. Solo last answered 25 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 1 October 2026, recorded by Rust Metrics.

Map and rules

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

Check: gather rate. The name Solo does not state one. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Solo?

The game generates a procedural map for Solo.

How to join

How do you connect to Solo?

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166586
Build Game build reading: 166586.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.