RUST METRICSFlight deck · live data
Data live Servers11,840 Players80,134 Populated3,897 Fresh wipes 3 h160 Scan5 min
‹ All servers169.1.203.43:28015
Offline Full Queue Fresh wipe Wipe due No query

Phoenix`s server

Offline 169.1.203.43:28015 checked 12h ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average1peak 1
Rank#6,857top 31%
Last wipe16d agono schedule published
Next wipe–too few wipes seen yet
Memory–48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75107:0010:0013:0016:0019:0008:00

Hourly average and peak, UTC.

REC 2

Server performance

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct9 Oct13 Oct18 Oct22 Oct27 Oct

Top 31% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 11 Oct, 09:27 UTC16d ago 2 – running 0

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on Phoenix`s server when wipe day comes?

An average of 2 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 1 hours.

How often does Phoenix`s server wipe, and when?

To tell the rhythm of Phoenix`s server, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 16 days 11 hours ago.

Tags

Which tags does Phoenix`s server carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from Phoenix`s server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Phoenix`s server appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Phoenix`s server: Rust community servers: live readings. 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.

Occupancy

What position does Phoenix`s server hold among Rust servers?

Ranking for Phoenix`s server: #6,857 on seven-day player hours, top 31% of all ranked servers.

What player count does Phoenix`s server carry?

Phoenix`s server is not responding; status offline, last seen 12 hours ago. Check: players over seven days. Average 1, peak 1. The last 48 hours peaked at 09:00 UTC, averaging 1 players at that hour.

Operator and location

Which location does Phoenix`s server run from?

No region tag on Phoenix`s server. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 169.1.203.43:28015.

What Rust version is Phoenix`s server on?

Rust network protocol 2635 and build 168909 on Windows is the build Phoenix`s server runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Phoenix`s server, and is it online?

Check: connection. Phoenix`s server is offline at this moment. Last contact was 12 hours ago. Reading: 10% uptime over the last 7 full days. It was up 16 of 168 hours. Check: first contact. Rust Metrics logged it on 4 October 2026.

Map and rules

How is Phoenix`s server configured, and what rules are in force?

No gather rate appears in the name: Phoenix`s server. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is Phoenix`s server on?

The game generates a procedural map for Phoenix`s server.

Join

How can you get onto Phoenix`s server?

To join: start Rust, press F1 and type client.connect 169.1.203.43:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players Slots: 500.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.