Rust Server TrendsSeismic network · station log
Recording Stations11,654 Players43,996 Active2,908 Wipes · 3 h99 48 h

Station XX-15922 · no signal

Phoenix Testing Server [DEV]

Offline 68.117.72.243:28083 checked 27d ago

moddedoxide
Connect
Players now
0/ 5
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,922
top 69%
Last wipe
51d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15922 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 5 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 151 on average
20/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
130/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 122 on average
38/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 97 on average
7/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 94 on average
22/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
107/ 200
Readings, in words

Quick answers

from the figures on this page

Map and rules

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

The map on Phoenix Testing Server [DEV] is procedural, produced by the game.

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

No gather rate appears in the name of Phoenix Testing Server [DEV]. Groups hold up to 8 players, which is the default for the game. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.

Live population

How many players are recorded on Phoenix Testing Server [DEV] right now?

No players are recorded on Phoenix Testing Server [DEV] at this moment; it is offline, and the last sighting was 27 days 19 hours ago.

How does Phoenix Testing Server [DEV] rank against other Rust servers?

On player hours for the past week, Phoenix Testing Server [DEV] sits at #15,922, which puts it inside the top 69% of every ranked server.

Server facts

How reliably does Phoenix Testing Server [DEV] stay online?

No contact with Phoenix Testing Server [DEV] right now, and the last recorded contact was 27 days 19 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 13 September 2026 is when Rust Server Trends first recorded it.

Where in the world is Phoenix Testing Server [DEV] hosted?

A region is not published by Phoenix Testing Server [DEV]. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 68.117.72.243:28083.

What build of Rust does Phoenix Testing Server [DEV] use?

Rust network protocol 2633 and build 163493 on Windows is what Phoenix Testing Server [DEV] runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

On what timetable does Phoenix Testing Server [DEV] run its wipes?

The rhythm of Phoenix Testing Server [DEV] cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 51 days 1 hours.

Server tags

What do the server tags on Phoenix Testing Server [DEV] mean?

These are the tags Phoenix Testing Server [DEV] publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp5 (Max players): 5 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs163493 (Build): It runs game build 163493; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Phoenix Testing Server [DEV] appear?

You will find Phoenix Testing Server [DEV] on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

How do you connect to Phoenix Testing Server [DEV]?

You can connect by pressing F1 in Rust and typing client.connect 68.117.72.243:28083 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp5
Max players 5 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs163493
Build It runs game build 163493.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.