Rust Data

rustdata.spaceservers106.72.130.224:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 106.72.130.224:28015 checked 18h ago

MySoloServer

Connect

srv = rust.server("106.72.130.224:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 1/1 # 100% full
7-day average 1 # peak 1
rank #5,228 # top 23%
last wipe 4d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75113:0015:0016:0018:0019:0013:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap5.8 daysbetween real wipes
on rhythm43%of its recent wipes
wipe-day peak1players, last three wipes
crowd held75%else halves by day 2

The first 48 hours of its last wipes

Sat 24 OctSat 24 OctMon 19 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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 24 Oct, 20:07 UTC4d ago 1 NaN running 1
1 Sat 24 Oct, 11:04 UTC4d ago 1 NaN 0.4 days 0
2 Mon 19 Oct, 07:12 UTC10d ago 1 held half 5.2 days 1
3 Tue 13 Oct, 12:47 UTC15d ago 1 held half 5.8 days 1
4 Sun 4 Oct, 01:39 UTC25d ago 1 held half 9.5 days 1
5 Wed 23 Sep, 12:45 UTC35d ago 1 halved by day 2 10.5 days 1
6 Sun 20 Sep, 10:54 UTC38d ago 1 held half 3.1 days 0
7 Mon 14 Sep, 00:17 UTC45d ago 1 halved by day 2 6.4 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
106.72.130.224:28015
region
–
max players
1
group limit
8, the default
wipe schedule
–
last wipe
24 Oct 2026, 20:07 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 531 on average258/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average191/225
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average21/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 280 on average22/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average22/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 248 on average91/200

Quick answers

From the figures on this page.

Player counts

What position does MySoloServer take in the server rankings?

Player hours over seven days put MySoloServer at #5,228, in the top 23% of the ranked set.

How many players does MySoloServer hold at once?

MySoloServer returns no live count at this refresh, having last been seen 18 hours ago. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 15:00 UTC, averaging 1 players.

Server facts

Which Rust version is MySoloServer on?

Version Rust network protocol 2635 and build 168909 on Windows is reported by MySoloServer. Joining needs the same protocol on your game; Steam handles the update.

How reliable is MySoloServer, and is it online now?

The latest sample has MySoloServer offline, with a last sighting 18 hours ago. Over the last 7 full days the hours up number 50 of 168, 30%. The first row Rust Data holds for it is dated 13 September 2026.

Which location does MySoloServer run from?

For MySoloServer, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 106.72.130.224:28015 is its address.

Settings and map

What rules and settings are recorded for MySoloServer?

The name MySoloServer carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has MySoloServer selected?

MySoloServer runs a procedural map, which the game generates.

Wipe data

On what schedule does MySoloServer wipe?

No next wipe can be predicted for MySoloServer, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 4 days 11 hours ago.

What is wipe day on MySoloServer like?

Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 75% of the time. In the wipes where it did not hold, half was lost by day 2.

Tags and filters

Which Rust Data filters and lists contain MySoloServer?

On Rust Data, MySoloServer appears in these lists: Rust community servers, unfiltered. 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; Last wipe: In the last week.

Which meanings do the tags on MySoloServer hold?

Read by the game's server browser, the tags MySoloServer publishes are: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

How to join

How can I connect to MySoloServer?

Enter client.connect 106.72.130.224:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp1
Max players 1 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build The server runs build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not 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.

Rust Data 39,799 players 11,618 servers online