Rust Data

rustdata.spaceservers176.52.80.72:28018.ipynb

Run all rust-data · live

‹ All servers

Offline 176.52.80.72:28017 checked 45d ago

Phoenix Server

Connect

srv = rust.server("176.52.80.72:28018")
print(srv.connect_command)

Right now

srv.summary()
players now 0/500 # 0% full
7-day average 0 # peak –
rank None # score 0
last wipe 45d 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
No rank history yet.

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
176.52.80.72:28017
region
–
max players
500
group limit
8, the default
wipe schedule
–
last wipe
13 Sep 2026, 09:02 UTC
hostname
–
first seen
13 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 · 550 on average636/675
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average485/525
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 300 on average59/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 300 on average36/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 269 on average138/200
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 257 on average255/300

Quick answers

From the figures on this page.

Player counts

How full does Phoenix Server run?

Phoenix Server returns no live count at this refresh, having last been seen 45 days 5 hours ago.

Server facts

What is the Rust version on Phoenix Server?

Rust network protocol 2633 and build 163794 on Windows is what Phoenix Server runs. Steam updates your game for you, but the protocol must match to join.

How reliable is Phoenix Server, and is it online now?

The latest sample has Phoenix Server offline, with a last sighting 45 days 5 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Which location does Phoenix Server run from?

For Phoenix Server, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 176.52.80.72:28017.

Map and rules

Which settings and rules does Phoenix Server run?

The name Phoenix Server carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Community is its browser category. VAC, Valve's anti-cheat, is enabled.

What is the map on Phoenix Server?

The game generates its map: procedural, on Phoenix Server.

Wipe data

On what schedule does Phoenix Server wipe?

Too few wipes are on record for Phoenix Server to reveal its rhythm. 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 45 days 9 hours ago, and that is the one in play.

Lists and tags

Where does Phoenix Server appear among Rust Data lists and filters?

The Rust Data lists that Phoenix Server fits are: Rust community servers, unfiltered. It appears under these filters 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 Phoenix Server?

Read by the game's server browser, the tags Phoenix Server publishes are: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): 500 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs163794 (Build): Build number: 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way to join Phoenix Server?

In Rust, F1 opens the console: type client.connect 176.52.80.72:28017. 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?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp500
Max players 500 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2633
Protocol To join, your game must run protocol 2633.
cs163794
Build Build number: 163794.
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 89,289 players 11,829 servers online