Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO O SRV11,624online PAX41,406playing OCC3,010with players WIPED 3H84
MODModded traffic
Callsign

BRN5655=

BURN FSB | PVE | Events | x3

Online 77.134.106.92:28015 checked 10m ago

3x moddedoxide
Clearance · join
Players now 0/ 10 0% full
7-day average0peak 4
Rank#5,655top 25%
Last wipe15d agono schedule published
Next wipe–too few wipes seen yet
Track history

Players

AveragePeak
0123408:0017:0002:0011:0021:0006:00

Hourly average and peak, UTC.

Server performance

02040608008:0017:0002:0011:0021:0006: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.

Flight plan

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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign ATL015EU · groups of 16+ · 3x · weekly · 390 on average Atlas - EU 3x | No BPs | Mondays
    Players 312/250
  2. 02MOD
    Callsign VTL015EU · groups of 14+ · 3x · weekly · 178 on average Vital Rust - EU Mondays | 3x | No BPs
    Players 115/125
  3. 03MOD
    Callsign HLL010NA · groups of 8+ · 3x · biweekly · 128 on average HollowServers.co 3x Solo/Duo |LootX3|JUST FULLWIPED
    Players 137/190
  4. 04MOD
    Callsign HLL010NA · groups of 8+ · 3x · biweekly · 122 on average HollowServers.co 3x Solo/Duo/Trio |LootX3|JUST FULLWIPED
    Players 46/100
  5. 05MOD
    Callsign FLM521groups of 30+ · 3x · weekly · 113 on average FLAME RUST #1 [ NOLIMIT | x3 | MAGIC ] WIPE 27.10
    Players 74/350
  6. 06MOD
    Callsign ACR010NA · groups of 8+ · 3x · biweekly · 105 on average AceRust.com 3x Solo/Duo|LootX3|JUST FULLWIPED
    Players 21/100
ATIS · this server

Quick answers

From the figures on this page.

Filters

Which lists and filters on Rust Tracker show BURN FSB | PVE | Events | x3?

On Rust Tracker, BURN FSB | PVE | Events | x3 sits in these lists: 3x Rust servers: live tracking and Modded servers, tracked live. It comes up under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.

Which tags does BURN FSB | PVE | Events | x3 carry, and what do they mean?

Listed for the server browser to read, BURN FSB | PVE | Events | x3 publishes these tags: gmrust (Game mode): Survival as standard Rust plays; mp10 (Max players): Capacity: 10 slots; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework confirmed: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Schedule

What should you expect on BURN FSB | PVE | Events | x3 when wipe day lands?

The average peak across recent wipes: 4 players. The peak on the latest wipe came 44 hours after it.

Which wipe times are confirmed for BURN FSB | PVE | Events | x3?

The record holds too few of BURN FSB | PVE | Events | x3's wipes to show its rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. This world has been running 15 days 21 hours.

Server Details

What is the uptime on BURN FSB | PVE | Events | x3, and is it online?

Right now BURN FSB | PVE | Events | x3 is online. About 42 hours ago it restarted last, based on reported uptime. 165 of 168 hours up over the last 7 full days: 98% uptime. Rust Tracker logged it first on 17 October 2026.

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

Rust network protocol 2635 and build 168909 is the build on BURN FSB | PVE | Events | x3; the platform is Windows. To join, your game must be on the same protocol; Steam handles the update.

What is performance like on BURN FSB | PVE | Events | x3?

For the last 48 hours it averaged 59 server fps; the floor was 55. Buildings, deployables and the rest of the world took it to a maximum of 54,088 entities. Memory peaked at 2,151 MB. Players feel lag when fps drops and the entity count climbs.

Where does BURN FSB | PVE | Events | x3 sit?

Region: none published by BURN FSB | PVE | Events | x3. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 77.134.106.92:28015.

Player Count

Is BURN FSB | PVE | Events | x3 busy?

Slots 10; players on board 0: that is BURN FSB | PVE | Events | x3 now. Peak of 4 in the last seven days, average 0 players. At 11:00 UTC it drew its highest average of the last 48 hours: 2 players.

What rank does BURN FSB | PVE | Events | x3 carry among Rust servers?

On player hours over seven days, BURN FSB | PVE | Events | x3 ranks #5,655, inside the top 25% of all ranked servers.

Settings

Which settings and rules are confirmed on BURN FSB | PVE | Events | x3?

The name says it: BURN FSB | PVE | Events | x3 runs 3x gather. Up to 8 players per group, the game's default. survival is the game mode, gather, build and raid: the standard game. Fighting and raiding between players are on. Plugins or settings change the game, and the server browser lists it under Modded. Oxide plugins run on it. VAC is on, Valve's anti-cheat.

Which map is confirmed for BURN FSB | PVE | Events | x3?

The map on BURN FSB | PVE | Events | x3 is procedural, size 3,000, seed 123456, generated by the game. Look at it on RustMaps from this page: equal size and seed return the same map.

How to Join

Which steps join BURN FSB | PVE | Events | x3?

Open the console in Rust with F1 after starting the game, then type client.connect 77.134.106.92:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Survival as standard Rust plays.
mp10
Max players Capacity: 10 slots.
ts8
Group limit Teams cap at 8; this is the game default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework confirmed: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it is listed under Modded.

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.