Rust Data

rustdata.spaceservers195.78.100.186:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 195.78.100.186:28015 checked 40d ago

TEST

Connect

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

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak –
rank #13,273 # 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 Sep25 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
195.78.100.186:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
18 Sep 2026, 14:53 UTC
hostname
–
first seen
18 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 · 553 on average510/575
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average340/400
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 297 on average39/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 296 on average36/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 272 on average109/150
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average125/200

Quick answers

From the figures on this page.

Player counts

How does TEST compare in the rankings?

Over the last seven days TEST sits at #13,273 on player hours, in the top – of ranked servers.

What population does TEST carry?

Offline now for TEST, with the last sample 40 days 3 hours ago.

Server data

What is the Rust version on TEST?

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.

Is TEST up, and what does its uptime show?

TEST is offline at this refresh; the last response came 40 days 3 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 18 September 2026.

Which location does TEST run from?

For TEST, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 195.78.100.186:28015 is its address.

Map and rules

What rules and settings are recorded for TEST?

No gather rate appears in the name: TEST. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. 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 TEST loaded?

A procedural map runs on TEST, generated by the game.

Wipe data

When does TEST wipe, and on what schedule?

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

Tags and filters

Where does TEST appear among Rust Data lists and filters?

The Rust Data lists that TEST fits are: 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?

These tags are published by TEST and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs164530 (Build): Build number: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way to join TEST?

The manual route: launch Rust, F1, then client.connect 195.78.100.186:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players Slot count: 10.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2633
Protocol Protocol 2633 is required; a different game version cannot connect.
cs164530
Build Build number: 164530.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is 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 70,703 players 11,802 servers online