Rust Data

rustdata.spaceservers5.215.61.217:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 5.215.61.217:28015 checked 21d ago

hoagaming-test

Connect

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

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,955 # top 72%
last wipe 22d 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
15k10k15k20k6 Oct8 Oct9 Oct11 Oct12 Oct14 Oct

Top 72% 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
5.215.61.217:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
6 Oct 2026, 09:19 UTC
hostname
–
first seen
6 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 · 542 on average145/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average131/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average15/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 283 on average19/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average16/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 249 on average46/200

Quick answers

From the figures on this page.

Population data

How does hoagaming-test compare in the rankings?

Over the last seven days hoagaming-test sits at #15,955 on player hours, in the top 72% of ranked servers.

How full does hoagaming-test run?

Offline now for hoagaming-test, with the last sample 21 days 16 hours ago.

Server data

What Rust version does hoagaming-test run?

Rust network protocol 2634 and build 166652 on Windows is what hoagaming-test runs. Steam updates your game for you, but the protocol must match to join.

Is hoagaming-test up, and what does its uptime show?

Offline now for hoagaming-test, last seen 21 days 16 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 6 October 2026.

In which location is hoagaming-test hosted?

No region is published by hoagaming-test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 5.215.61.217:28015.

Settings and map

What rules and settings are recorded for hoagaming-test?

The name hoagaming-test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. 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 hoagaming-test?

hoagaming-test runs a procedural map, which the game generates.

Wipes and dates

When does hoagaming-test wipe, and how often?

A rhythm cannot be read from the wipes of hoagaming-test 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. This world was created 22 days 19 hours ago.

Lists and tags

Where does hoagaming-test appear among Rust Data lists and filters?

The Rust Data lists that hoagaming-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.

How should you read the server tags on hoagaming-test?

These tags are published by hoagaming-test and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way to join hoagaming-test?

Enter client.connect 5.215.61.217: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 mp50,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players The server lists 50 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol To join, your game must run protocol 2634.
cs166652
Build The server runs build 166652.
ptrak
Networking Standard network layer for Rust: RakNet.
$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 31,131 players 11,626 servers online