Rust Data

rustdata.spaceservers185.216.144.98:28015.ipynb

Run all rust-data · live

‹ All servers

Offline 185.216.144.98:28080 checked 29d ago

STAGING BRANCH - RUSTEAMEESTA

moddedoxide

Connect

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

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #16,853 # top 71%
last wipe 30d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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 24 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 Sep23 Sep26 Sep30 Sep3 Oct6 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Tue 29 SepThu 24 SepTue 15 Sep
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 29 Sep, 13:59 UTC30d ago 0 NaN running 0
1 Thu 24 Sep, 16:00 UTC35d ago 0 NaN 4.9 days 0
2 Tue 15 Sep, 14:49 UTC44d ago 3 halved by day 1 9 days 0
3 Mon 14 Sep, 11:22 UTC45d ago 3 NaN 1.1 days 1
4 Sun 13 Sep, 19:43 UTC45d ago 3 NaN 0.7 days 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

1999 · seed 1578372894
Map of STAGING BRANCH - RUSTEAMEESTA
map
Procedural Map
size
1999
seed
1578372894
Open on RustMaps

Server

srv.info()
address
185.216.144.98:28080
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
29 Sep 2026, 13:59 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
0ShockRust | Blue | NoLimitno group limit · 151 on average157/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average133/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average185/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average94/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 88 on average231/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average348/350

Quick answers

From the figures on this page.

Population

What position does STAGING BRANCH - RUSTEAMEESTA take in the server rankings?

Over the last seven days STAGING BRANCH - RUSTEAMEESTA sits at #16,853 on player hours, in the top 71% of ranked servers.

How many players does STAGING BRANCH - RUSTEAMEESTA hold at once?

Offline now for STAGING BRANCH - RUSTEAMEESTA, with the last sample 29 days 21 hours ago.

Server facts

What is the Rust version on STAGING BRANCH - RUSTEAMEESTA?

Rust network protocol 2633 and build 165217 on Windows is what STAGING BRANCH - RUSTEAMEESTA runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is STAGING BRANCH - RUSTEAMEESTA, and is it online now?

STAGING BRANCH - RUSTEAMEESTA is offline at this refresh; the last response came 29 days 21 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.

Which location does STAGING BRANCH - RUSTEAMEESTA run from?

There is no region published for STAGING BRANCH - RUSTEAMEESTA. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 185.216.144.98:28080.

Map and rules

Which rules apply on STAGING BRANCH - RUSTEAMEESTA, and what settings?

No gather rate appears in the name: STAGING BRANCH - RUSTEAMEESTA. No custom cap; the default of 8 players per group stands. survival is the game mode here, and 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. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

What is the map on STAGING BRANCH - RUSTEAMEESTA?

STAGING BRANCH - RUSTEAMEESTA runs a procedural map of size 1,999 with seed 1578372894, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

When does STAGING BRANCH - RUSTEAMEESTA wipe, and on what schedule?

STAGING BRANCH - RUSTEAMEESTA wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 30 days 3 hours ago, and that is the one in play.

On STAGING BRANCH - RUSTEAMEESTA, what happens on wipe day?

Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.

Tags and filters

Which lists on Rust Data hold STAGING BRANCH - RUSTEAMEESTA, and which filters?

On Rust Data, STAGING BRANCH - RUSTEAMEESTA appears in these lists: 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.

How should you read the server tags on STAGING BRANCH - RUSTEAMEESTA?

These tags are published by STAGING BRANCH - RUSTEAMEESTA and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Build number: 165217; 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 Modded section lists it, because plugins or settings change the game. 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.

Connecting

What is the way into STAGING BRANCH - RUSTEAMEESTA?

Enter client.connect 185.216.144.98:28080 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players 50 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2633
Protocol Protocol 2633 is required; a different game version cannot connect.
cs165217
Build Build number: 165217.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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 99,159 players 11,894 servers online