Rust Data

rustdata.spaceservers160.251.139.124:28017.ipynb

Run all rust-data · live

‹ All servers

Online 160.251.139.124:28015 checked 10m ago

RustServer_bayadere

moddedoxide

Connect

srv = rust.server("160.251.139.124:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak 1
rank #15,142 # top 68%
last wipe 18h ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.250.50.75100:0006:0003:0009:0016:0022:00Wiped Thu 29 Oct, 00:29 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
05010015020000:0006:0003:0009:0016:0022:00Wiped Thu 29 Oct, 00:29 UTCWIPE

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 4 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
15k10k15k20k4 Oct9 Oct14 Oct19 Oct24 Oct29 Oct

Top 68% 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.

usual gap15.8 daysbetween real wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 2

The first 48 hours of its last wipes

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 29 Oct, 00:29 UTC23h ago NaN NaN running 0
1 Tue 13 Oct, 04:50 UTC16d ago 3 halved by day 2 15.8 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

3000 · seed 1337
Map of RustServer_bayadere
map
Custom Map
size
3000
seed
1337

Server

srv.info()
address
160.251.139.124:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
29 Oct 2026, 05:15 UTC
hostname
–
first seen
4 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 · 149 on average32/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average128/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 120 on average49/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average16/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 93 on average50/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average238/260

Quick answers

From the figures on this page.

Population data

What position does RustServer_bayadere take in the server rankings?

Rank #15,142 on seven-day player hours for RustServer_bayadere, within the top 68% of all ranked servers.

How many players does RustServer_bayadere hold at once?

Current row: 0 players on RustServer_bayadere, against 10 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 16:00 UTC, mean 0 players.

Server data

What does performance look like on RustServer_bayadere?

Averaged over 48 hours: 129 server fps, never under 79. Buildings, deployables and all else in the world took the count as high as 45,524 entities. A high of 1,976 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

What Rust version does RustServer_bayadere run?

Version Rust network protocol 2635 and build 168909 on Linux is reported by RustServer_bayadere. Steam updates your game for you, but the protocol must match to join.

How reliable is RustServer_bayadere, and is it up?

The current sample puts RustServer_bayadere online. The uptime it reports puts the last restart about 11 minutes ago. Uptime of 92% across the last 7 full days: 154 hours of 168. Rust Data logged it first on 4 October 2026.

In which location is RustServer_bayadere hosted?

There is no region published for RustServer_bayadere. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 160.251.139.124:28015.

Map and rules

Which rules apply on RustServer_bayadere, and what settings?

The name RustServer_bayadere carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.

Which map has RustServer_bayadere loaded?

RustServer_bayadere runs a procedural map of size 3,000 with seed 1337, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Recorded under map name: Custom Map.

Wipes and dates

When does RustServer_bayadere wipe, and how often?

A rhythm cannot be read from the wipes of RustServer_bayadere on record, which are too few. 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 18 hours ago, and that is the one in play.

On RustServer_bayadere, what happens on wipe day?

Across recent wipes the busiest point averaged 3 players. 33 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The drop under half arrived by day 2 in the other cases.

Lists and tags

Where does RustServer_bayadere appear among Rust Data lists and filters?

On Rust Data, RustServer_bayadere appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.

How should you read the server tags on RustServer_bayadere?

These tags are published by RustServer_bayadere and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 RustServer_bayadere?

The manual route: launch Rust, F1, then client.connect 160.251.139.124:28015. 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 mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players 10 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins 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.

Rust Data 65,587 players 11,740 servers online