Rust Data LabData lab · live
Live readings Servers11,766 Players65,323 Populated3,462 Fresh wipes · 3h190 Sampled every 5 min

Element card · group Community · atomic number 14,443, its rank

Solo

Offline 31.163.94.10:28015 checked 29d ago

Join the experiment
Atomic mass · players now 1/ 1 100% full Near capacity
7-day average0peak –
Rank · atomic number#14,443top 60%
Last wipe30d 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
15k10k15k20k26 Sep28 Sep30 Sep3 Oct5 Oct7 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 gap2.1 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Mon 28 SepSat 26 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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 28 Sep, 17:30 UTC30d ago 1 – running 0
Sat 26 Sep, 14:28 UTC32d ago 1 – 2.1 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… 500
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 514 on average 500/ 525
  2. 2 Ru Rustoria.co - … 388
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average 388/ 450
  3. 3 Ru Rusty Moose |E… 49
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average 49/ 250
  4. 4 Ru Rustoria.co - … 48
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 276 on average 48/ 250
  5. 5 Ru Rustafied.com … 51
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average 51/ 100
  6. 6 Ru Rustoria.co - … 161
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 241 on average 161/ 200

Quick answers

from the figures on this page

Server setup

What map is in play on Solo?

A procedural map runs on Solo, generated by the game.

What settings and rules apply on Solo?

The name of Solo carries no gather rate. Groups top out at 8 players, the default for the game. Play runs as survival, gather, build and raid, as in the standard game. You can fight other players and raid them. You will find it under Community in the server browser. The VAC anti-cheat from Valve is enabled.

Server facts

What region hosts Solo?

There is no region on record for Solo. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. You will find it at 31.163.94.10:28015.

Which Rust version is Solo on?

On Windows, Solo is running Rust network protocol 2633 and build 165217. Your game needs to match the protocol to join, and Steam updates it automatically.

How dependable is Solo for staying online?

Right now Solo is offline, with its last appearance 29 days 1 hours ago. It was online for 0 of 168 hours in the last 7 full days, which is 0% uptime. The first sighting by Rust Data Lab was on 26 September 2026.

Wipes and resets

What is the wiping pattern on Solo?

Too few wipes are on record for Solo to reveal a rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. Counting back, the current world began 30 days 18 hours ago.

On Solo, what happens when wipe day arrives?

At their busiest, recent wipes averaged 1 players. 0 hours after the latest wipe, the crowd peaked.

Where it appears

Which meanings sit behind 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): Player slots: 1; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): To join, your game must match protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): This runs on RakNet, the standard layer; $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?

The Rust Data Lab lists that include Solo are: Rust community servers, measured. Applying these filters on the server list returns it: 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 #14,443 for seven-day player hours, placing it in the top 60% of ranked servers.

How many players does Solo have at the moment?

No live signal from Solo right now, which was last seen 29 days 1 hours ago.

How to join

What steps get you onto Solo?

In Rust, press F1 and enter client.connect 31.163.94.10:28015. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp1
Max players Player slots: 1.
ts8
Group limit Teams cap at 8, which is the game default.
v2633
Protocol To join, your game must match protocol 2633.
cs165217
Build The game build is 165217.
ptrak
Networking This runs on RakNet, the standard layer.
$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.