Rust Data

rustdata.spaceservers94.240.163.109:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 94.240.163.109:28015 checked 22d ago

TEST

Connect

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

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak –
rank #13,746 # top 62%
last wipe 22d 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
15k10k15k20k7 Oct8 Oct10 Oct11 Oct13 Oct14 Oct

Top 62% 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.240.163.109:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
7 Oct 2026, 10:50 UTC
hostname
–
first seen
7 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 · 503 on average159/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average188/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 282 on average587/675
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 277 on average35/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average681/775
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 245 on average554/625

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does TEST rank?

Player hours over seven days put TEST at #13,746, in the top 62% of the ranked set.

What population does TEST carry?

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

Server data

Which Rust version is TEST on?

The build is Rust network protocol 2634 and build 167058 on Windows, run by TEST. Joining needs the same protocol on your game; Steam handles the update.

How reliable is TEST, and is it online now?

The latest sample has TEST offline, with a last sighting 22 days 11 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 7 October 2026.

Which location does TEST run from?

No region is published by TEST. Rust Data does not look up where the machine stands; it shows where a server says it is. 94.240.163.109:28015 is its address.

Settings and map

Which rules apply on TEST, and what settings?

No gather rate appears in the name: TEST. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

What is the map on TEST?

TEST runs a procedural map, which the game generates.

Wipe data

On what schedule does TEST wipe?

The record for TEST holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 22 days 12 hours ago.

Lists and tags

Where does TEST appear among Rust Data lists and filters?

These Rust Data lists include TEST: 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 TEST?

These tags are published by TEST and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167058 (Build): Build number: 167058; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not 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

How can I connect to TEST?

In Rust, F1 opens the console: type client.connect 94.240.163.109: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,cs167058,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players The server lists 10 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167058
Build Build number: 167058.
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 74,585 players 11,767 servers online