Rust Data

rustdata.spaceservers139.99.22.23:29589.ipynb

Run all rust-data · live

‹ All servers

Online 139.99.22.23:29588 checked 10m ago

[SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip

2x weekly wipes vanillamoddedoxide

Connect

srv = rust.server("139.99.22.23:29589")
print(srv.connect_command)

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 0 # peak 2
rank #5,810 # top 26%
last wipe 2d ago # weekly schedule
next wipe 4d 21h # Tue 3 Nov, 09:50 UTC
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5213:0022:0007:0015:0001:0010:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040013:0022:0007:0015:0001:0010: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 13 Oct. 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
12.5k5k7.5k10k13 Oct16 Oct19 Oct23 Oct26 Oct29 Oct

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

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Tuesday 3 November, 09:50 UTC, in 4d 21h. # Its weekly schedule tag · low confidence

usual gap1.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd

Coming wipes

inatkind
04d 21hTue 3 Nov, 09:50 UTCwipe
17d 6hThu 5 Nov, 19:00 UTCFW force wipe
211d 21hTue 10 Nov, 09:50 UTCwipe
318d 21hTue 17 Nov, 09:50 UTCwipe
425d 21hTue 24 Nov, 09:50 UTCwipe
532d 21hTue 1 Dec, 09:50 UTCwipe
635d 6hThu 3 Dec, 19:00 UTCFW force wipe
739d 21hTue 8 Dec, 09:50 UTCwipe

The first 48 hours of its last wipes

Tue 27 OctThu 22 OctThu 22 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 27 Oct, 09:50 UTC2d ago 2 NaN running 0
1 Thu 22 Oct, 18:52 UTC6d ago 2 held half 4.6 days 0
2 Thu 22 Oct, 09:43 UTC7d ago 2 NaN 0.4 days 1
3 Sat 17 Oct, 13:37 UTC11d ago 3 held half 4.8 days 0
4 Fri 16 Oct, 07:05 UTC13d ago 3 NaN 1.3 days 0
5 Thu 15 Oct, 17:07 UTC13d ago 2 NaN 0.6 days 1
6 Tue 13 Oct, 14:38 UTC15d ago 3 held half 2.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.

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

Map

3500 · seed 564262858
Map of [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip
map
Procedural Map
size
3500
seed
564262858
Open on RustMaps

Server

srv.info()
address
139.99.22.23:29588
region
–
max players
40
group limit
8, the default
wipe schedule
weekly
last wipe
27 Oct 2026, 09:50 UTC
hostname
–
first seen
13 Oct 2026

About this server · in its own words

print(srv.description)
No cheatingg No hack Play fair and respect all player Server restart daily at times 05:00 AM 10:00AM 02:00PM 07:00PM 12:30AM ( midnight ) This schedule repeats every day. Please secure your items and make sure you are in a safe place before each restart.

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

rust.similar(srv).head(6)
serverlike_thisplayers
0|TW-JP-SEA|Rustyafied 2X Vanilla|MAP WIPE 10/23EA · groups of 12+ · 2x · weekly · 2 on average0/200
1[KR/EN/JP/CN] 한국서버 | 2x Resources|WIPE 10.23EA · groups of 8+ · 2x · weekly · 4 on average1/100
2[SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10EA · groups of 8+ · 2x · biweekly · 82 on average61/115
3Japan Tokyo - Limited Raid Hours |3x|PvP|JPEA · groups of 8+ · 3x · weekly · 40 on average28/300
4QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造EA · groups of 20+ · weekly · 25 on average35/100
5[SEA] Rust Manila 2x | BiweeklyEA · groups of 8+ · 2x · biweekly · 24 on average65/150

Quick answers

From the figures on this page.

Player counts

How does [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip compare in the rankings?

Player hours over seven days put [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip at #5,810, in the top 26% of the ranked set.

What population does [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip carry?

[SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip reports 0 players at this refresh, with 40 slots configured. Over the last seven days it averaged 0 players and peaked at 2. The 48-hour sample puts the busiest hour at 18:00 UTC, averaging 1 players.

About the server

What does performance look like on [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip?

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

What is the Rust version on [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip?

Version Rust network protocol 2635 and build 168909 on Linux is reported by [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip. Joining needs the same protocol on your game; Steam handles the update.

How reliable is [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip, and is it up?

The current sample puts [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip online. A restart about 3 hours ago is what its reported uptime implies. Uptime of 86% across the last 7 full days: 144 hours of 168. The first row Rust Data holds for it is dated 13 October 2026.

Where does [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip sit?

No region tag is published by [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip, though its name points to Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 139.99.22.23:29588 is its address.

Map and rules

Which settings and rules does [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip run?

2x gather is what the name states, and the name is [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. The description says vanilla, which here means no changed rates, kits or rules: the game as Facepunch ships it. VAC is running: Valve's anti-cheat is on.

Which map has [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip loaded?

The game generates the map on [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip: procedural, size 3,500, seed 564262858. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipes and dates

When does [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip wipe, and how often?

The tag sets the prediction: [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip has too few wipes on record to confirm its schedule. The schedule puts the next wipe on Tuesday 3 November at 09:50 UTC. This world was created 2 days 2 hours ago. A weekly wipe schedule is published in its tags.

On [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip, what happens on wipe day?

Recent wipes averaged 2 players at their peak. The crowd on the latest wipe topped out 6 hours after it began. Half the peak or more was held to the next wipe in 100% of recent wipes.

Tags, lists

Which Rust Data filters and lists contain [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip?

The Rust Data lists that [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip fits are: Modded Rust servers and 2x Rust servers. These filters bring it up on the server list: Region: Asia; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 3 days; Gather rate: 2x.

How should you read the server tags on [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip?

These tags are published by [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): The server lists 40 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^w (Weekly): The interval is one week; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way into [SEA] Phoenix International | 2x | Solo/Dou/Trio | Weekly | Wip?

Enter client.connect 139.99.22.23:29588 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://discord.com/invite/wJrPSMJGP is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp40,ptrak,$r?,v2635,^w,^v,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp40
Max players The server lists 40 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build The server runs build 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly The interval is one week.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits 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.

Rust Data 65,323 players 11,766 servers online