Rust Server TrendsSeismic network · station log
Recording Stations11,890 Players103,751 Active3,994 Wipes · 3 h411 48 h

Station XX-14774 · no signal

Solo

Offline 81.177.189.7:28015 checked 10d ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,774
top 67%
Last wipe
10d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-14774 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k18 Oct20 Oct21 Oct23 Oct24 Oct26 Oct

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

Expected events

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 peak
1players, 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, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sun 18 Oct, 20:05 UTC10d ago M0.0rising 1 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 151 on average
126/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
128/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
197/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 95 on average
77/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 89 on average
226/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 84 on average
349/ 350
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Solo?

Solo uses a procedural map, which the game generates.

Which settings and rules apply on Solo?

No gather rate appears in the name of Solo. Groups hold up to 8 players, which is the default for the game. survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.

Population

How many players are recorded on Solo right now?

A reading taken now finds Solo offline; the most recent activity was 10 days 8 hours ago.

How does Solo rank against other Rust servers?

Over the last seven days, Solo recorded enough player hours to reach #14,774 worldwide, placing it in the top 67% of all ranked servers.

Server details

How reliably does Solo stay online?

No contact with Solo right now, and the last recorded contact was 10 days 8 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 18 October 2026 is when Rust Server Trends first recorded it.

Which region does Solo run from?

No region is published by Solo. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 81.177.189.7:28015.

Which Rust version is Solo running?

Solo is running Rust network protocol 2634 and build 167781 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on Solo?

On average, the busiest point of its recent wipes drew 1 players. 0 hours into the latest wipe, the crowd reached its peak.

How often does Solo wipe, and on which days?

On record so far are too few of Solo's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 10 days 22 hours.

Server tags

What do the server tags on Solo mean?

Tags published by Solo and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): 10 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): It runs game build 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Solo appear?

You will find Solo on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How to join

What steps get you onto Solo?

Enter client.connect 81.177.189.7:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp10
Max players 10 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167781
Build It runs game build 167781.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.