RUST METRICSFlight deck · live data
Data live Servers11,761 Players76,398 Populated3,723 Fresh wipes 3 h138 Scan5 min
‹ All servers68.117.72.243:28083
Offline Full Queue Fresh wipe Wipe due No query

Phoenix Testing Server [DEV]

Offline 68.117.72.243:28083 checked 26d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

Players now

0% full 7-day avg
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 average0peak –
Rank#15,922top 69%
Last wipe49d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

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
15k10k15k20k20 Sep24 Sep28 Sep1 Oct5 Oct9 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
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.

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 schedule

What wipe timing does Phoenix Testing Server [DEV] follow?

Its rhythm cannot be told from the wipes of Phoenix Testing Server [DEV] on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 49 days 12 hours ago the current world was made.

Lists and filters

How should you read the tags on Phoenix Testing Server [DEV]?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): 5 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163493 (Build): Game build reading: 163493; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game from Phoenix Testing Server [DEV]. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Phoenix Testing Server [DEV]?

These Rust Metrics lists carry Phoenix Testing Server [DEV]: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

Where does Phoenix Testing Server [DEV] sit in the rankings?

Player hours over seven days put Phoenix Testing Server [DEV] at #15,922, in the top 69% of all ranked servers.

How full does Phoenix Testing Server [DEV] get?

Status for Phoenix Testing Server [DEV]: offline. Last seen 26 days 6 hours ago.

Server

Where does Phoenix Testing Server [DEV] sit?

No region comes from Phoenix Testing Server [DEV]. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 68.117.72.243:28083.

What Rust version is Phoenix Testing Server [DEV] on?

Reading: Phoenix Testing Server [DEV], Rust network protocol 2633 and build 163493, Windows. Matching protocol is required to join. Let Steam update your game.

Is Phoenix Testing Server [DEV] up, and how often does it stay up?

Phoenix Testing Server [DEV] reports offline. The last reading came 26 days 6 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

What settings and rules apply on Phoenix Testing Server [DEV]?

No gather rate appears in the name: Phoenix Testing Server [DEV]. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Phoenix Testing Server [DEV]?

The game generates a procedural map for Phoenix Testing Server [DEV].

How to join

What do you do to join Phoenix Testing Server [DEV]?

Check: join. Open Rust, press F1, then enter client.connect 68.117.72.243:28083. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2633,gmrust,cs163493,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players 5 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163493
Build Game build reading: 163493.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

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.