Statistical profileOffline
PhoenixFireTigerLocalTest
80.208.56.246:28985 checked 16d ago
Connect to this server
1. Main points
Players now
0/ 1
0% full
7-day average
0
peak –
Rank
#15,479
top 71%
Last wipe
16d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 1 slots.
- It ranks #15,479 of all ranked servers, the top 71%, on player hours over the last seven days.
- Its current map went up 16d ago.
2. Players
Figure 1: Players on PhoenixFireTigerLocalTest
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipe-day peak
0
players, last three wipes
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 20:50 UTC16d ago | 0 | – | running | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of PhoenixFireTigerLocalTest
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of PhoenixFireTigerLocalTest
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 149 on average | 164 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 187 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 69 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 13 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 19 / 1000 |
10. Quick answers
From the figures on this page.
Wipe records
When does PhoenixFireTigerLocalTest wipe, and how often?
Too few wipes of PhoenixFireTigerLocalTest are on record to establish its rhythm. The monthly force wipe on Thursday 5 November at 19:00 UTC is the next point at which every Rust server wipes. 16 days 15 hours have passed since this world was made.
What should you expect on wipe day at PhoenixFireTigerLocalTest?
The average busiest point of its recent wipes drew 0 players. The peak of the latest wipe's crowd came 0 hours after it began.
Server record
Is PhoenixFireTigerLocalTest up, and how well has it held up?
PhoenixFireTigerLocalTest is offline at the time of this release; it was last seen 16 days 15 hours ago. Of the 168 hours in the last 7 full days, it was up 0 of them, or 0%. First recorded by Rust Census on 12 October 2026.
In which location is PhoenixFireTigerLocalTest based?
No region is given by PhoenixFireTigerLocalTest. Rust Census does not look up where the machine stands; it shows where a server says it is. At 80.208.56.246:28985 it is addressed.
What version of Rust has been recorded on PhoenixFireTigerLocalTest?
Rust network protocol 2631 and build 156583 on Windows is the version PhoenixFireTigerLocalTest runs. The same protocol is required for your game to join, and Steam updates it for you.
Player figures
What are the current player figures for PhoenixFireTigerLocalTest?
PhoenixFireTigerLocalTest is offline at present; its last recording was 16 days 15 hours ago.
How does PhoenixFireTigerLocalTest compare with other servers in the rankings?
The rank for PhoenixFireTigerLocalTest is #15,479 on seven-day player hours, in the top 71% of ranked servers.
Tag details
On Rust Census, which lists and filters carry PhoenixFireTigerLocalTest?
These Rust Census lists include PhoenixFireTigerLocalTest: Modded Rust servers, counted. Under these filters it comes up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
The tags on PhoenixFireTigerLocalTest: what do they indicate?
gmrust (Game mode): Survival play, in the standard Rust format; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2631 (Protocol): Your game must run protocol 2631 to join; cs156583 (Build): The server runs game build 156583; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): A region code has not been set; ^o (Oxide): Plugins are handled by Oxide (uMod) on this server; ^z (Modded): Plugins or settings alter the game on this modded server are the tags PhoenixFireTigerLocalTest publishes, and the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Settings and map
What map is listed for PhoenixFireTigerLocalTest?
The game generates the procedural map on PhoenixFireTigerLocalTest.
On PhoenixFireTigerLocalTest, what rules and settings are in force?
No gather rate is given in the name of PhoenixFireTigerLocalTest. The group cap stands at 8 players, the default for the game. survival is the game mode recorded, the standard game: gather, build, raid. Combat between players and raiding are both permitted. Plugins or settings change the game, and the browser lists it under Modded. Oxide plugins are recorded on it. Anti-cheat is active: VAC, Valve's system, is on.
Join details
What steps are needed to join PhoenixFireTigerLocalTest?
Enter client.connect 80.208.56.246:28985 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp1,ptrak,$r?,v2631,gmrust,cs156583,ts8,^o^z
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp1 | Max players 1 slots are available. |
ts8 | Group limit Teams are capped at 8, the default the game ships with. |
v2631 | Protocol Your game must run protocol 2631 to join. |
cs156583 | Build The server runs game build 156583. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code A region code has not been set. |
Mods and access
^o | Oxide Plugins are handled by Oxide (uMod) on this server. |
|---|---|
^z | Modded Plugins or settings alter the game on this modded server. |
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.