Rust Data

rustdata.spaceservers9.246.13.82:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 9.246.13.82:28015 checked 11d ago

LinuxGSM

Connect

srv = rust.server("9.246.13.82:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,102 # top 70%
last wipe 20d 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
15k10k15k20k15 Oct17 Oct18 Oct20 Oct21 Oct23 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
9.246.13.82:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
7 Oct 2026, 18:46 UTC
hostname
–
first seen
15 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 · 543 on average653/725
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average448/475
2Rustoria.co - EU MainEU · groups of 16+ · weekly · 308 on average37/250
3Rusty Moose |EU Main|EU · groups of 12+ · weekly · 308 on average49/250
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 268 on average214/250
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 266 on average135/175

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does LinuxGSM rank?

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

How many players does LinuxGSM hold at once?

Offline now for LinuxGSM, with the last sample 11 days 22 hours ago.

Server data

Which Rust version is LinuxGSM on?

Version Rust network protocol 2634 and build 167231 on Linux is reported by LinuxGSM. Joining needs the same protocol on your game; Steam handles the update.

How reliable is LinuxGSM, and is it up?

Offline now for LinuxGSM, last seen 11 days 22 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 15 October 2026.

Which location does LinuxGSM run from?

No region is published by LinuxGSM. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 9.246.13.82:28015.

Map and rules

Which rules apply on LinuxGSM, and what settings?

You will not find a gather rate in the string LinuxGSM. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

Which map has LinuxGSM selected?

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

Wipe schedule

When does LinuxGSM wipe, and on what schedule?

Too few wipes are on record for LinuxGSM to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 20 days 19 hours ago, and that is the one in play.

Tags, lists

Where does LinuxGSM appear among Rust Data lists and filters?

The Rust Data lists that LinuxGSM fits are: 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.

How should you read the server tags on LinuxGSM?

These tags are published by LinuxGSM and read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167231 (Build): Recorded game build: 167231; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is 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.

Connecting

How can I connect to LinuxGSM?

Enter client.connect 9.246.13.82: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 mp50,ptrak,$r?,v2634,gmvanilla,cs167231,ts8

Game

gmvanilla
Game mode The mode is vanilla survival.
mp50
Max players 50 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs167231
Build Recorded game build: 167231.
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 76,905 players 11,770 servers online