StatusLive Servers online11,898 Players103,740 Populated4,020 Wiped · 3 h406 Interval5 min Date29 OCT 2026

DWG RG-S6773Server sheetchecked 8h ago

BURN FSB | PVE | Events | x3

Offline 77.134.106.92:28015 checked 8h ago

3x moddedoxide
Connect
Players now 0/ 10 0% full
7-day average0peak 4
Rank#6,773top 30%
Last wipe16d agono schedule published
Next wipe–too few wipes seen yet
Fig. 1

Players

AveragePeak
00.250.50.75120:0003:0011:0019:0003:0010:00

Hourly average and peak, UTC.

Fig. 1Players on BURN FSB | PVE | Events | x3
Fig. 2

Server performance

02040608020:0003:0011:0019:0003:0010: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k17 Oct19 Oct22 Oct24 Oct27 Oct29 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 19 Oct, 22:11 UTC9d ago 4 – running 0
Sun 18 Oct, 16:02 UTC11d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Atlas - EU 3x | No BPs | MondaysEU · groups of 16+ · 3x · weekly · 386 on average
554 / 650
02
Vital Rust - EU Mondays | 3x | No BPsEU · groups of 14+ · 3x · weekly · 179 on average
232 / 275
03
HollowServers.co 3x Solo/Duo |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 129 on average
163 / 180
04
HollowServers.co 3x Solo/Duo/Trio |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 121 on average
41 / 100
05
FLAME RUST #1 [ NOLIMIT | x3 | MAGIC ] WIPE 27.10groups of 30+ · 3x · weekly · 116 on average
94 / 350
06
AceRust.com 3x Solo/Duo|LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 105 on average
104 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

Is BURN FSB | PVE | Events | x3 online, and what uptime has been recorded?

Last seen 8 hours ago; right now BURN FSB | PVE | Events | x3 is offline. About 46 hours ago is when it last restarted, measured from the uptime it reports. 165 of 168 hours up over the last 7 full days, which is 98% of the time. On 17 October 2026 is when Rust Graphs first saw it.

Is BURN FSB | PVE | Events | x3 stable in the figures recorded?

Average server fps over the last 48 hours is 59; the lowest was 36. Counted at its highest: 54,088 entities, buildings, deployables and the rest of the world included. 2,152 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for BURN FSB | PVE | Events | x3?

No region is published by BURN FSB | PVE | Events | x3. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. 77.134.106.92:28015 is its address.

On which Rust version is BURN FSB | PVE | Events | x3 running?

The platform is Windows and the version is Rust network protocol 2635 and build 168909 on BURN FSB | PVE | Events | x3. The same protocol is required for joining, and Steam updates your game to it.

Counts

What does the population history show for BURN FSB | PVE | Events | x3?

The latest refresh records BURN FSB | PVE | Events | x3 as offline, last seen 8 hours ago. Averaged across seven days, the player count is 0, with a peak of 4. Over the last 48 hours the busiest hour was 10:00 UTC, at an average of 0 players.

What rank has been recorded for BURN FSB | PVE | Events | x3?

Player hours over seven days place BURN FSB | PVE | Events | x3 at #6,773, within the top 30% of ranked servers.

Schedules

On BURN FSB | PVE | Events | x3, what does the data show for wipe day?

At their busiest, its recent wipes drew 4 players on average. 44 hours after the latest wipe, the crowd peaked.

Which times and days are wipes plotted at on BURN FSB | PVE | Events | x3?

Too few wipes are on record for BURN FSB | PVE | Events | x3 to show its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. 16 days 8 hours ago the current world was made.

Rules and settings

Which settings does BURN FSB | PVE | Events | x3 run, and what rules?

BURN FSB | PVE | Events | x3 takes its gather rate from its name: 3x. No limit is published beyond the default: 8 players per group. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. Plugins or settings change the game, and the browser lists it as Modded. Plugins run: Oxide. Anti-cheat: VAC, from Valve, is on.

Which map has BURN FSB | PVE | Events | x3 loaded?

Seed 123456 and size 3,000 define the procedural map BURN FSB | PVE | Events | x3 generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Tags

On Rust Graphs, which lists and filters contain BURN FSB | PVE | Events | x3?

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

Which meaning is attached to each tag on BURN FSB | PVE | Events | x3?

Tags published by BURN FSB | PVE | Events | x3, and read by the game's server browser: gmrust (Game mode): Survival in standard Rust style; mp10 (Max players): The slot count is 10; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is 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.

How to join

What is the way to connect to BURN FSB | PVE | Events | x3?

Enter client.connect 77.134.106.92:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust style.
mp10
Max players The slot count is 10.
ts8
Group limit The default team size of 8 applies.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded Plugins or settings change 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.

KeyTag string decoded