Rust Data

rustdata.spaceservers9.195.144.101:20002.ipynb

Run all rust-data · live

‹ All servers

Offline 9.195.144.101:20000 checked 22d ago

typical Test2

Connect

srv = rust.server("9.195.144.101:20002")
print(srv.connect_command)

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 0 # peak –
rank #15,956 # top 71%
last wipe 23d 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
15k10k15k20k5 Oct7 Oct8 Oct10 Oct11 Oct13 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.195.144.101:20000
region
–
max players
40
group limit
8, the default
wipe schedule
–
last wipe
5 Oct 2026, 05:51 UTC
hostname
–
first seen
5 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 · 565 on average195/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average114/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average21/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 289 on average12/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average21/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 251 on average27/225

Quick answers

From the figures on this page.

Player counts

How does typical Test2 compare in the rankings?

Rank #15,956 on seven-day player hours for typical Test2, within the top 71% of all ranked servers.

How full does typical Test2 run?

The current row shows typical Test2 offline; the last response was 22 days 23 hours ago.

Server facts

Which Rust version is typical Test2 on?

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

How reliable is typical Test2, and is it up?

Offline now for typical Test2, last seen 22 days 23 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 5 October 2026.

In which location is typical Test2 hosted?

For typical Test2, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 9.195.144.101:20000.

Settings and map

Which settings and rules does typical Test2 run?

You will not find a gather rate in the string typical Test2. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. Anti-cheat status: VAC on.

Which map has typical Test2 selected?

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

Wipes and dates

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 23 days 19 hours ago.

Tags, lists

Which lists on Rust Data hold typical Test2, and which filters?

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

How should you read the server tags on typical Test2?

Read by the game's server browser, the tags typical Test2 publishes are: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): Slot count: 40; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Recorded game build: 166652; 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.195.144.101:20000. 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?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp40
Max players Slot count: 40.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs166652
Build Recorded game build: 166652.
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 41,011 players 11,701 servers online