On the class lists: F (42), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,335top 69%
Last wipe8d 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 50 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,335 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
100/ 100
A+
Runs smoothly: 99 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
41/ 100
F
Slipped a little: down 2,875 places this week. Nothing a good wipe can't fix.
A term to build on.
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 14 Oct. 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, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 20 Oct, 21:54 UTC8d ago
1
–
running
1
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
You'll find no region listed by Texas BurningEagle. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 154.16.200.157:28080.
How reliable is Texas BurningEagle, and is it up?
Right now, Texas BurningEagle is online. According to its reported uptime, the last restart was about 44 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. On 14 October 2026, Rust Server Score saw it for the first time.
Does Texas BurningEagle perform well?
It averaged 99 server fps over the last 48 hours, with a low of 78. Up to 101,397 entities were in the world, covering buildings, deployables and the rest. Up to 4,430 MB of memory was used. When fps is low and entities climb, that is lag to players.
Which Rust version is Texas BurningEagle running?
You will find Texas BurningEagle on Rust network protocol 2634 and build 167781, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
When does Texas BurningEagle wipe, and how often?
The record holds too few of Texas BurningEagle's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 8 days 11 hours have passed since this world was made.
What should you expect from wipe day on Texas BurningEagle?
Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does Texas BurningEagle sit among Rust servers?
In the top 69% of all ranked servers, Texas BurningEagle sits at #15,335 for player hours over the last seven days.
How many players does Texas BurningEagle usually have?
With 50 slots available, Texas BurningEagle currently has 0 players. Over the past seven days, the average player count was 0.
Lists and filters
How should you read the tags on Texas BurningEagle?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags Texas BurningEagle publishes, and the game's server browser reads them. 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.
Where does Texas BurningEagle appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Texas BurningEagle 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; Last wipe: In the last 2 weeks.
Server rules
What settings and rules apply on Texas BurningEagle?
You will find no gather rate in the name of Texas BurningEagle. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Texas BurningEagle runs which map?
The game generates the procedural map on Texas BurningEagle at size 4,250 with seed 924725150. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How do you get onto Texas BurningEagle?
To connect, start Rust, press F1, and type client.connect 154.16.200.157:28080. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: 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 term to build on. Strongest in performance (A+); population is the one to work on (F).