Rust Data

rustdata.spaceservers9.244.18.186:30003.ipynb

Run all rust-data · live

‹ All servers

Offline 9.244.18.186:30000 checked 32d ago

typical TEST

Connect

srv = rust.server("9.244.18.186:30003")
print(srv.connect_command)

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 0 # peak –
rank #16,490 # top 71%
last wipe 33d 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
15k10k15k20k25 Sep26 Sep28 Sep29 Sep1 Oct2 Oct

Top 71% 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.244.18.186:30000
region
–
max players
40
group limit
8, the default
wipe schedule
–
last wipe
25 Sep 2026, 08:04 UTC
hostname
–
first seen
25 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 · 540 on average654/675
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average399/425
2Rustoria.co - EU MainEU · groups of 16+ · weekly · 312 on average43/250
3Rusty Moose |EU Main|EU · groups of 12+ · weekly · 311 on average48/250
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 272 on average174/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 265 on average103/125

Quick answers

From the figures on this page.

Player counts

What position does typical TEST take in the server rankings?

Player hours over seven days put typical TEST at #16,490, in the top 71% of the ranked set.

What population does typical TEST carry?

Offline now for typical TEST, with the last sample 32 days 15 hours ago.

About the server

Which Rust version is typical TEST on?

Rust network protocol 2633 and build 165217 on Linux is what typical TEST runs. Steam updates your game for you, but the protocol must match to join.

How reliable is typical TEST, and is it up?

The latest sample has typical TEST offline, with a last sighting 32 days 15 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 25 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.18.186:30000.

Map and rules

Which rules apply on typical TEST, and what settings?

The name typical TEST carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.

Which map has typical TEST loaded?

The game generates its map: procedural, on typical TEST.

Wipe data

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. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 33 days 3 hours ago.

Lists and tags

Which Rust Data filters and lists contain typical TEST?

On Rust Data, typical TEST appears in these lists: 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; mp40 (Max players): 40 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $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.

Join steps

What is the way into typical TEST?

In Rust, F1 opens the console: type client.connect 9.244.18.186:30000. 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 mp40,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp40
Max players 40 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2633
Protocol To join, your game must run protocol 2633.
cs165217
Build Build number: 165217.
ptrak
Networking The network layer is RakNet, standard for the game.
$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 65,057 players 11,694 servers online