Rust Server IndexCard catalogue of Rust servers

Holdings11,659 servers33,003 players78 fresh wipes

Call no.3X5656 On the shelf · online

BURN FSB | PVE | Events | x3

Online 77.134.106.92:28015 checked 14m ago

Subjects 1. 3x 2. modded3. oxide
Players now
0/ 10
0% full
7-day average
0
peak 4
Rank
#5,656
top 25%
Last wipeWiped13 OCT2026 · 15d 17h ago
15d ago · no schedule published
Next wipe
–
too few wipes seen yet
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
0123405:0014:0023:0007:0016:0002:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

02040608005:0014:0023: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.

Record sheet C · appended

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.

Record sheet D · loan terms

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 daysbetween real wipes
wipe-day peak
4players, 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.

Record sheet E · date due

Wipes

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

Shelf list · shelved beside it

Similar servers

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

EU3X
Atlas - EU 3x | No BPs | MondaysEU · groups of 16+ · 3x · weekly · 390 on average
157/ 200
EU3X
Vital Rust - EU Mondays | 3x | No BPsEU · groups of 14+ · 3x · weekly · 177 on average
70/ 125
NA3X
HollowServers.co 3x Solo/Duo |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 127 on average
307/ 315
NA3X
HollowServers.co 3x Solo/Duo/Trio |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 122 on average
97/ 100
3X
FLAME RUST #1 [ NOLIMIT | x3 | MAGIC ] WIPE 27.10groups of 30+ · 3x · weekly · 113 on average
16/ 350
NA3X
AceRust.com 3x Solo/Duo|LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 105 on average
46/ 100
Reference desk

Quick answers

From the figures on this page.

Rules and settings

Where can you read the rules and settings that apply on BURN FSB | PVE | Events | x3?

BURN FSB | PVE | Events | x3 sets gather at 3x, as its name shows. The default group limit of 8 players applies. Filed under survival, gather, build and raid: the standard game. Fighting and raiding other players is permitted. The server browser lists it under Modded; plugins or settings alter the game. Oxide plugins are run on it. VAC, Valve's anti-cheat, is enabled.

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

BURN FSB | PVE | Events | x3 runs a procedural map of size 3,000 with seed 123456, generated by the game. From this page you can view the map on RustMaps; the same size and seed give the same map.

Lists and filters

Which lists and filters on Rust Server Index is BURN FSB | PVE | Events | x3 filed under?

Filed under these Rust Server Index lists is BURN FSB | PVE | Events | x3: 3x Rust servers, filed and Modded Rust servers, filed by play style. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.

Which tags are attached to BURN FSB | PVE | Events | x3, and what do they stand for?

These are the tags BURN FSB | PVE | Events | x3 publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp10 (Max players): The queue ceiling sits at 10; ts8 (Group limit): Teams cap at 8, the default setting; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): It runs build 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region code field is left empty; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or changed settings put this under Modded. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.

Wipe dates

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

At their busiest, its recent wipes drew 4 players on average. 44 hours into the latest wipe, the crowd reached its peak.

Which wipe timetable does BURN FSB | PVE | Events | x3 follow?

The record holds too few of BURN FSB | PVE | Events | x3's wipes to tell its rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. 15 days 17 hours is when its current world was made.

Population

Where does BURN FSB | PVE | Events | x3 sit in the rankings?

The seven-day player-hours ranking places BURN FSB | PVE | Events | x3 at #5,656, among the top 25% of ranked servers.

What does the player count on BURN FSB | PVE | Events | x3 look like?

Filed under live counts: BURN FSB | PVE | Events | x3, 0 players on 10 slots at present. The seven-day average is 0 players; the peak reached 4. Filed under busiest hour: 11:00 UTC in the last 48 hours, averaging 2 players.

Server facts

What version does BURN FSB | PVE | Events | x3 use?

Rust network protocol 2635 and build 168909, on Windows, is what BURN FSB | PVE | Events | x3 runs. To join you need the same protocol; Steam handles the update.

What is the uptime and current status of BURN FSB | PVE | Events | x3?

Right now BURN FSB | PVE | Events | x3 is up and running. Its reported uptime gives the last restart as roughly 38 hours ago. Of the last 7 full days, 165 of 168 hours were up, 98% of the time. It was first recorded by Rust Server Index on 17 October 2026.

Is the performance on BURN FSB | PVE | Events | x3 good?

Averaged over the last 48 hours, server fps was 59, with a low of 55. Buildings, deployables and everything else in the world came to as many as 54,088 entities. Memory use reached as much as 2,151 MB. Lag, to players, is low fps and an entity count that climbs.

Where in the world is BURN FSB | PVE | Events | x3 hosted?

BURN FSB | PVE | Events | x3 gives no region at all. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. You will reach it at 77.134.106.92:28015.

Connecting

What steps lead onto BURN FSB | PVE | Events | x3?

Two ways in. Type client.connect 77.134.106.92:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.

Subject headings explained

Server tags

What each one means.

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

Game

gmrust
Game mode Survival on standard Rust rules.
mp10
Max players The queue ceiling sits at 10.
ts8
Group limit Teams cap at 8, the default setting.
v2635
Protocol Your client must run protocol 2635 to connect.
cs168909
Build It runs build 168909.
ptrak
Networking The standard RakNet layer carries the connection.
$r?
Region code The region code field is left empty.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded Plugins or changed settings put this 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.