Rust Data

rustdata.spaceservers95.170.182.48:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 95.170.182.48:28015 checked 40d ago

TEST

Connect

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

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak –
rank #13,285 # no region published
last wipe 40d 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep

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.170.182.48:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
17 Sep 2026, 16:46 UTC
hostname
–
first seen
17 Sep 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 · 533 on average233/250
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 325 on average14/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 323 on average19/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average143/200
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 278 on average41/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average40/100

Quick answers

From the figures on this page.

Population data

How does TEST compare in the rankings?

Player hours over seven days put TEST at #13,285, in the top – of the ranked set.

How many players does TEST hold at once?

The current row shows TEST offline; the last response was 40 days 11 hours ago.

Server data

What Rust version does TEST run?

The build is Rust network protocol 2633 and build 164530 on Windows, run by TEST. Steam updates your game for you, but the protocol must match to join.

How reliable is TEST, and is it up?

TEST is offline at this refresh; the last response came 40 days 11 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 17 September 2026.

Which location does TEST run from?

No region is published by TEST. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 95.170.182.48:28015 is its address.

Map and rules

Which settings and rules does TEST run?

No gather rate appears in the name: TEST. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Community is its browser category. Anti-cheat status: VAC on.

Which map has TEST selected?

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. 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 40 days 12 hours ago.

Tags and filters

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

On Rust Data, TEST appears in these lists: 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?

The game's server browser reads these tags from TEST: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs164530 (Build): The server runs build 164530; 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.

Join steps

What is the way into TEST?

In Rust, F1 opens the console: type client.connect 95.170.182.48: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?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players 10 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol Protocol 2633 is required; a different game version cannot connect.
cs164530
Build The server runs build 164530.
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 34,643 players 11,595 servers online