PhoenixFireTigerLocalTest
Offline 80.208.56.246:28985 checked 16d ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot 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
every wipe as a delivery, newest first-
Mon 12 Oct, 20:50 UTC 21:50 UK · 16d agoWipe delivered
- Peak
- 0
- Crowd
- –
- Lasted
- running
- Players before
- 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
- ShockRust | Blue | NoLimit 41 / 500
- МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 124 / 100
- RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 0 / 225
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 16 / 700
- RustSpain.com | EU Main 2 / 200
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 3 / 1000
Quick answers
From the figures on this page.
Player activity
How does PhoenixFireTigerLocalTest compare with other Rust servers in the rankings?
In the top 71% of all ranked servers sits PhoenixFireTigerLocalTest, at #15,479 on hours played over seven days.
What is the current population on PhoenixFireTigerLocalTest?
The last sighting of PhoenixFireTigerLocalTest was 16 days 8 hours ago; it is offline right now.
Rules and settings
On what map does PhoenixFireTigerLocalTest take place?
A procedural map, generated by the game, is what PhoenixFireTigerLocalTest runs.
What are the rules on PhoenixFireTigerLocalTest, and what settings does it run?
No gather rate appears in the name of PhoenixFireTigerLocalTest. Up to 8 players can join a group, the default for the game. It runs survival, the usual game: build, gather, raid. You can raid and fight other players. The server browser lists it as Modded, because plugins or settings alter the game. Oxide supplies the plugins. VAC, Valve's anti-cheat, is switched on.
About the server
What location does PhoenixFireTigerLocalTest run from?
There is no region published for PhoenixFireTigerLocalTest. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. 80.208.56.246:28985 is its address.
Is PhoenixFireTigerLocalTest up, and how good is its uptime?
PhoenixFireTigerLocalTest is offline at the moment, with the last sighting 16 days 8 hours ago. It was up 0 of 168 hours over the last 7 full days, 0% of the time. It was first seen by Rust Wipe Tracker on 12 October 2026.
On what Rust version does PhoenixFireTigerLocalTest operate?
On Windows, PhoenixFireTigerLocalTest runs Rust network protocol 2631 and build 156583. To join, your game must be on the same protocol; Steam handles that update for you.
Map resets
How does PhoenixFireTigerLocalTest handle its wipe days?
The average busiest point of its recent wipes was 0 players. 0 hours after the latest wipe, the crowd reached its peak.
On what schedule does PhoenixFireTigerLocalTest reset its map?
Its rhythm cannot yet be told: too few of PhoenixFireTigerLocalTest's wipes are on record. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. You are playing a world created 16 days 8 hours.
Tags and filters
Where does PhoenixFireTigerLocalTest appear in Rust Wipe Tracker lists and filters?
The Rust Wipe Tracker lists that include PhoenixFireTigerLocalTest are: Modded Rust servers. These are the filters that 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 tags on PhoenixFireTigerLocalTest?
gmrust (Game mode): Survival in standard Rust; mp1 (Max players): The server has 1 slots; ts8 (Group limit): The game default caps teams at 8; v2631 (Protocol): To join, your game must match protocol 2631; cs156583 (Build): Build number: 156583; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): A region code isn't set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings, hence the Modded listing are the tags PhoenixFireTigerLocalTest publishes, and the server browser takes them as read. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.
Getting started
What steps do you take to join PhoenixFireTigerLocalTest?
Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 80.208.56.246:28985.