Rust Data

rustdata.spaceservers84.147.150.45:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 84.147.150.45:28015 checked 27d ago

TestServer

Connect

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

Right now

srv.summary()
players now 1/5 # 20% full
7-day average 0 # peak –
rank #14,412 # top 60%
last wipe 30d 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
15k10k15k20k30 Sep1 Oct3 Oct4 Oct6 Oct7 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
84.147.150.45:28015
region
–
max players
5
group limit
8, the default
wipe schedule
–
last wipe
27 Sep 2026, 14:37 UTC
hostname
–
first seen
30 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 · 508 on average667/750
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 343 on average50/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 339 on average87/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 315 on average370/450
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 280 on average179/250
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 260 on average162/250

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does TestServer rank?

Over the last seven days TestServer sits at #14,412 on player hours, in the top 60% of ranked servers.

How full does TestServer run?

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

About the server

Which Rust version is TestServer on?

Version Rust network protocol 2633 and build 165217 on Windows is reported by TestServer. The protocol has to match before you can join, and Steam does the updating.

How reliable is TestServer, and is it online now?

Offline now for TestServer, last seen 27 days 8 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 30 September 2026.

Which location does TestServer run from?

There is no region published for TestServer. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 84.147.150.45:28015 is its address.

Settings and map

What rules and settings are recorded for TestServer?

The name TestServer carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.

Which map has TestServer loaded?

The game generates its map: procedural, on TestServer.

Wipe schedule

When does TestServer wipe, and on what schedule?

The record for TestServer holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 30 days 6 hours ago.

Tags, lists

Which lists on Rust Data hold TestServer, and which filters?

The Rust Data lists that TestServer fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which meanings do the tags on TestServer hold?

The game's server browser reads these tags from TestServer: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): Slot count: 5; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Build number: 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way into TestServer?

Enter client.connect 84.147.150.45:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp5,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp5
Max players Slot count: 5.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2633
Protocol Protocol 2633 is required; a different game version cannot connect.
cs165217
Build Build number: 165217.
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 76,849 players 11,834 servers online