Rust Data

rustdata.spaceservers162.19.95.79:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 162.19.95.79:28015 checked 10d ago

probe

Connect

srv = rust.server("162.19.95.79:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,321 # top 70%
last wipe 10d 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
15k10k15k20k18 Oct19 Oct21 Oct22 Oct24 Oct25 Oct

Top 70% 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
162.19.95.79:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
18 Oct 2026, 05:34 UTC
hostname
–
first seen
18 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 average586/675
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average372/525
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 299 on average49/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 298 on average38/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 271 on average130/200
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 254 on average144/300

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does probe rank?

Player hours over seven days put probe at #15,321, in the top 70% of the ranked set.

How full does probe run?

probe returns no live count at this refresh, having last been seen 10 days 14 hours ago.

Server facts

What is the Rust version on probe?

Rust network protocol 2634 and build 167781 on Linux is what probe runs. Steam updates your game for you, but the protocol must match to join.

How reliable is probe, and is it online now?

probe is offline at this refresh; the last response came 10 days 14 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 18 October 2026.

Where does probe sit?

For probe, no region is published. 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 162.19.95.79:28015.

Map and rules

What rules and settings are recorded for probe?

You will not find a gather rate in the string probe. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

What is the map on probe?

probe runs a procedural map, which the game generates.

Wipe data

When does probe wipe, and how often?

Too few wipes are on record for probe to reveal its 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 10 days 15 hours ago.

Tags and filters

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

These Rust Data lists include probe: 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 2 weeks.

Which meanings do the tags on probe hold?

Read by the game's server browser, the tags probe publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. 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 probe?

The manual route: launch Rust, F1, then client.connect 162.19.95.79: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?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players The server lists 10 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build The server runs build 167781.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

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 79,295 players 11,799 servers online