Rust Data LabData lab · live
Live readings Servers11,867 Players86,491 Populated4,000 Fresh wipes · 3h168 Sampled every 5 min

Element card · group Community · atomic number 13,792, its rank

Solo

Offline 90.150.253.35:28015 checked 25d ago

Join the experiment
Atomic mass · players now 1/ 1 100% full Near capacity
7-day average0peak –
Rank · atomic number#13,792top 60%
Last wipe25d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
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.

Result 03

Rank

Result

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.

Reaction kinetics

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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 11:33 UTC25d ago 1 – running 0
Thu 1 Oct, 21:10 UTC FW25d 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rusty Moose |E… 762
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 504 on average 762/ 825
  2. 2 Ru Rustoria.co - … 51
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 345 on average 51/ 250
  3. 3 Ru Rusty Moose |E… 110
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 340 on average 110/ 250
  4. 4 Ru Rustoria.co - … 414
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 314 on average 414/ 500
  5. 5 Ru Rustoria.co - … 237
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 280 on average 237/ 300
  6. 6 Ru Rustafied.com … 181
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 259 on average 181/ 300

Quick answers

from the figures on this page

Settings and map

What map is in play on Solo?

The map on Solo is procedural, made by the game.

What rules has Solo set, and what settings are in force?

No gather rate appears in the name of Solo. Eight players per group is the limit, the game's default. survival is the game mode, raiding, building and gathering: the standard game. You can fight other players and raid them. You will find it under Community in the server browser. VAC is on, Valve's anti-cheat.

Server facts

Which location is Solo based in?

Nothing about a region is published by Solo. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 90.150.253.35:28015 is the address it uses.

Which Rust version is Solo on?

Rust network protocol 2634 and build 166586 on Windows is what Solo uses. Your game needs to match the protocol to join, and Steam updates it automatically.

How reliably does Solo stay online?

Right now Solo is offline, with its last appearance 25 days 7 hours ago. For the last 7 full days, 0 of 168 hours were online, giving 0% uptime. On 1 October 2026, Rust Data Lab saw it for the first time.

Wipe schedule

What is the wiping pattern on Solo?

Too few wipes are on record for Solo to reveal a rhythm. The next monthly force wipe, which wipes all Rust servers, is scheduled for Thursday 5 November at 19:00 UTC. The world it is running now dates from 25 days 8 hours ago.

On Solo, what happens when wipe day arrives?

Recent wipes on average reached 1 players at their busiest. The latest wipe's peak fell 0 hours after it began.

Tags, lists

How should you read the tags on Solo?

The game's server browser reads the tags Solo publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): It has 1 slots; ts8 (Group limit): This uses the game's default: 8 per team; v2634 (Protocol): Protocol 2634 is required; join only if your game matches it; cs166586 (Build): It runs build 166586; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): The region field is left blank. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Where among the Rust Data Lab lists and filters does Solo come up?

You will find Solo on the following Rust Data Lab lists: Rust community servers, measured. 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.

Population

Against other Rust servers, where does Solo place?

Solo sits at #13,792 for seven-day player hours, placing it in the top 60% of ranked servers.

What does the current player count on Solo tell you?

The last recorded sighting of Solo was 25 days 7 hours ago, and it is offline now.

How to join

How can you connect to Solo?

You can connect by pressing F1 in Rust and entering client.connect 90.150.253.35:28015, or by pressing Launch Rust here, which starts the game through Steam and joins for you.

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode Survival in the standard Rust style.
mp1
Max players It has 1 slots.
ts8
Group limit This uses the game's default: 8 per team.
v2634
Protocol Protocol 2634 is required; join only if your game matches it.
cs166586
Build It runs build 166586.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code The region field is left blank.

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.