Rust Data

rustdata.spaceservers176.52.80.72:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 176.52.80.72:28015 checked 44d ago

Phoenix

Connect

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

Right now

srv.summary()
players now 1/500 # 0% full
7-day average 0 # peak –
rank None # score 0
last wipe 44d 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:28015
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 · 504 on average780/825
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 345 on average47/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 average412/500
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 280 on average247/300
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 259 on average190/300

Quick answers

From the figures on this page.

Population data

How many players does Phoenix hold at once?

The current row shows Phoenix offline; the last response was 44 days 7 hours ago.

About the server

What Rust version does Phoenix run?

The build is Rust network protocol 2633 and build 163794 on Windows, run by Phoenix. The protocol has to match before you can join, and Steam does the updating.

How reliable is Phoenix, and is it up?

Phoenix is offline at this refresh; the last response came 44 days 7 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 13 September 2026.

In which location is Phoenix hosted?

There is no region published for Phoenix. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 176.52.80.72:28015 is its address.

Settings and map

Which rules apply on Phoenix, and what settings?

No gather rate appears in the name: Phoenix. 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. Community is its browser category. VAC is running: Valve's anti-cheat is on.

Which map has Phoenix selected?

Phoenix runs a procedural map, which the game generates.

Wipes and dates

On what schedule does Phoenix wipe?

Too few wipes are on record for Phoenix to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 44 days 11 hours ago.

Tags, lists

Which Rust Data filters and lists contain Phoenix?

These Rust Data lists include Phoenix: 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?

The game's server browser reads these tags from Phoenix: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): 500 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): Recorded game build: 163794; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not 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.

Connecting

How can I connect to Phoenix?

In Rust, F1 opens the console: type client.connect 176.52.80.72:28015. 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 Team limit of 8, as shipped by default.
v2633
Protocol The server speaks protocol 2633, so match your game version.
cs163794
Build Recorded game build: 163794.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not 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 88,657 players 11,874 servers online