Rust Data

rustdata.spaceservers154.16.200.157:28015.ipynb

Run all rust-data · live

‹ All servers

Online 154.16.200.157:28080 checked 7m ago

Texas BurningEagle

moddedoxide

Connect

srv = rust.server("154.16.200.157:28015")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,341 # top 69%
last wipe 8d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123407:0016:0001:0009:0019:0004:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020007:0016:0001:0009:0019:0004: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 14 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k14 Oct17 Oct20 Oct23 Oct26 Oct29 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 20 Oct, 21:54 UTC8d ago 1 NaN 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.

display(srv.map, srv.info())

Map

4250 · seed 924725150
Map of Texas BurningEagle
map
Procedural Map
size
4250
seed
924725150
Open on RustMaps

Server

srv.info()
address
154.16.200.157:28080
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
20 Oct 2026, 21:54 UTC
hostname
–
first seen
14 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 151 on average52/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average134/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average70/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average20/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average3/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average6/1000

Quick answers

From the figures on this page.

Population data

What position does Texas BurningEagle take in the server rankings?

Over the last seven days Texas BurningEagle sits at #15,341 on player hours, in the top 69% of ranked servers.

What population does Texas BurningEagle carry?

The sample now reads 0 players for Texas BurningEagle, out of 50 slots. Over the last seven days it averaged 0 players.

About the server

How smoothly does Texas BurningEagle run?

The 48-hour average is 99 server fps, with a low of 78. The entity count peaked at 101,564, covering buildings, deployables and the rest of the world. A high of 4,430 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on Texas BurningEagle?

Version Rust network protocol 2634 and build 167781 on Windows is reported by Texas BurningEagle. Joining needs the same protocol on your game; Steam handles the update.

How reliable is Texas BurningEagle, and is it up?

Texas BurningEagle reports itself online at the current refresh. The uptime it reports puts the last restart about 40 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. Rust Data logged it first on 14 October 2026.

Where does Texas BurningEagle sit?

No region is published by Texas BurningEagle. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 154.16.200.157:28080.

Map and rules

Which settings and rules does Texas BurningEagle run?

The name Texas BurningEagle carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has Texas BurningEagle selected?

Size 4,250, seed 924725150: the procedural map on Texas BurningEagle, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does Texas BurningEagle wipe, and on what schedule?

A rhythm cannot be read from the wipes of Texas BurningEagle on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 8 days 8 hours ago.

What is wipe day on Texas BurningEagle like?

Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.

Tags and filters

Where does Texas BurningEagle appear among Rust Data lists and filters?

These Rust Data lists include Texas BurningEagle: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should you read the server tags on Texas BurningEagle?

The game's server browser reads these tags from Texas BurningEagle: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

What is the way to join Texas BurningEagle?

The manual route: launch Rust, F1, then client.connect 154.16.200.157:28080. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players 50 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs167781
Build Build number: 167781.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 33,162 players 11,622 servers online