PhoenixFireTigerLocalTest
Offline 80.208.56.246:28985 checked 17d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 20:50 UTC17d ago | 0 | – | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 29/500
- 123/100
- 55/225
- 10/700
- 29/700
- 53/200
Quick answers
from the figures on this pageWipe timing
What happens on PhoenixFireTigerLocalTest when wipe day comes?
The busiest point of its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.
How often does PhoenixFireTigerLocalTest wipe, and when?
To tell the rhythm of PhoenixFireTigerLocalTest, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 17 days 8 hours ago.
Tags
How should you read the tags on PhoenixFireTigerLocalTest?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2631 (Protocol): Match the game version: protocol 2631 is required; cs156583 (Build): Build 156583; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game from PhoenixFireTigerLocalTest. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does PhoenixFireTigerLocalTest appear in Rust Metrics lists and filters?
These Rust Metrics lists carry PhoenixFireTigerLocalTest: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
What position does PhoenixFireTigerLocalTest hold among Rust servers?
Player hours over seven days put PhoenixFireTigerLocalTest at #15,479, in the top 71% of all ranked servers.
What is the population on PhoenixFireTigerLocalTest?
Status for PhoenixFireTigerLocalTest: offline. Last seen 17 days 8 hours ago.
Operator and location
What location is PhoenixFireTigerLocalTest hosted in?
No region tag on PhoenixFireTigerLocalTest. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 80.208.56.246:28985.
What Rust version is PhoenixFireTigerLocalTest on?
Version check: Rust network protocol 2631 and build 156583 on Windows, run by PhoenixFireTigerLocalTest. To get in, your game needs the same protocol; Steam applies the update.
Is PhoenixFireTigerLocalTest up, and how often does it stay up?
PhoenixFireTigerLocalTest reports offline. The last reading came 17 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 12 October 2026.
Settings and map
What settings and rules apply on PhoenixFireTigerLocalTest?
Reading the name gives no gather rate for PhoenixFireTigerLocalTest. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on PhoenixFireTigerLocalTest?
The game generates a procedural map for PhoenixFireTigerLocalTest.
Connection
How can you get onto PhoenixFireTigerLocalTest?
Press F1 in Rust and enter client.connect 80.208.56.246:28985. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.