Rust Data

rustdata.spaceservers9.244.16.170:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 9.244.16.170:28015 checked 39d ago

typical TEST

Connect

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

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,413 # no region published
last wipe 39d ago # no schedule published
next wipe – # too few wipes 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 · too few wipes seen yet

srv.wipe_schedule()

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

usual gap1.9 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Sat 19 SepThu 17 Sep
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 19 Sep, 05:20 UTC40d ago 0 NaN running 0
1 Thu 17 Sep, 07:02 UTC41d ago 0 NaN 1.9 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
9.244.16.170:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
19 Sep 2026, 07:46 UTC
hostname
–
first seen
16 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 · 537 on average162/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average148/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average15/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 281 on average15/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average19/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 248 on average69/200

Quick answers

From the figures on this page.

Population data

What position does typical TEST take in the server rankings?

Over the last seven days typical TEST sits at #15,413 on player hours, in the top – of ranked servers.

How full does typical TEST run?

typical TEST returns no live count at this refresh, having last been seen 39 days 12 hours ago.

About the server

What Rust version does typical TEST run?

The build is Rust network protocol 2633 and build 164530 on Linux, run by typical TEST. The protocol has to match before you can join, and Steam does the updating.

How reliable is typical TEST, and is it online now?

The latest sample has typical TEST offline, with a last sighting 39 days 12 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 16 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. You can reach it at 9.244.16.170:28015.

Rules, settings, map

Which settings and rules does typical TEST run?

No gather rate appears in the name: typical TEST. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has typical TEST selected?

typical TEST runs a procedural map, which the game generates.

Wipe schedule

When does typical TEST wipe, and on what schedule?

Too few wipes are on record for typical TEST 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. The world it runs now was generated 39 days 22 hours ago.

What is wipe day on typical TEST like?

The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.

Tags and filters

Which Rust Data filters and lists contain typical TEST?

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?

Read by the game's server browser, the tags typical TEST publishes are: 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): To join, your game must run protocol 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. 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 TEST?

In Rust, F1 opens the console: type client.connect 9.244.16.170:28015. 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 The default cap applies: 8 per team.
v2633
Protocol To join, your game must run protocol 2633.
cs164530
Build Build number: 164530.
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 32,693 players 11,617 servers online