Rust Data

rustdata.spaceservers135.148.15.62:28016.ipynb

Run all rust-data · live

‹ All servers

Online 135.148.15.62:28015 checked 7m ago

Siunattu

Connect

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

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 0 # peak 2
rank #6,580 # top 30%
last wipe 6d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75103:0012:0021:0006:0015:0001:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040003:0012:0021:0006:0015:0001:00

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 17 Sep. 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 30% 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 gap2.1 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Thu 22 OctFri 16 OctTue 13 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 4 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 22 Oct, 17:25 UTC6d ago 2 NaN running 0
1 Fri 16 Oct, 22:39 UTC12d ago 1 halved by day 1 5.8 days 0
2 Tue 13 Oct, 19:45 UTC15d ago 1 halved by day 1 3.1 days 1
3 Sun 11 Oct, 22:23 UTC17d ago 1 NaN 1.9 days 1
4 Tue 6 Oct, 01:08 UTC23d ago 1 halved by day 2 5.9 days 1
5 Sun 4 Oct, 02:09 UTC25d ago 1 NaN 2 days 1
6 Thu 1 Oct, 18:54 UTC FW27d ago 1 held half 2.3 days 1
7 Tue 29 Sep, 21:48 UTC29d ago 1 NaN 1.9 days 0
8 Mon 28 Sep, 17:43 UTC30d ago 1 NaN 1.2 days 1
9 Fri 25 Sep, 04:57 UTC33d ago 1 halved by day 2 3.5 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

3100 · seed 123457
Map of Siunattu
map
Procedural Map
size
3100
seed
123457
Open on RustMaps

Server

srv.info()
address
135.148.15.62:28015
region
–
max players
40
group limit
8, the default
wipe schedule
–
last wipe
22 Oct 2026, 21:03 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 · 555 on average161/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average97/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average15/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 286 on average16/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average14/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 250 on average17/200

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does Siunattu rank?

Rank #6,580 on seven-day player hours for Siunattu, within the top 30% of all ranked servers.

What population does Siunattu carry?

The sample now reads 0 players for Siunattu, out of 40 slots. Over the last seven days it averaged 0 players and peaked at 2. Averaged by hour over 48 hours, 23:00 UTC is the busiest, at 1 players.

About the server

What does performance look like on Siunattu?

Averaged over 48 hours: 214 server fps, never under 161. The entity count peaked at 50,828, covering buildings, deployables and the rest of the world. Memory peaked at 4,035 MB. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on Siunattu?

Rust network protocol 2635 and build 168909 on Linux is what Siunattu runs. Steam updates your game for you, but the protocol must match to join.

Is Siunattu up, and what does its uptime show?

Siunattu reports itself online at the current refresh. Count back 32 hours from its reported uptime to get the last restart. 158 of 168 hours up over the last 7 full days, or 94%. The first row Rust Data holds for it is dated 13 September 2026.

Which location does Siunattu run from?

No region is published by Siunattu. Rust Data does not look up where the machine stands; it shows where a server says it is. 135.148.15.62:28015 is its address.

Rules, settings, map

Which rules apply on Siunattu, and what settings?

No gather rate appears in the name: Siunattu. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has Siunattu selected?

The game generates the map on Siunattu: procedural, size 3,100, seed 123457. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

On what schedule does Siunattu wipe?

Siunattu wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 6 days 5 hours ago, and that is the one in play.

On Siunattu, what happens on wipe day?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 4 hours in. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The drop under half arrived by day 1 in the other cases.

Tags and filters

Where does Siunattu appear among Rust Data lists and filters?

The Rust Data lists that Siunattu fits are: Rust community servers, unfiltered. It appears under these filters 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 Siunattu hold?

These tags are published by Siunattu and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): 40 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way into Siunattu?

Enter client.connect 135.148.15.62: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 mp40,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp40
Max players 40 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game 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 36,352 players 11,696 servers online