Rust StatisticsWorking papers on every public Rust server · 31,880 players now

Texas BurningEagle

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 1h ago · 154.16.200.157:28080

Abstract

We describe the public Rust server Texas BurningEagle, reached at 154.16.200.157:28080. It is offline at the last check, against a seven-day mean of 01. It ranks #15,351 of all servers, the top 69%. It last wiped 8d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/500% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,351top 69%
Last wipe8d agono schedule published
Next wipe3–too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
0123406:0015:0000:0009:0019:0004:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
05010015020006:0015:0000:0009:0019:0004:00
Figure 2: Server performance. 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.

4Rank

The server stands in the top 69% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k14 Oct17 Oct20 Oct23 Oct26 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak1players, last three wipes
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Tue 20 Oct, 21:548d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of Texas BurningEagle
Figure 5: The map: Procedural Map, size 4250, seed 924725150. Open on RustMaps.
Table 4: The server's published settings.
Address154.16.200.157:28080
Region–
Max players50
Group limit8, the default
Wipe schedule–
Last wipe20 Oct 2026, 21:54 UTC
Hostname–
First seen14 Oct 2026
MapProcedural Map
Size4250
Seed924725150

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded server list with rates [2] and Rust wipe forecast [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 152 on average41/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average135/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average59/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average19/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average3/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average5/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1Is the performance of Texas BurningEagle smooth?

Over the past 48 hours, it ran at an average of 99 server fps, with a low of 78. Buildings, deployables and all other world objects counted together reached a maximum of 101,564 entities. The peak memory usage was 4,430 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2What location does Texas BurningEagle have?

No region is published by Texas BurningEagle. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 154.16.200.157:28080.

A.3What is the online status and reliability of Texas BurningEagle?

Right now, Texas BurningEagle is offline, and the last time it was seen was 1 hours ago. It last restarted around 40 hours ago, according to its reported uptime. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. The first record of it by Rust Statistics dates to 14 October 2026.

A.4What version of Rust is run on Texas BurningEagle?

Rust network protocol 2634 and build 167781 is the version that Texas BurningEagle runs, on Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.5On what cycle does Texas BurningEagle wipe?

Too few wipes by Texas BurningEagle have been recorded to determine the pattern. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. The world currently in use was created 8 days 7 hours ago.

A.6What happens on Texas BurningEagle when wipe day arrives?

Across its recent wipes, the average peak population was 1 players. The crowd reached its maximum 0 hours after the latest wipe.

Player count

A.7How does Texas BurningEagle compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts Texas BurningEagle at #15,351, within the top 69% of ranked servers.

A.8What is the population level of Texas BurningEagle?

Texas BurningEagle is not online now; 1 hours have passed since it was last seen. The seven-day average for this server is 0 players.

Tags and filters

A.9How should the tags on Texas BurningEagle be interpreted?

gmrust (Game mode): Rust survival, in its standard form; mp50 (Max players): The slot count is 50; ts8 (Group limit): 8 per team, the value the game sets by default; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags Texas BurningEagle publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can Texas BurningEagle be found among the Rust Statistics lists and filters?

The Rust Statistics lists that Texas BurningEagle fits are: Modded Rust servers. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Settings and map

A.11Which settings and rules are in force on Texas BurningEagle?

Its name carries no gather rate for Texas BurningEagle. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. Plugins or settings change the game; the browser files it under Modded. Oxide plugins are running. VAC, Valve's anti-cheat, is enabled.

A.12What is the map for Texas BurningEagle?

Generated by the game from seed 924725150, the procedural map on Texas BurningEagle measures 4,250. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.

How to join

A.13What steps are required to join Texas BurningEagle?

Press F1 inside Rust to open the console and enter client.connect 154.16.200.157:28080. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Rust survival, in its standard form.
mp50Max players. The slot count is 50.
ts8Group limit. 8 per team, the value the game sets by default.
v2634Protocol. The game protocol is 2634; your client must match it to join.
cs167781Build. The game build is 167781.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. No region code is set.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. The game is altered by plugins or settings, so 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.