PhoenixFireTigerLocalTest

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 16d ago · 80.208.56.246:28985

Abstract

We describe the public Rust server PhoenixFireTigerLocalTest, reached at 80.208.56.246:28985. It is offline at the last check, against a seven-day mean of 0¹. It ranks #15,479 of all servers, the top 71%. It last wiped 16d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/1	0% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#15,479	top 71%
Last wipe	16d ago	no schedule published
Next wipe³	–	too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

This server has not answered a direct query in the last 48 hours.

Figure 2: 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.

4Rank

The server stands in the top 71% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.

Measure	Value	Note
Wipe-day peak	0	players, last three wipes

No hourly players around its wipes yet.

Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Mon 12 Oct, 20:5016d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published

Figure 5: The map: Procedural Map.

Table 4: The server's published settings.

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
Map	Procedural Map
Size	–
Seed	–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust servers listed live [2] and next Rust wipe times [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 150 on average	105/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 28.10EU · groups of 8+ · weekly · 128 on average	122/100
RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average	149/225
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average	46/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 88 on average	4/200
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average	18/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1In which location is PhoenixFireTigerLocalTest based?

No region is published by PhoenixFireTigerLocalTest. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 80.208.56.246:28985 is its address.

A.2What is the online status and reliability of PhoenixFireTigerLocalTest?

At the present moment, PhoenixFireTigerLocalTest is offline; it was last seen 16 days 11 hours ago. The server was up 0% of the time over the last 7 full days, 0 of 168 hours. Its first appearance in Rust Statistics's records is 12 October 2026.

A.3What version of Rust is run on PhoenixFireTigerLocalTest?

The version of Rust on PhoenixFireTigerLocalTest is network protocol 2631 and build 156583, and the operating system is Windows. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.4What schedule does PhoenixFireTigerLocalTest follow for wipes?

Too few wipes by PhoenixFireTigerLocalTest have been recorded to determine the pattern. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. The current world has been running for 16 days 11 hours.

A.5How would you describe wipe day on PhoenixFireTigerLocalTest?

Recent wipes saw an average peak of 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Player count

A.6What is the rank of PhoenixFireTigerLocalTest among Rust servers?

The seven-day player-hours ranking puts PhoenixFireTigerLocalTest at #15,479, within the top 71% of ranked servers.

A.7What is the population level of PhoenixFireTigerLocalTest?

PhoenixFireTigerLocalTest is not online now; 16 days 11 hours have passed since it was last seen.

Tags and filters

A.8How should the tags on PhoenixFireTigerLocalTest be interpreted?

Tags from PhoenixFireTigerLocalTest, read by the game's server browser, are gmrust (Game mode): This is survival as standard Rust plays; mp1 (Max players): It offers 1 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2631 (Protocol): The game protocol is 2631; your client must match it to join; cs156583 (Build): Build 156583 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can PhoenixFireTigerLocalTest be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that PhoenixFireTigerLocalTest fits. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Settings and map

A.10Under what rules and settings does PhoenixFireTigerLocalTest operate?

The name of PhoenixFireTigerLocalTest states no gather rate. No cap is given beyond the game's default of 8 players per group. The mode is survival, which means gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. It appears under Modded in the browser: the game is changed by plugins or settings. Plugins number Oxide on this server. VAC is active: that is Valve's anti-cheat.

A.11On which map does PhoenixFireTigerLocalTest take place?

On PhoenixFireTigerLocalTest the terrain is procedural, built by the game itself.

How to join

A.12What is the process for joining PhoenixFireTigerLocalTest?

Enter client.connect 80.208.56.246:28985 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp1,ptrak,$r?,v2631,gmrust,cs156583,ts8,^o^z.

Table 6: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. This is survival as standard Rust plays.
`mp1`	Max players. It offers 1 slots.
`ts8`	Group limit. 8 per team, the value the game sets by default.
`v2631`	Protocol. The game protocol is 2631; your client must match it to join.
`cs156583`	Build. Build 156583 is the one running.
`ptrak`	Networking. Networking runs on RakNet, the game's standard layer.
`$r?`	Region code. The region code is unset.
Mods and access
`^o`	Oxide. The plugin framework in use is Oxide (uMod).
`^z`	Modded. The game is altered by plugins or settings, so it is listed as Modded.

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.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Modded Rust servers listed live. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.