Rust Server Analytics 34,317 players11,668 servers
All servers
Drill-through Server detail

BURN FSB | PVE | Events | x3

Online 77.134.106.92:28015 checked 7m ago

Drill-through
FilterServeris BURN FSB | PVE | Events | x3
Attributes
3x moddedoxide
Last refreshed
Players now 0/ 10
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
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
0123404:0013:0022:0007:0016:0002:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
02040608004:0013:0022:0007:0016:0002:00

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 best
RankRank in region
15k10k15k20k17 Oct19 Oct22 Oct24 Oct27 Oct29 Oct

Top 25% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

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.

usual gap1.3 daysbetween real wipes
wipe-day peak4players, last three wipes

The first 48 hours of its last wipes

Mon 19 OctSun 18 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 4, 44 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 19 Oct, 22:11 UTC9d ago 4 – running 0
Sun 18 Oct, 16:02 UTC10d ago 3 – 1.3 days 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
ServerProfilePlayers now
Atlas - EU 3x | No BPs | Mondays EU · groups of 16+ · 3x · weekly · 390 on average 170 / 200
Vital Rust - EU Mondays | 3x | No BPs EU · groups of 14+ · 3x · weekly · 177 on average 78 / 125
HollowServers.co 3x Solo/Duo |LootX3|JUST FULLWIPED NA · groups of 8+ · 3x · biweekly · 126 on average 305 / 370
HollowServers.co 3x Solo/Duo/Trio |LootX3|JUST FULLWIPED NA · groups of 8+ · 3x · biweekly · 122 on average 110 / 115
FLAME RUST #1 [ NOLIMIT | x3 | MAGIC ] WIPE 27.10 groups of 30+ · 3x · weekly · 113 on average 16 / 350
AceRust.com 3x Solo/Duo|LootX3|JUST FULLWIPED NA · groups of 8+ · 3x · biweekly · 105 on average 41 / 100

Quick answers

from the figures on this page

Wipe data

On what cycle does BURN FSB | PVE | Events | x3 wipe?

Too few wipes on record for BURN FSB | PVE | Events | x3 to show its rhythm. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. 15 days 17 hours ago the current world was made.

On BURN FSB | PVE | Events | x3, what happens on wipe day?

The average busiest count over recent wipes is 4 players. The highest player count on the latest wipe arrived 44 hours in.

Server details

In which region does BURN FSB | PVE | Events | x3 sit?

A region is not published by BURN FSB | PVE | Events | x3. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 77.134.106.92:28015.

Which Rust version is BURN FSB | PVE | Events | x3 on?

On Windows, BURN FSB | PVE | Events | x3 runs Rust network protocol 2635 and build 168909. The protocol has to match before you can join; Steam updates it automatically.

How reliable is BURN FSB | PVE | Events | x3, and is it online now?

BURN FSB | PVE | Events | x3 reports online at the current check. About 38 hours ago is when it last restarted, judged by its reported uptime. Of 168 hours in the last 7 full days, 165 were up: 98%. 17 October 2026 is when Rust Server Analytics first recorded it.

What performance does BURN FSB | PVE | Events | x3 show?

The 48-hour average was 59 server fps; the low was 55. At its highest the entity count was 54,088, including buildings, deployables and all else. Memory use reached 2,151 MB at peak. Players experience lag as low fps combined with a rising entity count.

Tags

Which meanings do the tags on BURN FSB | PVE | Events | x3 carry?

Tags from BURN FSB | PVE | Events | x3, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): A region code is not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section, because plugins or settings modify play. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does BURN FSB | PVE | Events | x3 appear across Rust Server Analytics's lists and filters?

These Rust Server Analytics lists include BURN FSB | PVE | Events | x3: 3x Rust servers: live list and Modded Rust servers: live data. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.

Population

What position does BURN FSB | PVE | Events | x3 hold in the server rankings?

The seven-day player-hours rank for BURN FSB | PVE | Events | x3 is #5,655, inside the top 25% of all ranked servers.

What is the population of BURN FSB | PVE | Events | x3?

Of 10 slots, 0 are filled on BURN FSB | PVE | Events | x3 at this refresh. Seven-day figures: an average of 0 players and a peak of 4. The 48-hour peak window is 11:00 UTC, at an average of 2 players.

Settings

How is BURN FSB | PVE | Events | x3 configured, and what rules apply?

BURN FSB | PVE | Events | x3 names a 3x gather rate. The game's default 8-player group limit is in force. survival is the game mode, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. The Modded category lists it; plugins or settings change the game. Oxide plugins are run. VAC, Valve's anti-cheat, is enabled.

What is the map for BURN FSB | PVE | Events | x3?

BURN FSB | PVE | Events | x3 uses a procedural map of size 3,000 with seed 123456, generated by the game. The map is reproducible from its size and seed and can be seen on RustMaps from here.

How to join

How do you connect to BURN FSB | PVE | Events | x3?

In the Rust console (F1), enter client.connect 77.134.106.92:28015. Launch Rust on this page also works, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust format.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, the stock game setting.
v2635
Protocol To join, your game version must match protocol 2635.
cs168909
Build Build number 168909.
ptrak
Networking RakNet is the network layer, the game's standard one.
$r?
Region code A region code is not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section, because plugins or settings modify play.

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.