On the class lists: D (54), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak 4
Rank#5,648top 25%
Last wipe15d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
2/ 100
F
A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
75/ 100
B
Holds a respectable place: #5,648 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
99/ 100
A+
Runs smoothly: 60 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
42/ 100
F
Slipped a little: down 946 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 25% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
W······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 4, 44 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
NA · groups of 8+ · 3x · biweekly · 105 on average
50 / 100
Quick answers
from the figures on this page
About the server
Which region is BURN FSB | PVE | Events | x3 based in?
BURN FSB | PVE | Events | x3 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 77.134.106.92:28015 is the address to use.
How reliable is BURN FSB | PVE | Events | x3, and is it up?
The server is up: BURN FSB | PVE | Events | x3 is online now. According to its reported uptime, the last restart was about 34 hours ago. For the last 7 full days, it was up 156 of 168 hours, or 93% of the time. The first sighting by Rust Server Score was on 17 October 2026.
Does BURN FSB | PVE | Events | x3 perform well?
It never fell below 55 server fps in the last 48 hours, averaging 60. Buildings, deployables and everything else in the world added up to as many as 54,088 entities. At its highest, it used 2,151 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does BURN FSB | PVE | Events | x3 sit?
The server BURN FSB | PVE | Events | x3 is on Rust network protocol 2635 and build 168909 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does BURN FSB | PVE | Events | x3 wipe its map?
There are too few wipes on record for BURN FSB | PVE | Events | x3 to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 15 days 13 hours.
What happens on BURN FSB | PVE | Events | x3 when wipe day arrives?
Recent wipes have peaked at 4 players on average. 44 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does BURN FSB | PVE | Events | x3 place in the wider field of Rust servers?
In the top 25% of all ranked servers, BURN FSB | PVE | Events | x3 sits at #5,648 for player hours over the last seven days.
Is BURN FSB | PVE | Events | x3 a busy server?
BURN FSB | PVE | Events | x3 is showing 0 players right now, with 10 slots in total. It peaked at 4 and averaged 0 players over the last seven days. Over the last 48 hours, the peak hour was 11:00 UTC, averaging 2 players.
Lists and filters
How should you read the tags on BURN FSB | PVE | Events | x3?
The game's browser takes its cue from the tags BURN FSB | PVE | Events | x3 has set: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show BURN FSB | PVE | Events | x3?
These Rust Server Score lists count BURN FSB | PVE | Events | x3 among them: 3x Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.
Rules and settings
How is BURN FSB | PVE | Events | x3 set up, and what rules does it keep?
Going by its name, BURN FSB | PVE | Events | x3 runs 3x gather. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
BURN FSB | PVE | Events | x3 runs which map?
BURN FSB | PVE | Events | x3 runs a game-generated procedural map at size 3,000, seed 123456. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How should you connect to BURN FSB | PVE | Events | x3?
To connect, start Rust, press F1, and type client.connect 77.134.106.92:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).