Rust Data

rustdata.spaceservers216.245.177.46:28017.ipynb

Run all rust-data · live

‹ All servers

Online 216.245.177.46:28015 checked 11m ago

Test Server

solo

Connect

srv = rust.server("216.245.177.46:28017")
print(srv.connect_command)

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123418:0003:0012:0022:0007:0016:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020018:0003:0012:0022:0007:0016:00

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, measured since 17 Sep. 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 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 69% of all ranked servers, and #197 of the solo servers (top 89%). 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 gap10.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 2

The first 48 hours of its last wipes

Tue 6 OctThu 17 SepTue 15 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 6 Oct, 10:53 UTC23d ago 1 NaN running 0
1 Thu 17 Sep, 10:39 UTC42d ago 1 halved by day 2 19 days 0
2 Tue 15 Sep, 00:57 UTC44d ago 1 held half 2.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

4000 · seed 3513435846
Map of Test Server
map
Procedural Map
size
4000
seed
3513435846
Open on RustMaps

Server

srv.info()
address
216.245.177.46:28015
region
–
max players
30
group limit
solo
wipe schedule
–
last wipe
6 Oct 2026, 10:53 UTC
hostname
–
first seen
13 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Rustafied.com - EU SoloEU · solo · weekly · 118 on average318/325
1Rustafied.com - US SoloNA · solo · weekly · 104 on average36/100
2RustForNoobs.com | Mondays | SOLO ONLY | EUEU · solo · weekly · 54 on average52/100
3RustForNoobs.com | SOLO ONLY | Weekly | EU 29/10 29.10EU · solo · weekly · 48 on average170/180
4Lone Wolf Rust | Solo Only, Monthly, Vanilla, No BP WipesNA · solo · monthly · 35 on average38/100
5[JP][日本] Bocchi The Rust! |SOLO ONLY| 1人 ソロ用 10/23EA · solo · weekly · 35 on average9/100

Quick answers

From the figures on this page.

Population

How does Test Server compare in the rankings?

Player hours over seven days put Test Server at #15,327, in the top 69% of the ranked set. The solo group places it at #197.

What population does Test Server carry?

The sample now reads 0 players for Test Server, out of 30 slots. Over the last seven days it averaged 0 players.

Server facts

How well does Test Server perform?

Server fps over the last 48 hours averages 96; the floor is 76. Buildings, deployables and all else in the world took the count as high as 88,323 entities. A high of 5,624 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does Test Server run?

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

How reliable is Test Server, and is it online now?

Test Server reports itself online at the current refresh. A restart about 17 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 13 September 2026.

In which location is Test Server hosted?

For Test Server, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 216.245.177.46:28015.

Settings and map

What rules and settings are recorded for Test Server?

No gather rate appears in the name: Test Server. This server is solo only, with no teams. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Community is its browser category. Anti-cheat status: VAC on.

What is the map on Test Server?

Test Server runs a procedural map of size 4,000 with seed 3513435846, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

On what schedule does Test Server wipe?

No next wipe can be predicted for Test Server, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 23 days 6 hours ago, and that is the one in play.

On Test Server, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 28 hours after it began. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. Otherwise the crowd fell below half by day 2.

Lists and tags

Which lists on Rust Data hold Test Server, and which filters?

On Rust Data, Test Server appears in these lists: Rust community servers, unfiltered and Solo Rust servers, group limit 1. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: Solo.

Which meanings do the tags on Test Server hold?

These tags are published by Test Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp30 (Max players): Slot count: 30; ts1 (Group limit): Team size tops out at 1; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not 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 to join Test Server?

In Rust, F1 opens the console: type client.connect 216.245.177.46: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 mp30,ptrak,$r?,v2634,gmrust,cs166652,ts1

Game

gmrust
Game mode Rust survival in its standard form.
mp30
Max players Slot count: 30.
ts1
Group limit Team size tops out at 1.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs166652
Build Recorded game build: 166652.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not 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 102,314 players 11,909 servers online