Skip to the page
RUST ANALYTICS
LIVE45,373PLY11,592SRV
QUOTE 77.134.106.92:28015 Offline checked 1h ago

BURN FSB | PVE | Events | x3

3x moddedoxide
Players · last
0/ 10
+024h
0% full
Day range 0 2
7-day avg 1 peak 3
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 10
0% full
Change · 24h
+0
no reading a day ago
7-day average
1
peak 3
Rank
#4,985
top 23%
Rank · 7d ago
–
not ranked a week ago
Last wipe
7d ago
no schedule published
Next wipe
–
too few wipes seen yet
Group limit
8
8, the default
Gather rate
3x
read from the name
Score
48
player hours, last seven days
Map
3000
Procedural Map · seed 123456
First seen
17 Oct 2026
no hostname published

Players

AveragePeakWipe
00.511.5200:0008:0016:0001:0013:0021:00Wiped Mon 19 Oct, 22:11 UTCWIPE

Hourly average and peak, UTC. Busiest hour of the two days: 2 players.

Server performance

Server fpsWipe
05010015020000:0008:0016:0001:0013:0021:00Wiped Mon 19 Oct, 22:11 UTCWIPE

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 Oct18 Oct19 Oct20 Oct

Top 23% 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 gap
1.3 days
between real wipes
wipe-day peak
3
players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 19 Oct, 22:11 UTC1d ago – – running 0
Sun 18 Oct, 16:02 UTC2d 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
#ServerLastChg 24hPlayers over the last 24 hours24h
1Atlas - EU 3x | No BPs | MondaysEU · groups of 16+ · 3x · weekly · 358 on average452/550−2−0.3%
2Vital Rust - EU Mondays | 3x | No BPsEU · groups of 14+ · 3x · weekly · 148 on average117/175−1−0.8%
3HollowServers.co 3x Solo/Duo |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 134 on average50/100−57−53.4%
4HollowServers.co 3x Solo/Duo/Trio |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 117 on average190/175−258−57.6%
5AceRust.com 3x Solo/Duo|LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 94 on average95/125−100−51.3%
6[US] Upsurge Main | 3x Vanilla | 10/20NA · groups of 12+ · 3x · weekly · 88 on average351/310+334+1921.5%

Quick answers

from the figures on this page

Server Rules

How is BURN FSB | PVE | Events | x3 configured in terms of rules and settings?

A gather rate of 3x appears in the name of BURN FSB | PVE | Events | x3. The default group size of 8 players applies here. survival is the mode, gather, build and raid in the standard game. You can fight and raid other players. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are running. VAC is active.

What is the current map on 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. Because size and seed determine the map, RustMaps offers a view of it from this page.

Player Count

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

In the top 23% of all ranked servers, BURN FSB | PVE | Events | x3 is #4,985 on player hours over the last seven days.

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

At present, BURN FSB | PVE | Events | x3 is offline; the last sighting was 1 hours ago. Average players over seven days: 1; peak: 3. At 18:00 UTC in the last 48 hours, it averaged 2 players, the busiest hour.

Wipe Frequency

What can you expect on wipe day for BURN FSB | PVE | Events | x3?

An average of 3 players marked the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd reached its peak.

How often does BURN FSB | PVE | Events | x3 wipe?

There are too few wipes on record for BURN FSB | PVE | Events | x3 to reveal its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. Its world now is 7 days 12 hours old.

Server Info

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

No region is published by BURN FSB | PVE | Events | x3. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. 77.134.106.92:28015 is its address.

How is the performance on BURN FSB | PVE | Events | x3?

Server fps over the last 48 hours: 81 on average, 54 at the lowest. At its peak it held 51,697 entities: buildings, deployables and the rest of the world. The memory ceiling reached 1,889 MB. What players feel as lag is low fps together with a rising entity count.

BURN FSB | PVE | Events | x3 runs which version of Rust?

Rust network protocol 2634 and build 167781 on Windows is what BURN FSB | PVE | Events | x3 runs. Joining requires the same protocol on your game, which Steam updates.

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

Offline at this moment: BURN FSB | PVE | Events | x3. Last seen 1 hours ago. Its own uptime figure dates the last restart to roughly 3 hours ago. 2 full days have passed with 100% uptime, 48 of 48 hours. The earliest Rust Analytics saw it was 17 October 2026.

Server Tags

How should you interpret the tags on BURN FSB | PVE | Events | x3?

The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp10 (Max players): It holds 10 slots; ts8 (Group limit): Team size stays at the game default of 8; v2634 (Protocol): To join, your game needs protocol 2634; cs167781 (Build): Build 167781; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): Region code: none set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay, which BURN FSB | PVE | Events | x3 publishes. The top of this page and the tags both show its players now, its queue and when its world was made.

On Rust Analytics, which lists and filters feature BURN FSB | PVE | Events | x3?

These Rust Analytics lists include BURN FSB | PVE | Events | x3: 3x Rust servers and Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 3x.

Joining the Server

How can I connect to BURN FSB | PVE | Events | x3?

The console route: start Rust, press F1, enter client.connect 77.134.106.92:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Rust's standard survival mode.
mp10
Max players It holds 10 slots.
ts8
Group limit Team size stays at the game default of 8.
v2634
Protocol To join, your game needs protocol 2634.
cs167781
Build Build 167781.
ptrak
Networking Runs on RakNet, Rust's default network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded Categorised as Modded: plugins or settings alter gameplay.

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.