Fire Test
ruststatistics.org · independent, not affiliated with Facepunch Studios
Offline · checked 2d ago · 109.171.98.79:28015
Abstract
We describe the public Rust server Fire Test, reached at 109.171.98.79:28015. It is offline at the last check, against a seven-day mean of 1 and a peak of 11. It ranks #11,937 of all servers, the top 54%. It last wiped 25d ago.
Keywordsmodded oxide
1Summary statistics
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.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 54% 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.
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.
| Measure | Value | Note |
|---|---|---|
| Wipe-day peak | 1 | players, last three wipes |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Sat 3 Oct, 11:3025d ago | 1 | – | 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
| Address | 109.171.98.79:28015 |
|---|---|
| Region | – |
| Max players | 3 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 3 Oct 2026, 11:39 UTC |
| Hostname | – |
| First seen | 21 Sep 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 population table [2] and upcoming Rust wipes [3].
| Server | Players |
|---|---|
| ShockRust | Blue | NoLimitno group limit · 149 on average | 154/500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average | 120/100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average | 186/225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average | 78/700 |
| RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average | 8/200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average | 22/1000 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1What location does Fire Test have?
There is no region published for Fire Test. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 109.171.98.79:28015 is its address.
A.2What is the online status and reliability of Fire Test?
At the present moment, Fire Test is offline; it was last seen 2 days 17 hours ago. The server was up 1% of the time over the last 7 full days, 2 of 168 hours. Its first appearance in Rust Statistics's records is 21 September 2026.
A.3What version of Rust is run on Fire Test?
Rust network protocol 2635 and build 167398 is the version that Fire Test runs, on Windows. To join, your game must use the same protocol; Steam handles the update for you.
Wipe timing
A.4What schedule does Fire Test follow for wipes?
Too few wipes by Fire Test 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. 25 days 23 hours have passed since the current world was generated.
A.5What happens on Fire Test when wipe day arrives?
The average busiest point of recent wipes was 1 players. The crowd reached its maximum 29 hours after the latest wipe.
Population
A.6How does Fire Test compare with other Rust servers in the rankings?
Ranked by player hours across seven days, Fire Test holds #11,937, in the top 54% of all ranked servers.
A.7How would you characterise the player activity on Fire Test?
The last recorded sighting of Fire Test was 2 days 17 hours ago; it is offline now. The peak over seven days is 1, against an average of 1.
Tags and filters
A.8How should the tags on Fire Test be interpreted?
gmrust (Game mode): Survival on standard Rust rules; mp3 (Max players): It offers 3 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs167398 (Build): Build 167398 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): A region code has not been set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags Fire Test publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.
A.9Where can Fire Test be found among the Rust Statistics lists and filters?
These Rust Statistics lists include Fire Test: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules, settings, map
A.10Which settings and rules are in force on Fire Test?
No gather rate appears in the name of Fire Test. At 8 players, the group limit equals the game's default. survival is the game mode here; gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. The server browser lists it as Modded, where plugins or settings alter the game. The plugin count is Oxide. VAC is active: that is Valve's anti-cheat.
A.11What is the map for Fire Test?
On Fire Test the terrain is procedural, built by the game itself.
How to join
A.12What steps are required to join Fire Test?
Enter client.connect 109.171.98.79:28015 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 mp3,ptrak,$r?,v2635,gmrust,cs167398,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Survival on standard Rust rules. |
mp3 | Max players. It offers 3 slots. |
ts8 | Group limit. 8 per team, the value the game sets by default. |
v2635 | Protocol. Joining requires the same game version: protocol 2635. |
cs167398 | Build. Build 167398 is the one running. |
ptrak | Networking. Networking runs on RakNet, the game's standard layer. |
$r? | Region code. A region code has not been set. |
| Mods and access | |
^o | Oxide. Plugins are handled by Oxide (uMod). |
^z | Modded. Modded listing: plugins or settings modify the game. |
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 population table. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.