RUST METRICSFlight deck · live data
Data live Servers11,875 Players95,389 Populated3,882 Fresh wipes 3 h387 Scan5 min
‹ All servers51.161.199.14:60409
Offline Full Queue Fresh wipe Wipe due No query

PhoenixGamers

Offline OC 51.161.199.14:60409 checked 34m ago

biweekly wipes moddedcarbon
COM 1 · connect

Server instruments

last reading Thu 14:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

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

Server fps

48 h low 27 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 71,982 ×1000

Entities

48 h range 66,985–74,812 · memory 2,618 MB
1239 ET SINCE RESTART 1D 20H

Uptime

1 days 20 hours since its last restart, at the last reading
7-day average0peak 1
Rank#13,589top 61% · #170 in OC
Last wipe1d agobiweekly schedule
Next wipe7d 2hThu 5 Nov, 19:00 UTC FW
Memory2,618MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75117:0002:0011:0020:0005:0014:00Wiped Tue 27 Oct, 18:02 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
05010015020017:0002:0011:0020:0005:0014:00Wiped Tue 27 Oct, 18:02 UTCWIPE

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, measured since 23 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k23 Sep30 Sep7 Oct15 Oct22 Oct29 Oct

Top 61% of all ranked servers, top 79% in OC. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 2h. The force wipe · high confidence

usual gap17.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 6.5

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 2hFW
  2. WPT 2Tue 10 Nov, 18:02 UTC12d 1h
  3. WPT 3Tue 24 Nov, 18:02 UTC26d 1h
  4. WPT 4Thu 3 Dec, 19:00 UTC35d 2hFW
  5. WPT 5Tue 8 Dec, 18:02 UTC40d 1h

The first 48 hours of its last wipes

Fri 2 OctWed 23 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 8 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 18:02 UTC1d ago – – running 1
Fri 2 Oct, 02:32 UTC27d ago 3 halved by day 12 25.6 days 2
Wed 23 Sep, 00:32 UTC36d ago 2 halved by day 1 9.1 days 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 PhoenixGamers when wipe day comes?

An average of 2 players came at the busiest on its recent wipes. 8 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell below half by day 6.5 when it didn't.

How often does PhoenixGamers wipe, and when?

Its tag guides the prediction: too few of PhoenixGamers's wipes are on record to confirm its schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world in play was created 46 hours ago. A wipe schedule of every two weeks is published in its tags.

Lists and filters

How should you read the tags on PhoenixGamers?

Tags published by PhoenixGamers, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^b (Biweekly): It wipes once a fortnight; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Plugin framework in use: Carbon; OC (Oceania): Oceania is the browser category it sits in. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does PhoenixGamers appear in Rust Metrics lists and filters?

Rust Metrics lists featuring PhoenixGamers: Rust servers in Oceania and Modded Rust servers, checked live. Reading: server list filters. It comes up under Region: Oceania; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 3 days.

Occupancy

What position does PhoenixGamers hold among Rust servers?

Ranked by seven-day player hours, PhoenixGamers sits at #13,589 and #170 in Oceania, inside the top 61%.

What player count does PhoenixGamers carry?

Reading for PhoenixGamers: offline at this moment; last seen 34 minutes ago. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 1 players, at 17:00 UTC over the last 48 hours.

Operator and location

Which location does PhoenixGamers run from?

Its OC tag places PhoenixGamers in Oceania. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 51.161.199.14:60409.

What Rust version is PhoenixGamers on?

Reading: PhoenixGamers, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.

How does PhoenixGamers perform?

Over the last 48 hours the average was 78 server fps; the floor was 27. Check: entities. The peak was 74,812, counting buildings, deployables and the rest of the world. Memory peak: 2,685 MB. What players call lag comes from low fps and an entity count on the rise.

How reliable is PhoenixGamers, and is it online now?

PhoenixGamers reports offline. The last reading came 34 minutes ago. Reading: uptime. About 44 hours ago it restarted, on its own count. Uptime for the last 7 full days: 31 of 168 hours, or 18%. Reading: first seen 23 September 2026, recorded by Rust Metrics.

Settings and map

What rules does PhoenixGamers enforce, and what are its settings?

Reading the name gives no gather rate for PhoenixGamers. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Carbon plugins are running. VAC is on. That is Valve's anti-cheat.

What map is PhoenixGamers on?

Size 3,500 and seed 1721170919: the game generates the procedural map on PhoenixGamers from them. View it on RustMaps from this page: matching size and seed give an identical map.

Join

How can you get onto PhoenixGamers?

Press F1 in Rust and enter client.connect 51.161.199.14:60409. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^z,^y,^b,OC,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^y
Carbon Plugin framework in use: Carbon.

Region

OC
Oceania Oceania is the browser category it sits in.

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.