Rust Data

rustdata.spaceservers94.134.192.41:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 94.134.192.41:28015 checked 22d ago

TestServer

Connect

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

Right now

srv.summary()
players now 1/5 # 20% full
7-day average 0 # peak –
rank #13,792 # top 61%
last wipe 25d 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
15k10k15k20k5 Oct6 Oct8 Oct9 Oct11 Oct12 Oct

Top 61% 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.41:28015
region
–
max players
5
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 07:33 UTC
hostname
–
first seen
5 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 · 504 on average780/825
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 345 on average47/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 340 on average124/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 314 on average412/500
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 280 on average247/300
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 259 on average190/300

Quick answers

From the figures on this page.

Population data

What position does TestServer take in the server rankings?

Player hours over seven days put TestServer at #13,792, in the top 61% of the ranked set.

What population does TestServer carry?

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

Server facts

What Rust version does TestServer run?

Rust network protocol 2634 and build 166652 on Windows is what TestServer runs. 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 22 days 2 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 5 October 2026.

Where does TestServer sit?

No region is published by TestServer. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 94.134.192.41:28015.

Map and rules

Which rules apply on TestServer, and what settings?

You will not find a gather rate in the string TestServer. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has TestServer selected?

The game generates its map: procedural, on TestServer.

Wipe schedule

When does TestServer wipe, and how often?

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. A new world was started 25 days 12 hours ago, and that is the one in play.

Tags and filters

Where does TestServer appear among Rust Data lists and filters?

The Rust Data lists that TestServer fits are: Rust community servers, unfiltered. It appears under these filters 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 TestServer?

These tags are published by TestServer and read by the game's server browser: 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; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

How can I connect to TestServer?

Enter client.connect 94.134.192.41: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?,v2634,gmrust,cs166652,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.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs166652
Build Recorded game build: 166652.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

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 88,657 players 11,874 servers online