Rust Data

rustdata.spaceservers188.47.5.97:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 188.47.5.97:28015 checked 30d ago

TEST

Connect

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

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak –
rank #15,922 # top 67%
last wipe 30d 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
15k10k15k20k27 Sep28 Sep30 Sep1 Oct3 Oct4 Oct

Top 67% 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
188.47.5.97:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
27 Sep 2026, 09:55 UTC
hostname
–
first seen
27 Sep 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 · 535 on average336/350
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 320 on average11/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 319 on average22/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average148/225
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 277 on average85/225
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 265 on average33/100

Quick answers

From the figures on this page.

Population data

What position does TEST take in the server rankings?

Rank #15,922 on seven-day player hours for TEST, within the top 67% of all ranked servers.

How many players does TEST hold at once?

TEST returns no live count at this refresh, having last been seen 30 days 19 hours ago.

About the server

Which Rust version is TEST on?

Rust network protocol 2633 and build 165217 on Windows is what TEST runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is TEST, and is it up?

Offline now for TEST, last seen 30 days 19 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 27 September 2026.

In which location is TEST hosted?

For TEST, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 188.47.5.97:28015.

Settings and map

Which rules apply on TEST, and what settings?

The name TEST carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Community is its browser category. VAC is running: Valve's anti-cheat is on.

What is the map on TEST?

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

Wipes and dates

When does TEST wipe, and on what schedule?

A rhythm cannot be read from the wipes of TEST on record, which are too few. 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 30 days 21 hours ago.

Tags and filters

Where does TEST appear among Rust Data lists and filters?

On Rust Data, TEST appears in these lists: 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.

Which meanings do the tags on TEST hold?

Read by the game's server browser, the tags TEST publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. 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 TEST?

The manual route: launch Rust, F1, then client.connect 188.47.5.97: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?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players 10 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol The server speaks protocol 2633, so match your game version.
cs165217
Build Recorded game build: 165217.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$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 40,450 players 11,620 servers online