Rust Data

rustdata.spaceservers72.225.139.233:28018.ipynb

Run all rust-data · live

‹ All servers

Offline 72.225.139.233:28015 checked 14d ago

SIPLAB

Connect

srv = rust.server("72.225.139.233:28018")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,236 # top 70%
last wipe 14d ago # no schedule published
next wipe – # no wipe seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

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
15k10k15k20k14 Oct15 Oct17 Oct18 Oct20 Oct21 Oct

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

Wipe schedule

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · no wipe seen yet.

# 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
72.225.139.233:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
14 Oct 2026, 14:24 UTC
hostname
–
first seen
14 Oct 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 · 514 on average541/525
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average387/450
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average49/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average50/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average57/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 241 on average165/200

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does SIPLAB rank?

Rank #15,236 on seven-day player hours for SIPLAB, within the top 70% of all ranked servers.

What population does SIPLAB carry?

Offline now for SIPLAB, with the last sample 14 days 21 hours ago.

Server facts

Which Rust version is SIPLAB on?

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

Is SIPLAB up, and what does its uptime show?

The latest sample has SIPLAB offline, with a last sighting 14 days 21 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 14 October 2026.

Which location does SIPLAB run from?

There is no region published for SIPLAB. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 72.225.139.233:28015.

Rules, settings, map

Which settings and rules does SIPLAB run?

You will not find a gather rate in the string SIPLAB. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has SIPLAB selected?

SIPLAB runs a procedural map, which the game generates.

Wipe data

On what schedule does SIPLAB wipe?

Too few wipes are on record for SIPLAB to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 14 days 21 hours ago.

Lists and tags

Which lists on Rust Data hold SIPLAB, and which filters?

The Rust Data lists that SIPLAB fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the server tags on SIPLAB?

These tags are published by SIPLAB and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

What is the way to join SIPLAB?

Enter client.connect 72.225.139.233: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 mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs167781
Build The server runs build 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is 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 66,925 players 11,786 servers online