Rust Data

rustdata.spaceservers168.100.161.9:28026.ipynb

Run all rust-data · live

‹ All servers

Online 168.100.161.9:28029 checked 11m ago

A Rust Server Phoenix

moddedoxide

Connect

srv = rust.server("168.100.161.9:28026")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,358 # top 69%
last wipe 26d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123404:0013:0022:0007:0016:0002:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
025507510004:0013:0022:0007:0016:0002: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 04:02 UTC26d ago 0 NaN running 0
1 Sun 27 Sep, 06:56 UTC31d 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.

display(srv.map, srv.info())

Map

4750 · seed 1337
Map of A Rust Server Phoenix
map
Custom Map
size
4750
seed
1337

Server

srv.info()
address
168.100.161.9:28029
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 04:02 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 154 on average26/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average130/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average35/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average11/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average3/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average1/1000

Quick answers

From the figures on this page.

Population

How does A Rust Server Phoenix compare in the rankings?

Rank #15,358 on seven-day player hours for A Rust Server Phoenix, within the top 69% of all ranked servers.

How full does A Rust Server Phoenix run?

A Rust Server Phoenix reports 0 players at this refresh, with 10 slots configured. Over the last seven days it averaged 0 players.

Server data

How well does A Rust Server Phoenix perform?

Averaged over 48 hours: 91 server fps, never under 26. Buildings, deployables and all else in the world took the count as high as 122,430 entities. A high of 3,135 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does A Rust Server Phoenix run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by A Rust Server Phoenix. The protocol has to match before you can join, and Steam does the updating.

How reliable is A Rust Server Phoenix, and is it online now?

Online is the state at the latest refresh for A Rust Server Phoenix. Count back 21 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 13 September 2026.

Where does A Rust Server Phoenix sit?

No region is published by A Rust Server Phoenix. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 168.100.161.9:28029.

Rules, settings, map

Which rules apply on A Rust Server Phoenix, and what settings?

You will not find a gather rate in the string A Rust Server Phoenix. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

Which map has A Rust Server Phoenix selected?

A Rust Server Phoenix runs a procedural map of size 4,750 with seed 1337, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Recorded under map name: Custom Map.

Wipe data

When does A Rust Server Phoenix wipe, and how often?

The record for A Rust Server Phoenix holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 26 days 23 hours ago.

On A Rust Server Phoenix, what happens on wipe day?

Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The drop under half arrived by day 1 in the other cases.

Tags and filters

Which lists on Rust Data hold A Rust Server Phoenix, and which filters?

On Rust Data, A Rust Server Phoenix appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on A Rust Server Phoenix?

Read by the game's server browser, the tags A Rust Server Phoenix publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way to join A Rust Server Phoenix?

The manual route: launch Rust, F1, then client.connect 168.100.161.9:28029. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players 10 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the 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.

Rust Data 34,137 players 11,669 servers online