Rust Data

rustdata.spaceservers73.95.239.37:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 73.95.239.37:28015 checked 12d ago

Test

Connect

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

Right now

srv.summary()
players now 0/500 # 0% full
7-day average 0 # peak –
rank #15,180 # top 70%
last wipe 12d 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
15k10k15k20k16 Oct17 Oct19 Oct20 Oct22 Oct23 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
73.95.239.37:28015
region
–
max players
500
group limit
8, the default
wipe schedule
–
last wipe
16 Oct 2026, 18:50 UTC
hostname
–
first seen
16 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 average211/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average125/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average25/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 289 on average13/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average25/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 251 on average32/225

Quick answers

From the figures on this page.

Player counts

How does Test compare in the rankings?

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

How full does Test run?

Offline now for Test, with the last sample 12 days 4 hours ago.

Server facts

Which Rust version is Test on?

Version Rust network protocol 2634 and build 167781 on Windows is reported by Test. The protocol has to match before you can join, and Steam does the updating.

Is Test up, and what does its uptime show?

The latest sample has Test offline, with a last sighting 12 days 4 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 16 October 2026.

In which location is Test hosted?

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. 73.95.239.37:28015 is its address.

Map and rules

What rules and settings are recorded for Test?

The name Test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.

Which map has Test selected?

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

Wipe data

On what schedule does Test wipe?

A rhythm cannot be read from the wipes of Test on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 12 days 6 hours ago.

Tags and filters

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

The Rust Data lists that Test fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: 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 Test hold?

Read by the game's server browser, the tags Test publishes are: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): The server lists 500 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; 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.

Connecting

What is the way into Test?

In Rust, F1 opens the console: type client.connect 73.95.239.37: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 mp500,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp500
Max players The server lists 500 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol To join, your game must run protocol 2634.
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 42,340 players 11,701 servers online