RUST METRICSFlight deck · live data
Data live Servers11,700 Players38,808 Populated2,943 Fresh wipes 3 h91 Scan5 min
‹ All servers77.134.106.92:28015
Online Full Queue Fresh wipe Wipe due No query

BURN FSB | PVE | Events | x3

Online 77.134.106.92:28015 checked 11m ago

3x moddedoxide
COM 1 · connect

Server instruments

last reading Thu 00:00 UTC
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 59 SERVER FPS

Server fps

48 h low 55 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 51,529 ×1000

Entities

48 h range 50,650–54,088 · memory 1,924 MB
1239 ET SINCE RESTART 1D 12H

Uptime

1 days 12 hours since its last restart, at the last reading
7-day average0peak 4
Rank#5,653top 25%
Last wipe15d agono schedule published
Next wipe–too few wipes seen yet
Memory1,924MB48 h peak 4 players
REC 1

Players

AveragePeak
0123403:0012:0021:0005:0014:0000:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608003:0012:0021:0005:0014:0000: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.

REC 3

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.

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.

LOG

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on BURN FSB | PVE | Events | x3 when wipe day comes?

An average of 4 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 44 hours in.

When does BURN FSB | PVE | Events | x3 wipe?

To tell the rhythm of BURN FSB | PVE | Events | x3, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 15 days 15 hours ago the current world was made.

Tags

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

Tags published by BURN FSB | PVE | Events | x3, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

On Rust Metrics, BURN FSB | PVE | Events | x3 sits in these lists: 3x Rust servers, checked live and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.

Occupancy

What position does BURN FSB | PVE | Events | x3 hold among Rust servers?

Player hours over seven days put BURN FSB | PVE | Events | x3 at #5,653, in the top 25% of all ranked servers.

How full does BURN FSB | PVE | Events | x3 get?

0 of 10 slots are filled on BURN FSB | PVE | Events | x3 right now. Check: players over seven days. Average 0, peak 4. The last 48 hours peaked at 11:00 UTC, averaging 2 players at that hour.

Operator and location

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

No region comes from BURN FSB | PVE | Events | x3. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 77.134.106.92:28015.

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

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

Is performance on BURN FSB | PVE | Events | x3 within range?

Over the last 48 hours the average was 60 server fps; the floor was 55. Peak entity count: 54,088. Buildings, deployables and all else included. Memory peak: 2,151 MB. What players call lag comes from low fps and an entity count on the rise.

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

Check: connection. BURN FSB | PVE | Events | x3 is online at this moment. Check: restart. The uptime it reports puts the last restart about 36 hours ago. Reading: 98% uptime over the last 7 full days. It was up 165 of 168 hours. The first sighting on Rust Metrics was 17 October 2026.

Settings and map

How is BURN FSB | PVE | Events | x3 configured, and what rules are in force?

The name carries the rate: 3x gather on BURN FSB | PVE | Events | x3. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on BURN FSB | PVE | Events | x3?

From seed 123456, the game generates the procedural map on BURN FSB | PVE | Events | x3. Its size is 3,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

What do you do to join BURN FSB | PVE | Events | x3?

Press F1 in Rust and enter client.connect 77.134.106.92:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

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 it.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

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.