Rust Data

rustdata.spaceservers9.244.16.170:28020.ipynb

Run all rust-data · live

‹ All servers

Offline 9.244.16.170:28019 checked 40d ago

typical test2

Connect

srv = rust.server("9.244.16.170:28020")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,398 # no region published
last wipe 40d 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 Sep24 Sep25 Sep26 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.16.170:28019
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
19 Sep 2026, 06:09 UTC
hostname
–
first seen
19 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 · 495 on average109/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average124/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 283 on average455/575
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 277 on average26/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average534/650
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 251 on average439/525

Quick answers

From the figures on this page.

Population

How does typical test2 compare in the rankings?

Player hours over seven days put typical test2 at #15,398, in the top – of the ranked set.

How many players does typical test2 hold at once?

typical test2 returns no live count at this refresh, having last been seen 40 days 17 hours ago.

Server facts

What is the Rust version on typical test2?

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

Is typical test2 up, and what does its uptime show?

Offline now for typical test2, last seen 40 days 17 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 19 September 2026.

Which location does typical test2 run from?

There is no region published for typical test2. 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.244.16.170:28019.

Settings and map

What rules and settings are recorded for typical test2?

You will not find a gather rate in the string typical test2. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.

What is the map on typical test2?

A procedural map runs on typical test2, generated by the game.

Wipe schedule

When does typical test2 wipe, and how often?

A rhythm cannot be read from the wipes of typical test2 on record, which are too few. 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 40 days 17 hours ago.

Tags, lists

Where does typical test2 appear among Rust Data lists and filters?

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

Which meanings do the tags on typical test2 hold?

Read by the game's server browser, the tags typical test2 publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): The server runs build 164530; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. 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 typical test2?

In Rust, F1 opens the console: type client.connect 9.244.16.170:28019. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players 100 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2633
Protocol To join, your game must run protocol 2633.
cs164530
Build The server runs build 164530.
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 63,580 players 11,733 servers online