Rust Data

rustdata.spaceservers157.85.90.179:28016.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.90.179:28015 checked 12m ago

Texas Tea

Connect

srv = rust.server("157.85.90.179:28016")
print(srv.connect_command)

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123400:0009:0018:0003:0012:0022:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020000:0009:0018:0003:0012:0022: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 17 Sep. 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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 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, 7 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 3 Oct, 12:17 UTC25d ago 1 NaN 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.

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

Map

6000 · seed 67
Map of Texas Tea
map
Procedural Map
size
6000
seed
67
Open on RustMaps

Server

srv.info()
address
157.85.90.179:28015
region
–
max players
150
group limit
8, the default
wipe schedule
–
last wipe
3 Oct 2026, 12:17 UTC
hostname
–
first seen
13 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 560 on average312/375
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average196/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 292 on average36/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 291 on average23/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average51/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 251 on average63/200

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Texas Tea rank?

Player hours over seven days put Texas Tea at #15,349, in the top 69% of the ranked set.

How full does Texas Tea run?

Current row: 0 players on Texas Tea, against 150 slots. Over the last seven days it averaged 0 players.

Server data

How smoothly does Texas Tea run?

The 48-hour average is 74 server fps, with a low of 59. Buildings, deployables and all else in the world took the count as high as 202,933 entities. A high of 6,861 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

What Rust version does Texas Tea run?

Rust network protocol 2635 and build 168909 on Linux is what Texas Tea runs. The protocol has to match before you can join, and Steam does the updating.

Is Texas Tea up, and what does its uptime show?

Texas Tea reports itself online at the current refresh. The uptime it reports puts the last restart about 5 days 2 hours ago. Over the last 7 full days the hours up number 168 of 168, 100%. Its earliest recorded date in Rust Data is 13 September 2026.

Where does Texas Tea sit?

For Texas Tea, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 157.85.90.179:28015 is its address.

Rules, settings, map

Which rules apply on Texas Tea, and what settings?

The name Texas Tea carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Community is its browser category. VAC, Valve's anti-cheat, is enabled.

Which map has Texas Tea loaded?

The game generates the map on Texas Tea: procedural, size 6,000, seed 67. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does Texas Tea wipe, and how often?

The record for Texas Tea holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 25 days 11 hours ago.

On Texas Tea, what happens on wipe day?

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

Lists and tags

Which lists on Rust Data hold Texas Tea, and which filters?

The Rust Data lists that Texas Tea fits are: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the server tags on Texas Tea?

The game's server browser reads these tags from Texas Tea: gmrust (Game mode): Survival play, standard Rust; mp150 (Max players): The server lists 150 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

How can I connect to Texas Tea?

In Rust, F1 opens the console: type client.connect 157.85.90.179:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp150,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp150
Max players The server lists 150 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build The server runs build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

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 51,299 players 11,732 servers online