Rust Data

rustdata.spaceservers9.195.144.101:20004.ipynb

Run all rust-data · live

‹ All servers

Offline 9.195.144.101:20003 checked 24d ago

typical TEST

Connect

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

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,962 # top 71%
last wipe 26d 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
15k10k15k20k4 Oct5 Oct7 Oct8 Oct10 Oct11 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:20003
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 22:26 UTC
hostname
–
first seen
4 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 · 531 on average229/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average131/225
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average20/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 280 on average18/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average20/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 248 on average68/200

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does typical TEST rank?

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

How full does typical TEST run?

The current row shows typical TEST offline; the last response was 24 days 11 hours ago.

Server facts

What is the Rust version on typical TEST?

The build is Rust network protocol 2634 and build 166652 on Linux, run by typical TEST. Joining needs the same protocol on your game; Steam handles the update.

How reliable is typical TEST, and is it up?

The latest sample has typical TEST offline, with a last sighting 24 days 11 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 4 October 2026.

Which location does typical TEST run from?

There is no region published for typical TEST. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 9.195.144.101:20003.

Map and rules

Which rules apply on typical TEST, and what settings?

No gather rate appears in the name: typical TEST. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat status: VAC on.

What is the map on typical TEST?

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

Wipe schedule

On what schedule does typical TEST wipe?

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. A new world was started 26 days 8 hours ago, and that is the one in play.

Lists and tags

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

On Rust Data, typical TEST appears in these lists: 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 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): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is 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.

Join steps

What is the way into typical TEST?

The manual route: launch Rust, F1, then client.connect 9.195.144.101:20003. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2634,gmrust,cs166652,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.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs166652
Build Recorded game build: 166652.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is 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 37,934 players 11,623 servers online