Station XX-15479 · no signal
PhoenixFireTigerLocalTest
Offline 80.208.56.246:28985 checked 16d ago
- Players now
- 0/ 1
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,479
- top 71%
- Last wipe
- 16d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 1 slots
- Motion · 24 h
- M –not enough readings
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.
- wipe-day peak
- 0players, last three wipes
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 12 Oct, 20:50 UTC16d ago | M0.0■steady | 0 | – | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on PhoenixFireTigerLocalTest?
The map on PhoenixFireTigerLocalTest is procedural, produced by the game.
Which settings and rules apply on PhoenixFireTigerLocalTest?
You will find no gather rate in the name of PhoenixFireTigerLocalTest. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.
Player counts
How many players are recorded on PhoenixFireTigerLocalTest right now?
PhoenixFireTigerLocalTest is not responding at this moment and is offline, last seen 16 days 11 hours ago.
How does PhoenixFireTigerLocalTest rank against other Rust servers?
On player hours for the past week, PhoenixFireTigerLocalTest sits at #15,479, which puts it inside the top 71% of every ranked server.
Server facts
How reliably does PhoenixFireTigerLocalTest stay online?
PhoenixFireTigerLocalTest is down at the moment; the last recorded contact was 16 days 11 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 12 October 2026.
Where in the world is PhoenixFireTigerLocalTest hosted?
No region is published by PhoenixFireTigerLocalTest. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 80.208.56.246:28985 is the address it uses.
Which Rust version is PhoenixFireTigerLocalTest running?
Rust network protocol 2631 and build 156583 on Windows is what PhoenixFireTigerLocalTest runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on PhoenixFireTigerLocalTest?
On average, the busiest point of its recent wipes drew 0 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does PhoenixFireTigerLocalTest run its wipes?
The rhythm of PhoenixFireTigerLocalTest cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 16 days 11 hours.
Server tags
What do the server tags on PhoenixFireTigerLocalTest mean?
These are the tags PhoenixFireTigerLocalTest publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): The server has 1 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2631 (Protocol): To connect, your game must be on the same protocol, 2631; cs156583 (Build): Game build: 156583; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does PhoenixFireTigerLocalTest appear?
These Rust Server Trends lists include PhoenixFireTigerLocalTest: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
How do you connect to PhoenixFireTigerLocalTest?
Enter client.connect 80.208.56.246:28985 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.