Rust Data

rustdata.spaceservers46.63.106.19:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 46.63.106.19:28015 checked 27d ago

test_server

Connect

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

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak –
rank #14,212 # top 60%
last wipe 27d 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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

Top 60% 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
46.63.106.19:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 10:16 UTC
hostname
–
first seen
1 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 · 552 on average636/675
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average485/525
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 299 on average59/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 298 on average36/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 270 on average138/200
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 256 on average255/300

Quick answers

From the figures on this page.

Population data

How does test_server compare in the rankings?

Rank #14,212 on seven-day player hours for test_server, within the top 60% of all ranked servers.

How full does test_server run?

test_server returns no live count at this refresh, having last been seen 27 days 7 hours ago.

Server facts

What Rust version does test_server run?

Version Rust network protocol 2634 and build 166465 on Windows is reported by test_server. Joining needs the same protocol on your game; Steam handles the update.

Is test_server up, and what does its uptime show?

test_server is offline at this refresh; the last response came 27 days 7 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 1 October 2026.

Which location does test_server run from?

There is no region published for test_server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 46.63.106.19:28015 is its address.

Settings and map

Which settings and rules does test_server run?

You will not find a gather rate in the string test_server. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

Which map has test_server loaded?

test_server runs a procedural map, which the game generates.

Wipes and dates

When does test_server wipe, and how often?

A rhythm cannot be read from the wipes of test_server 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 27 days 9 hours ago.

Lists and tags

Which Rust Data filters and lists contain test_server?

On Rust Data, test_server 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.

How should you read the server tags on test_server?

Read by the game's server browser, the tags test_server publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166465 (Build): Recorded game build: 166465; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into test_server?

In Rust, F1 opens the console: type client.connect 46.63.106.19: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 mp10,ptrak,$r?,v2634,gmrust,cs166465,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs166465
Build Recorded game build: 166465.
ptrak
Networking Standard network layer for Rust: RakNet.
$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 89,289 players 11,829 servers online