Rust Data

rustdata.spaceservers94.134.192.101:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 94.134.192.101:28015 checked 26d ago

TestServer

Connect

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

Right now

srv.summary()
players now 0/5 # 0% full
7-day average 0 # peak –
rank #15,934 # top 70%
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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

Top 70% 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
94.134.192.101:28015
region
–
max players
5
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 07:33 UTC
hostname
–
first seen
2 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 · 514 on average434/500
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 317 on average457/475
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 281 on average981/1000
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 276 on average64/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average989/1000
5Rustoria.co - US MainNA · groups of 16+ · weekly · 236 on average23/250

Quick answers

From the figures on this page.

Population

How does TestServer compare in the rankings?

Over the last seven days TestServer sits at #15,934 on player hours, in the top 70% of ranked servers.

How full does TestServer run?

Offline now for TestServer, with the last sample 26 days 23 hours ago.

About the server

Which Rust version is TestServer on?

The build is Rust network protocol 2634 and build 166586 on Windows, run by TestServer. The protocol has to match before you can join, and Steam does the updating.

Is TestServer up, and what does its uptime show?

Offline now for TestServer, last seen 26 days 23 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 2 October 2026.

Where does TestServer sit?

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

Settings and map

What rules and settings are recorded for TestServer?

No gather rate appears in the name: TestServer. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

What is the map on TestServer?

TestServer runs a procedural map, which the game generates.

Wipe data

When does TestServer wipe, and on what schedule?

The record for TestServer holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 27 days 8 hours ago.

Tags and filters

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

These Rust Data lists include TestServer: 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): The server lists 5 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166586 (Build): Recorded game build: 166586; ptrak (Networking): Network traffic runs over RakNet, the game standard; $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.

Join steps

What is the way into TestServer?

The manual route: launch Rust, F1, then client.connect 94.134.192.101:28015. 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 mp5,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp5
Max players The server lists 5 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs166586
Build Recorded game build: 166586.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$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 95,389 players 11,875 servers online