Offline 109.171.98.79:28015 checked 2d ago
Fire Test
Connect
srv = rust.server("109.171.98.79:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 54% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()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 1, 29 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 11:30 UTC25d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- 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
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 144/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 185/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 75/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 8/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 16/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Fire Test rank?
Rank #11,956 on seven-day player hours for Fire Test, within the top 54% of all ranked servers.
What population does Fire Test carry?
Fire Test returns no live count at this refresh, having last been seen 2 days 17 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server facts
Which Rust version is Fire Test on?
Version Rust network protocol 2635 and build 167398 on Windows is reported by Fire Test. The protocol has to match before you can join, and Steam does the updating.
How reliable is Fire Test, and is it online now?
Offline now for Fire Test, last seen 2 days 17 hours ago. 2 of 168 hours up over the last 7 full days, or 1%. The first row Rust Data holds for it is dated 21 September 2026.
Which location does Fire Test run from?
For Fire Test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 109.171.98.79:28015.
Settings and map
Which settings and rules does Fire Test run?
You will not find a gather rate in the string Fire Test. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Fire Test selected?
Fire Test runs a procedural map, which the game generates.
Wipe data
When does Fire Test wipe, and on what schedule?
Too few wipes are on record for Fire Test to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 25 days 22 hours ago, and that is the one in play.
What is wipe day on Fire Test like?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 29 hours in.
Tags, lists
Which lists on Rust Data hold Fire Test, and which filters?
These Rust Data lists include Fire Test: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Fire Test?
The game's server browser reads these tags from Fire Test: gmrust (Game mode): Survival play, standard Rust; mp3 (Max players): The server lists 3 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs167398 (Build): The server runs build 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way to join Fire Test?
In Rust, F1 opens the console: type client.connect 109.171.98.79:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.