Rust Data

rustdata.spaceservers9.244.19.246:28018.ipynb

Run all rust-data · live

‹ All servers

Offline 9.244.19.246:28017 checked 42d ago

typical [TEST]

Connect

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

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,521 # no region published
last wipe 47d 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep

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.244.19.246:28017
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
11 Sep 2026, 20:32 UTC
hostname
–
first seen
15 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 · 513 on average527/550
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average426/450
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average57/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average59/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average58/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 238 on average161/200

Quick answers

From the figures on this page.

Population data

How does typical [TEST] compare in the rankings?

Player hours over seven days put typical [TEST] at #15,521, in the top – of the ranked set.

How full does typical [TEST] run?

Offline now for typical [TEST], with the last sample 42 days 18 hours ago.

Server data

What is the Rust version on typical [TEST]?

The build is Rust network protocol 2633 and build 163794 on Linux, run by typical [TEST]. Steam updates your game for you, but the protocol must match to join.

Is typical [TEST] up, and what does its uptime show?

typical [TEST] is offline at this refresh; the last response came 42 days 18 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 September 2026.

Which location does typical [TEST] run from?

There is no region published for typical [TEST]. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 9.244.19.246:28017 is its address.

Rules, settings, map

What rules and settings are recorded for typical [TEST]?

The name typical [TEST] carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. The server browser lists it under Community. Anti-cheat status: VAC on.

Which map has typical [TEST] loaded?

A procedural map runs on typical [TEST], generated by the game.

Wipes and dates

When does typical [TEST] wipe, and on what schedule?

A rhythm cannot be read from the wipes of typical [TEST] on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 47 days 16 hours ago.

Tags, lists

Which lists on Rust Data hold typical [TEST], and which filters?

These Rust Data lists include typical [TEST]: 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.

Which meanings do the tags on typical [TEST] hold?

These tags are published by typical [TEST] and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): Build number: 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way into typical [TEST]?

Enter client.connect 9.244.19.246:28017 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 mp100,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players 100 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol The server speaks protocol 2633, so match your game version.
cs163794
Build Build number: 163794.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

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 69,381 players 11,801 servers online