Rust Data

rustdata.spaceservers60.56.65.96:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 60.56.65.96:28015 checked 26d ago

TestServer

Connect

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

Right now

srv.summary()
players now 1/1 # 100% full
7-day average 0 # peak –
rank #13,818 # top 60%
last wipe 27d 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
15k10k15k20k1 Oct3 Oct4 Oct6 Oct7 Oct9 Oct

Top 60% 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
60.56.65.96:28015
region
–
max players
1
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 22:12 UTC
hostname
–
first seen
1 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 · 555 on average145/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average122/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average12/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 286 on average21/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average12/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 250 on average23/200

Quick answers

From the figures on this page.

Population

What position does TestServer take in the server rankings?

Rank #13,818 on seven-day player hours for TestServer, within the top 60% of all ranked servers.

How full does TestServer run?

TestServer returns no live count at this refresh, having last been seen 26 days 11 hours ago.

Server data

What Rust version does TestServer run?

The build is Rust network protocol 2634 and build 166494 on Windows, run by TestServer. Joining needs the same protocol on your game; Steam handles the update.

How reliable is TestServer, and is it up?

The latest sample has TestServer offline, with a last sighting 26 days 11 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 1 October 2026.

Which location does TestServer run from?

For TestServer, 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. 60.56.65.96:28015 is its address.

Settings and map

Which rules apply on TestServer, and what settings?

No gather rate appears in the name: TestServer. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has TestServer loaded?

The game generates its map: procedural, on TestServer.

Wipes and dates

When does TestServer wipe, and how often?

A rhythm cannot be read from the wipes of TestServer on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 27 days 5 hours ago, and that is the one in play.

Tags, lists

Which Rust Data filters and lists contain TestServer?

These Rust Data lists include TestServer: 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.

How should you read the server tags on TestServer?

The game's server browser reads these tags from TestServer: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166494 (Build): Build number: 166494; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

How can I connect to TestServer?

Enter client.connect 60.56.65.96:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp1,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp1
Max players The server lists 1 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs166494
Build Build number: 166494.
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 33,246 players 11,665 servers online