Rust Data

rustdata.spaceservers2.63.180.36:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 2.63.180.36:28015 checked 20d ago

TEST SERVER

Connect

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

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,967 # top 71%
last wipe 24d 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
15k10k15k20k3 Oct5 Oct7 Oct9 Oct11 Oct13 Oct

Top 71% 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
2.63.180.36:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
3 Oct 2026, 11:13 UTC
hostname
–
first seen
3 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 · 504 on average781/825
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 345 on average43/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 340 on average124/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 314 on average407/500
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 280 on average260/300
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 259 on average193/300

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does TEST SERVER rank?

Over the last seven days TEST SERVER sits at #15,967 on player hours, in the top 71% of ranked servers.

How full does TEST SERVER run?

The current row shows TEST SERVER offline; the last response was 20 days 21 hours ago.

About the server

Which Rust version is TEST SERVER on?

Version Rust network protocol 2634 and build 166652 on Windows is reported by TEST SERVER. Steam updates your game for you, but the protocol must match to join.

How reliable is TEST SERVER, and is it up?

TEST SERVER is offline at this refresh; the last response came 20 days 21 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 3 October 2026.

Which location does TEST SERVER run from?

For TEST SERVER, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 2.63.180.36:28015 is its address.

Settings and map

What rules and settings are recorded for TEST SERVER?

No gather rate appears in the name: TEST SERVER. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. 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 SERVER loaded?

TEST SERVER runs a procedural map, which the game generates.

Wipes and dates

When does TEST SERVER wipe, and how often?

A rhythm cannot be read from the wipes of TEST SERVER 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. The world it runs now was generated 24 days 8 hours ago.

Lists and tags

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

The Rust Data lists that TEST SERVER 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 SERVER?

Read by the game's server browser, the tags TEST SERVER publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $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

What is the way to join TEST SERVER?

The manual route: launch Rust, F1, then client.connect 2.63.180.36: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 mp100,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players The server lists 100 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs166652
Build Recorded game build: 166652.
ptrak
Networking The network layer is RakNet, standard for the game.
$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 90,661 players 11,897 servers online