This server publishes no banner
Exhibit no. 15,479Acc. 2026.15479
PhoenixFireTigerLocalTest
Rust server · in the archive since 12 October 2026
Offline 80.208.56.246:28985 checked 16d ago
The timeline
Wipes
Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.
12 Oct Last seen 12 Oct20:50
a wipe on recordthe monthly force wipeexpectedlast seen, 12 Oct 2026, 20:55 UTCAll times UTC.
The record of each wipe
-
Mon 12 Oct 202620:50 UTC16d ago
- 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.
The rhythm
Wipe schedule
too few wipes seen yet
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.
The record
Population, performance and rank
Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.
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
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Related exhibits
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Visitors' questions about this exhibit
Quick answers
Answered from the figures on this page.
Lists and tags
What do the server tags on PhoenixFireTigerLocalTest mean?
You can see the tags PhoenixFireTigerLocalTest publishes, read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): 1 slots are set on this server; ts8 (Group limit): The default cap of 8 per team applies here; v2631 (Protocol): The server runs game protocol 2631; matching it is required to join; cs156583 (Build): The game build is 156583; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code field is empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings. Shown at the top of this page are the current players, the queue and the world's age, also taken from the tags.
Which Rust Server History lists and filters include PhoenixFireTigerLocalTest?
The Rust Server History lists that feature PhoenixFireTigerLocalTest are: Modded Rust servers: the record. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server entry
Which version of Rust does PhoenixFireTigerLocalTest run?
On Windows, PhoenixFireTigerLocalTest runs Rust network protocol 2631 and build 156583. Steam updates your game for you; joining needs the same protocol.
Is PhoenixFireTigerLocalTest online, and how reliable is it?
The record shows PhoenixFireTigerLocalTest offline at this moment, last seen 16 days 16 hours ago. It was up for 0 of 168 hours in the last 7 full days, 0% of the time. The first sighting by Rust Server History was on 12 October 2026.
Where is PhoenixFireTigerLocalTest located?
You will find no region published by PhoenixFireTigerLocalTest. The location on Rust Server History is what a server says, not a lookup of where the machine stands. Its entry gives 80.208.56.246:28985 as the address.
Wipe log
What does wipe day look like on PhoenixFireTigerLocalTest?
0 players on average was the busiest its recent wipes drew. At 0 hours after the latest wipe, the crowd reached its peak.
What is the wipe schedule on PhoenixFireTigerLocalTest?
The rhythm of PhoenixFireTigerLocalTest cannot be told yet, as too few of its wipes are on record. Next on Thursday 5 November at 19:00 UTC is the monthly force wipe, when every Rust server wipes. The world it runs now dates from 16 days 17 hours ago.
Player counts
How does PhoenixFireTigerLocalTest rank against other Rust servers?
Player hours over the last seven days put PhoenixFireTigerLocalTest at #15,479: a place in the top 71% of all ranked servers.
How busy is PhoenixFireTigerLocalTest?
PhoenixFireTigerLocalTest is offline at present, having last been seen 16 days 16 hours ago.
Rules and settings
What are the rules and settings on PhoenixFireTigerLocalTest?
No gather rate is stated in the name of PhoenixFireTigerLocalTest. The limit of 8 players per group is the game's default. Under game mode, the entry reads survival, gathering, building and raiding: the standard game. You may fight and raid other players. Plugins or settings alter the game here, and the browser lists the server under Modded. The plugin count is Oxide. VAC from Valve is switched on.
Which map does PhoenixFireTigerLocalTest run?
A procedural map is what PhoenixFireTigerLocalTest runs; the game generates it.
Join record
How do I join PhoenixFireTigerLocalTest?
Entering client.connect 80.208.56.246:28985 in the console (F1) connects you to this server. The Launch Rust button on this page does the same: it opens the game via Steam and connects on your behalf.
The label explained
Server tags
What each tag this server publishes means.
Published as mp1,ptrak,$r?,v2631,gmrust,cs156583,ts8,^o^z
Game
gmrust
mp1
ts8
v2631
cs156583
ptrak
$r?
Mods and access
^o
^z
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.