Fire Test
Key statistics
the figures behind the quote- Players now
- 0/ 3 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak 1
- Rank
- #9,843 top 44%
- Rank · 7d ago
- #12,083 ▲2240 places up
- Last wipe
- 11d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 5 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 21 Sep 2026 no hostname published
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 44% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yet- wipe-day peak
- 1 players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 29 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 11:30 UTC11d 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. 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 wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 127 on average | 164/300 | ▲+8+5.5% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 107 on average | 185/225 | ▼−17−8.5% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 92/100 | ▲+1+1.3% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 87 on average | 39/1000 | ▼−67−63.3% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 12/1000 | ▼−28−69.8% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 67/700 | ▼−29−30.2% |
Quick answers
from the figures on this pageRules & Settings
How is Fire Test configured in terms of rules and settings?
The name of Fire Test carries no gather rate. Groups can contain a maximum of 8 players, the default for the game. It runs survival, gather, build and raid in the standard game. Combat and raiding between players are allowed. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins are in use. VAC is active.
What is the current map on Fire Test?
The game generates the procedural map on Fire Test.
Population
What is the rank of Fire Test?
In the top 44% of all ranked servers, Fire Test is #9,843 on player hours over the last seven days.
What is the population on Fire Test?
Right now, Fire Test is offline; the last sighting was 36 hours ago. The seven-day average is 0 players, with a peak of 1.
Wipe Cycle
What happens on wipe day at Fire Test?
The average peak across its recent wipes is 1 players. 29 hours after the latest wipe, the crowd reached its peak.
When does Fire Test schedule its wipes?
The record holds too few of Fire Test's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. This world has been running for 11 days 6 hours.
Server Info
What is the server location for Fire Test?
For Fire Test, no region is published. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 109.171.98.79:28015 is its address.
What Rust version is Fire Test running?
The version in use at Fire Test: Rust network protocol 2634 and build 167398, on Windows. The protocol has to match for you to join, and Steam applies that update.
What is the uptime and reliability of Fire Test?
Offline at this moment: Fire Test. Last seen 36 hours ago. 7% is its uptime for the last 7 full days, 11 of 168 hours. First sighting by Rust Analytics: 21 September 2026.
Server Tags
How should you interpret the tags on Fire Test?
Published by Fire Test for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust format; mp3 (Max players): It holds 3 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167398 (Build): Build 167398; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): Region code: none set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also carry its current players, queue and world creation time; this page shows them at the top.
On Rust Analytics, which lists and filters feature Fire Test?
The following Rust Analytics lists feature Fire Test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How to Join
What is the process to join Fire Test?
The console route: start Rust, press F1, enter client.connect 109.171.98.79:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp3,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z
Game
gmrust
mp3
ts8
v2634
cs167398
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.