BURN FSB | PVE | Events | x3
Online 77.134.106.92:28015 checked 7m ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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, measured since 19 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 26% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot 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 4, 44 hours in.
Wipes
every wipe as a delivery, newest first-
Mon 19 Oct, 22:11 UTC 23:11 UK · 9d agoWipe delivered
- Peak
- 4
- Crowd
- –
- Lasted
- running
- Players before
- 0
-
Sun 18 Oct, 16:02 UTC 17:02 UK · 10d agoWipe delivered
- Peak
- 3
- Crowd
- –
- Lasted
- 1.3 days
- Players before
- 2
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.
- Atlas - EU 3x | No BPs | Mondays 371 / 400
- Vital Rust - EU Mondays | 3x | No BPs 156 / 175
- HollowServers.co 3x Solo/Duo |LootX3|JUST FULLWIPED 124 / 120
- HollowServers.co 3x Solo/Duo/Trio |LootX3|JUST FULLWIPED 32 / 100
- FLAME RUST #1 [ NOLIMIT | x3 | MAGIC ] WIPE 27.10 99 / 350
- AceRust.com 3x Solo/Duo|LootX3|JUST FULLWIPED 17 / 100
Quick answers
From the figures on this page.
Player activity
What is the ranking of BURN FSB | PVE | Events | x3 against other Rust servers?
A seven-day player-hours count places BURN FSB | PVE | Events | x3 at #5,715: the top 26% of every ranked server.
How many players are on BURN FSB | PVE | Events | x3 right now?
At the moment 0 players are on BURN FSB | PVE | Events | x3, which has 10 slots. Averaged over the past week: 0 players, peaking at 4. The busiest hour over the last 48 hours was 11:00 UTC, averaging 2 players.
Rules and settings
On what map does BURN FSB | PVE | Events | x3 take place?
Size 3,000 and seed 123456 define the procedural map BURN FSB | PVE | Events | x3 runs, generated by the game. Identical size and seed give an identical map: view it on RustMaps from this page.
What are the rules on BURN FSB | PVE | Events | x3, and what settings does it run?
You get 3x gather on BURN FSB | PVE | Events | x3, going by its name. 8 players is the group limit, since the game's default applies. You get survival here, the usual game: build, gather, raid. Raiding and PvP are both on. Plugins or settings alter the game on this one, which sits under Modded in the server browser. Plugins come from Oxide. VAC, Valve's anti-cheat, is switched on.
Server details
In which region is BURN FSB | PVE | Events | x3 based?
You will find no region published by BURN FSB | PVE | Events | x3. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. 77.134.106.92:28015 is its address.
How smoothly does BURN FSB | PVE | Events | x3 run?
The 48-hour average for server fps stands at 59, never dipping below 55. The world held as many as 54,088 entities: buildings, deployables and the rest. 2,151 MB of memory was its top figure. What players call lag is the mix of low fps and an entity count that keeps climbing.
What is the uptime of BURN FSB | PVE | Events | x3, and is it online?
BURN FSB | PVE | Events | x3 is up and online at the moment. Its reported uptime suggests a restart roughly 43 hours ago. It was up 165 of 168 hours over the last 7 full days, 98% of the time. It was first seen by Rust Wipe Tracker on 17 October 2026.
What Rust version is BURN FSB | PVE | Events | x3 using?
The version on BURN FSB | PVE | Events | x3 is Rust network protocol 2635 and build 168909, running on Windows. The same protocol is required to join, and Steam takes care of updating it.
Wipe times
How does BURN FSB | PVE | Events | x3 handle its wipe days?
At their busiest, its recent wipes drew an average of 4 players. On the latest wipe, 44 hours passed before the crowd peaked.
On what schedule does BURN FSB | PVE | Events | x3 reset its map?
To tell its rhythm we would need more of BURN FSB | PVE | Events | x3's wipes on record; there are too few yet. The monthly force wipe takes every Rust server with it, and Thursday 5 November at 19:00 UTC is the next one. The world it is running was made 15 days 22 hours.
Server tags
Where does BURN FSB | PVE | Events | x3 appear across the Rust Wipe Tracker lists and filters?
You will find BURN FSB | PVE | Events | x3 on the following Rust Wipe Tracker lists: 3x Rust servers and Modded Rust servers. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.
How should you read the tags on BURN FSB | PVE | Events | x3?
Read off the game's server browser, the tags for BURN FSB | PVE | Events | x3 are: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): 8 per team, which is the default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.
Getting started
What is the process to join BURN FSB | PVE | Events | x3?
Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 77.134.106.92:28015.