Station XX-5655 · recording
BURN FSB | PVE | Events | x3
Online 77.134.106.92:28015 checked 8m ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 4
- Rank
- #5,655
- top 25%
- Last wipe
- 15d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +2into Tue 11:00 UTC
- Peak · 48 h
- 4most players in any hour
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 25% 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.
- usual gap
- 1.3 daysbetween real wipes
- wipe-day peak
- 4players, last three wipes
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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 19 Oct, 22:11 UTC9d ago | M0.6▲rising | 4 | – | running | 0 | |
| Sun 18 Oct, 16:02 UTC10d ago | M0.0▲rising | 3 | – | 1.3 days | 2 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on BURN FSB | PVE | Events | x3?
The procedural map on BURN FSB | PVE | Events | x3 is size 3,000 with seed 123456, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on BURN FSB | PVE | Events | x3?
Its name points to a gather rate of 3x on BURN FSB | PVE | Events | x3. The group limit is 8 players, the game's default. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on BURN FSB | PVE | Events | x3?
A reading taken now shows 0 players on BURN FSB | PVE | Events | x3, which has 10 slots. Across seven days this server recorded an average of 0 players and a peak of 4. Averaged over the last 48 hours, the busiest hour was 11:00 UTC at 2 players.
How does BURN FSB | PVE | Events | x3 rank against other Rust servers?
Over the last seven days, BURN FSB | PVE | Events | x3 recorded enough player hours to reach #5,655 worldwide, placing it in the top 25% of all ranked servers.
Server details
How reliably does BURN FSB | PVE | Events | x3 stay online?
Right now, you can reach BURN FSB | PVE | Events | x3. Its reported uptime points to a restart about 38 hours ago. It was up 98% of the time across the last 7 full days: 165 of 168 hours. 17 October 2026 is when Rust Server Trends first recorded it.
Does BURN FSB | PVE | Events | x3 hold a steady tick rate?
The 48-hour average is 59 server fps; 55 is the lowest observed. At its highest, it carried 54,088 entities: buildings, deployables and the world's other contents. Its highest memory use was 2,151 MB. What you feel as lag is the combination of low fps and a rising entity count.
Which region does BURN FSB | PVE | Events | x3 run from?
Nothing about a region comes from BURN FSB | PVE | Events | x3. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 77.134.106.92:28015.
Which Rust version is BURN FSB | PVE | Events | x3 running?
Rust network protocol 2635 and build 168909 on Windows is what BURN FSB | PVE | Events | x3 runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on BURN FSB | PVE | Events | x3?
4 players, on average, was the busiest crowd at its recent wipes. 44 hours into the latest wipe, the crowd reached its peak.
How often does BURN FSB | PVE | Events | x3 wipe, and on which days?
On record so far are too few of BURN FSB | PVE | Events | x3's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 15 days 16 hours.
Tags
What do the server tags on BURN FSB | PVE | Events | x3 mean?
The game's server browser reads the tags BURN FSB | PVE | Events | x3 publishes: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): The server has 10 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does BURN FSB | PVE | Events | x3 appear?
These Rust Server Trends lists include BURN FSB | PVE | Events | x3: 3x Rust servers, by live population and Modded Rust servers, tracked live. 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.
Join the server
What steps get you onto BURN FSB | PVE | Events | x3?
You can connect by pressing F1 in Rust and typing client.connect 77.134.106.92:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.