StatusLive Servers online11,649 Players46,616 Populated3,134 Wiped · 3 h110 Interval5 min Date29 OCT 2026

DWG RG-S15338Server sheetchecked 14m ago

A Rust Server Phoenix

Online 168.100.161.9:28029 checked 14m ago

moddedoxide
Connect
Players now 0/ 10 0% full
7-day average0peak –
Rank#15,338top 69%
Last wipe27d agono schedule published
Next wipe–too few wipes seen yet
Fig. 1

Players

AveragePeak
0123409:0018:0003:0012:0022:0007:00

Hourly average and peak, UTC.

Fig. 1Players on A Rust Server Phoenix
Fig. 2

Server performance

025507510009:0018:0003:0012:0022:0007:00

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

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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.

usual gap4.9 daysbetween real wipes
wipe-day peak0players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Fri 2 OctSun 27 Sep
01234+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 04:02 UTC27d ago 0 – running 0
Sun 27 Sep, 06:56 UTC32d ago 1 halved by day 1 4.9 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 150 on average
106 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
132 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average
163 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average
50 / 700
05
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
5 / 200
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
22 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

What uptime is recorded for A Rust Server Phoenix, and is it up?

Right now, A Rust Server Phoenix is recorded as online. Counted from its reported uptime, the last restart was about 2 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. On 13 September 2026 is when Rust Graphs first saw it.

Is A Rust Server Phoenix stable in the figures recorded?

92 server fps on average over the last 48 hours, and never under 26. Counted at its highest: 122,430 entities, buildings, deployables and the rest of the world included. Memory use peaked at 3,135 MB. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for A Rust Server Phoenix?

A region is not published by A Rust Server Phoenix. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. It is reached at 168.100.161.9:28029.

What Rust version is recorded for A Rust Server Phoenix?

Rust network protocol 2635 and build 168909 on Linux: that is what A Rust Server Phoenix runs. To join, your game must be on the same protocol; Steam handles the update.

Player data

How many players are plotted on A Rust Server Phoenix?

Current player count on A Rust Server Phoenix: 0, of 10 slots. Averaged across seven days, the player count is 0.

What rank has been recorded for A Rust Server Phoenix?

Within the top 69% of all ranked servers: A Rust Server Phoenix at #15,338 for player hours, seven days recorded.

Schedules

What is recorded on A Rust Server Phoenix on wipe day?

The recent wipes averaged a busiest count of 0 players. At 0 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 0% of its recent wipes stayed above half that peak. In the other cases the crowd was below half by day 1.

Which times and days are wipes plotted at on A Rust Server Phoenix?

A Rust Server Phoenix's rhythm cannot be told yet: too few of its wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The current world has been in use since 27 days 4 hours ago.

Rules and settings

Which settings does A Rust Server Phoenix run, and what rules?

No gather rate is stated in the name of A Rust Server Phoenix. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is on.

What is the map for A Rust Server Phoenix?

A Rust Server Phoenix runs a procedural map of size 4,750 with seed 1337, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. The name of the map reads: Custom Map.

Lists and filters

On Rust Graphs, which lists and filters contain A Rust Server Phoenix?

The Rust Graphs lists that carry A Rust Server Phoenix are: Modded Rust servers. On the server list, these filters bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

On A Rust Server Phoenix, what is meant by each tag?

The game's server browser reads these tags from A Rust Server Phoenix: gmrust (Game mode): Survival in standard Rust style; mp10 (Max players): Slots: 10; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): 168909 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

How to join

By what method do you join A Rust Server Phoenix?

Connect with client.connect 168.100.161.9:28029: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust style.
mp10
Max players Slots: 10.
ts8
Group limit The default team size of 8 applies.
v2635
Protocol Your game must match protocol 2635 to join.
cs168909
Build 168909 is the game build.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The region code field is empty.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is 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.

KeyTag string decoded