Offline 80.208.56.246:28985 checked 16d ago
PhoenixFireTigerLocalTest
Connect
srv = rust.server("80.208.56.246:28986")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 71% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 12 Oct, 20:50 UTC16d ago | 0 | NaN | running | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 80.208.56.246:28985
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 20:50 UTC
- hostname
- –
- first seen
- 12 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 166/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 180/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 68/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 13/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 19/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does PhoenixFireTigerLocalTest rank?
Player hours over seven days put PhoenixFireTigerLocalTest at #15,479, in the top 71% of the ranked set.
How full does PhoenixFireTigerLocalTest run?
The current row shows PhoenixFireTigerLocalTest offline; the last response was 16 days 15 hours ago.
Server facts
What is the Rust version on PhoenixFireTigerLocalTest?
Version Rust network protocol 2631 and build 156583 on Windows is reported by PhoenixFireTigerLocalTest. Steam updates your game for you, but the protocol must match to join.
Is PhoenixFireTigerLocalTest up, and what does its uptime show?
Offline now for PhoenixFireTigerLocalTest, last seen 16 days 15 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 12 October 2026.
Which location does PhoenixFireTigerLocalTest run from?
No region is published by PhoenixFireTigerLocalTest. Rust Data does not look up where the machine stands; it shows where a server says it is. 80.208.56.246:28985 is its address.
Rules, settings, map
Which settings and rules does PhoenixFireTigerLocalTest run?
No gather rate appears in the name: PhoenixFireTigerLocalTest. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has PhoenixFireTigerLocalTest selected?
The game generates its map: procedural, on PhoenixFireTigerLocalTest.
Wipe data
When does PhoenixFireTigerLocalTest wipe, and on what schedule?
Too few wipes are on record for PhoenixFireTigerLocalTest to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 16 days 15 hours ago, and that is the one in play.
On PhoenixFireTigerLocalTest, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Where does PhoenixFireTigerLocalTest appear among Rust Data lists and filters?
The Rust Data lists that PhoenixFireTigerLocalTest fits are: Modded Rust servers. It appears under these filters 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 PhoenixFireTigerLocalTest?
Read by the game's server browser, the tags PhoenixFireTigerLocalTest publishes are: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2631 (Protocol): The server speaks protocol 2631, so match your game version; cs156583 (Build): The server runs build 156583; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join PhoenixFireTigerLocalTest?
Enter client.connect 80.208.56.246:28985 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.