On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak –
Rank#15,426top 69%
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,426 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 76 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
49/ 100
D
Slipped a little: down 253 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····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.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 37 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 09:25 UTC26d ago
1
–
running
0
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
SFBA Lighthouse leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 172.240.229.155:28015 is the address to use.
Is SFBA Lighthouse up, and how steady is its uptime?
The server is up: SFBA Lighthouse is online now. About 5 days 17 hours ago, it restarted, based on the uptime it reports. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Does SFBA Lighthouse perform well?
The average over the last 48 hours was 76 server fps, and it never went below 63. At its peak, it held 207,062 entities, including buildings, deployables and all else in the world. Up to 5,793 MB of memory was used. When fps is low and entities climb, that is lag to players.
Which Rust version is SFBA Lighthouse running?
Rust network protocol 2634 and build 166586 on Windows is what SFBA Lighthouse runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does SFBA Lighthouse wipe its map?
SFBA Lighthouse has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 26 days 8 hours.
What happens on SFBA Lighthouse when wipe day arrives?
The average peak on its recent wipes was 1 players. 37 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does SFBA Lighthouse place in the wider field of Rust servers?
In the top 69% of all ranked servers, SFBA Lighthouse sits at #15,426 for player hours over the last seven days.
How many players does SFBA Lighthouse usually have?
SFBA Lighthouse is showing 0 players right now, with 100 slots in total. Over the past seven days, the average player count was 0.
Tags and filters
What is meant by the tags on SFBA Lighthouse?
You'll see SFBA Lighthouse tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166586 (Build): This runs on build 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does SFBA Lighthouse appear in the Rust Server Score lists and filters?
These Rust Server Score lists count SFBA Lighthouse among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
What settings and rules apply on SFBA Lighthouse?
You will find no gather rate in the name of SFBA Lighthouse. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map SFBA Lighthouse uses?
A procedural map of size 6,000 and seed 7007, generated by the game, is what SFBA Lighthouse runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
What is the way to join SFBA Lighthouse?
To connect, start Rust, press F1, and type client.connect 172.240.229.155:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166586
BuildThis runs on build 166586.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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).