Rust Data

rustdata.spaceservers46.138.162.88:29016.ipynb

Run all rust-data · live

‹ All servers

Offline 46.138.162.88:29015 checked 22d ago

TEST MASTER

teams off moddedoxide

Connect

srv = rust.server("46.138.162.88:29016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/175 # 0% full
7-day average 0 # peak –
rank #15,565 # top 70%
last wipe 22d ago # no schedule published
next wipe – # no rhythm it keeps

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 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1 daysbetween real wipes
on rhythm29%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Wed 7 OctTue 6 OctMon 5 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in, with 1 in the queue.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 7 Oct, 19:33 UTC22d ago 1+1 queue NaN running 0
1 Tue 6 Oct, 01:32 UTC24d ago 1+1 queue NaN 1.8 days 0
2 Mon 5 Oct, 19:28 UTC24d ago 0 NaN 0.3 days 0
3 Fri 2 Oct, 14:40 UTC27d ago 0 NaN 3.2 days 0
4 Thu 1 Oct, 14:52 UTC28d ago 0 NaN 1 days 0
5 Wed 30 Sep, 17:38 UTC29d ago 0 NaN 0.9 days 0
6 Thu 24 Sep, 23:55 UTC35d ago 0 NaN 5.7 days 0
7 Thu 24 Sep, 14:09 UTC35d ago 1 NaN 0.4 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

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
46.138.162.88:29015
region
– · ger
max players
175
group limit
teams off
wipe schedule
–
last wipe
7 Oct 2026, 23:25 UTC
hostname
–
first seen
17 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[EU] Builders Sanctuary 3.0 Creative | Sandbox | Minigames |EU · groups of 8+ · 120 on average40/999
1[NA] Builders Sanctuary 3.0 Creative | Sandbox | Minigames |NA · groups of 8+ · 94 on average58/999
2[AU] Rusticated.com - Creative Sandbox | Build | Never WipesOC · groups of 8+ · 53 on average72/150
3Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFAEU · groups of 30+ · weekly · 35 on average88/150
4KoalaKopters - Minicopter / Helicopter Training|Arena|Dogfightgroups of 8+ · 23 on average14/100
5AQRUX RUST BUILD | CREATIVE | SANDBOXEU · groups of 8+ · monthly · 23 on average18/100

Quick answers

From the figures on this page.

Player counts

What position does TEST MASTER take in the server rankings?

Player hours over seven days put TEST MASTER at #15,565, in the top 70% of the ranked set.

How full does TEST MASTER run?

The current row shows TEST MASTER offline; the last response was 22 days 8 hours ago.

Server facts

What is the Rust version on TEST MASTER?

The build is Rust network protocol 2634 and build 166494 on Windows, run by TEST MASTER. Steam updates your game for you, but the protocol must match to join.

How reliable is TEST MASTER, and is it up?

Offline now for TEST MASTER, last seen 22 days 8 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 17 September 2026.

Which location does TEST MASTER run from?

For TEST MASTER, no region is published; the region code is ger. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 46.138.162.88:29015 is its address.

Map and rules

What rules and settings are recorded for TEST MASTER?

The name TEST MASTER carries no gather rate. No group limit is published. Recorded as build & creative, sandbox construction, gathering off. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC on.

Wipe data

On what schedule does TEST MASTER wipe?

TEST MASTER wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 22 days 8 hours ago.

On TEST MASTER, what happens on wipe day?

Recent wipes averaged 1 players at their peak. A peak 2 hours into the latest wipe, plus 1 waiting in the queue.

Lists and tags

Where does TEST MASTER appear among Rust Data lists and filters?

On Rust Data, TEST MASTER appears in these lists: Modded Rust servers, Servers with build or creative tags and Rust creative servers, listed. These filters bring it up on the server list: Type: Modded; Server tag: Creative ^c, Build server ^k, Modded ^z and Oxide ^o.

Which meanings do the tags on TEST MASTER hold?

These tags are published by TEST MASTER and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp175 (Max players): The server lists 175 slots; ts0 (Group limit): The team system is off; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166494 (Build): The server runs build 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $rger (Region code): ger is the region code recorded; ^c (Creative): Build freely, with no gathering: sandbox mode; ^k (Build server): A place to design and practise bases; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^o (Oxide): The plugin framework in use is Oxide (uMod). The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

How can I connect to TEST MASTER?

The manual route: launch Rust, F1, then client.connect 46.138.162.88:29015. 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 mp175,ptrak,$rger,v2634,^z,^c,^k,^o,gmrust,cs166494,ts0

Game

gmrust
Game mode Survival play, standard Rust.
mp175
Max players The server lists 175 slots.
ts0
Group limit The team system is off.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs166494
Build The server runs build 166494.
ptrak
Networking Standard network layer for Rust: RakNet.
$rger
Region code ger is the region code recorded.

Gameplay

^c
Creative Build freely, with no gathering: sandbox mode.
^k
Build server A place to design and practise bases.

Mods and access

^z
Modded Plugins or settings alter the game, so it sits under Modded.
^o
Oxide The plugin framework in use is Oxide (uMod).

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 48,858 players 11,607 servers online