Rust Data

rustdata.spaceservers95.26.41.95:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 95.26.41.95:28015 checked 3d ago

test

Connect

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

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,349 # top 69%
last wipe 3d 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
15k10k15k20k25 Oct26 Oct27 Oct28 Oct29 Oct

Top 69% 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
95.26.41.95:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
25 Oct 2026, 19:29 UTC
hostname
–
first seen
25 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 · 565 on average220/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average129/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average28/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 289 on average14/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average23/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 251 on average32/225

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does test rank?

Over the last seven days test sits at #15,349 on player hours, in the top 69% of ranked servers.

How many players does test hold at once?

test returns no live count at this refresh, having last been seen 3 days 3 hours ago. Over the last seven days it averaged 0 players.

Server facts

What Rust version does test run?

Rust network protocol 2635 and build 169082 on Windows is what test runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is test, and is it up?

test is offline at this refresh; the last response came 3 days 3 hours ago. Uptime of 0% across the last 3 full days: 0 hours of 72. Its earliest recorded date in Rust Data is 25 October 2026.

Where does test sit?

There is no region published for test. 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 95.26.41.95:28015.

Map and rules

Which settings and rules does test run?

The name test carries no gather rate. 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. Community is its browser category. Anti-cheat status: VAC on.

Which map has test loaded?

test runs a procedural map, which the game generates.

Wipes and dates

On what schedule does test wipe?

Too few wipes are on record for test to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 3 days 5 hours ago.

Lists and tags

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

The Rust Data lists that test 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; Last wipe: In the last week.

How should you read the server tags on test?

The game's server browser reads these tags from test: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs169082 (Build): Build number: 169082; ptrak (Networking): The network layer is RakNet, standard for the game; $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.

How to join

What is the way to join test?

In Rust, F1 opens the console: type client.connect 95.26.41.95: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?,v2635,gmrust,cs169082,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players Slot count: 10.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs169082
Build Build number: 169082.
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 43,388 players 11,713 servers online