RUST METRICSFlight deck · live data
Data live Servers11,824 Players88,321 Populated3,715 Fresh wipes 3 h404 Scan5 min
‹ All servers221.150.194.220:28015
Offline Full Queue Fresh wipe Wipe due No query

SOLO

Offline 221.150.194.220:28015 checked 29d ago

COM 1 · connect

Server instruments

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

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#16,590top 70%
Last wipe29d agono schedule published
Next wipe–no wipe 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, measured since 30 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k30 Sep1 Oct3 Oct4 Oct6 Oct7 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 wipe timing does SOLO follow?

Its rhythm cannot be told from the wipes of SOLO 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. 29 days 6 hours ago the current world was made.

Tag meanings

How should you read the tags on SOLO?

Tags published by SOLO, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): Slots: 500; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): The server runs game build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $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 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.

Player count

What position does SOLO hold among Rust servers?

Player hours over seven days put SOLO at #16,590, in the top 70% of all ranked servers.

What is the population on SOLO?

Reading for SOLO: offline at this moment; last seen 29 days 5 hours ago.

Server

What location is SOLO hosted in?

No region comes from SOLO. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 221.150.194.220:28015.

What Rust version is SOLO on?

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

What is the uptime on SOLO, and is it online?

SOLO reports offline. The last reading came 29 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 30 September 2026.

Map and rules

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

Check: gather rate. The name SOLO does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is SOLO on?

Size 4,000 and seed 35221741: the game generates the procedural map on SOLO from them. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How do you connect to SOLO?

Check: join. Open Rust, press F1, then enter client.connect 221.150.194.220:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players Slots: 500.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build The server runs game build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.