Rust Data

rustdata.spaceservers2.26.17.28:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 2.26.17.28:28015 checked 18d ago

TEST

Connect

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

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak –
rank #14,202 # top 64%
last wipe 23d 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
15k10k15k20k4 Oct6 Oct9 Oct11 Oct14 Oct16 Oct

Top 64% 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
2.26.17.28:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
5 Oct 2026, 01:27 UTC
hostname
–
first seen
4 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 · 552 on average636/675
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average485/525
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 299 on average59/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 298 on average36/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 270 on average138/200
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 256 on average255/300

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does TEST rank?

Rank #14,202 on seven-day player hours for TEST, within the top 64% of all ranked servers.

How many players does TEST hold at once?

Offline now for TEST, with the last sample 18 days 23 hours ago.

Server facts

Which Rust version is TEST on?

Version Rust network protocol 2634 and build 166652 on Windows is reported by TEST. Steam updates your game for you, but the protocol must match to join.

How reliable is TEST, and is it up?

The latest sample has TEST offline, with a last sighting 18 days 23 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 4 October 2026.

Which location does TEST run from?

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

Map and rules

Which settings and rules does TEST run?

You will not find a gather rate in the string TEST. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.

Which map has TEST selected?

TEST runs a procedural map, which the game generates.

Wipe data

When does TEST wipe, and on what schedule?

Too few wipes are on record for TEST to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 23 days 17 hours ago.

Tags, lists

Where does TEST appear among Rust Data lists and filters?

On Rust Data, TEST appears in these lists: Rust community servers, unfiltered. These filters bring it up 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?

Read by the game's server browser, the tags TEST publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $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 to join TEST?

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

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players The server lists 10 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs166652
Build Build number: 166652.
ptrak
Networking The network layer is RakNet, standard for the game.
$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 89,289 players 11,829 servers online