Rust Server Analytics 103,775 players11,888 servers
All servers
Drill-through Server detail

RustServer_bayadere

Online 160.251.139.124:28015 checked 6m ago

Drill-through
FilterServeris RustServer_bayadere
Attributes
moddedoxide
Last refreshed
Players now 0/ 10
7-day average 0 peak 1
Rank #15,158 top 68%
Last wipe 13h ago no schedule published
Next wipe – too few wipes seen yet
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeakWipe
00.250.50.75119:0001:0008:0004:0011:0017:00Wiped Thu 29 Oct, 00:29 UTCWIPE

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
Server fpsWipe
05010015020019:0001:0008:0004:0011:0017: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
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

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
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 00:29 UTC17h ago – – running 0
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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
ShockRust | Blue | NoLimit no group limit · 151 on average 137 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 126 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average 196 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 95 on average 79 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 89 on average 225 / 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 84 on average 348 / 350

Quick answers

from the figures on this page

Wipe data

The wipe schedule for RustServer_bayadere: what is it?

Too few wipes on record for RustServer_bayadere to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. The current world dates from 13 hours.

Wipe day on RustServer_bayadere: what should you expect?

The average busiest count over recent wipes is 3 players. Peak population for the latest wipe came 33 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. By day 2 it had fallen below half where the hold failed.

Server details

What is the hosting location of RustServer_bayadere?

No region is published by RustServer_bayadere. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 160.251.139.124:28015 is its address.

Which Rust version is RustServer_bayadere on?

On Linux, RustServer_bayadere runs Rust network protocol 2635 and build 168909. Joining requires the same protocol on your game; Steam handles the update.

What uptime does RustServer_bayadere show, and is it up?

RustServer_bayadere reports online at the current check. Its reported uptime indicates a restart roughly 10 hours ago. Uptime over the last full days (7) was 92%, or 154 of 168 hours. The first sighting of it by Rust Server Analytics was on 4 October 2026.

Does RustServer_bayadere perform well?

The 48-hour average was 122 server fps; the low was 79. At its highest the entity count was 45,524, including buildings, deployables and all else. At its highest, memory use was 2,086 MB. A climbing entity count and low fps are the lag players perceive.

Lists and tags

What do RustServer_bayadere's tags stand for?

Tags from RustServer_bayadere, as read by the game's server browser, are: gmrust (Game mode): Rust survival, standard ruleset; mp10 (Max players): Player slots: 10; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): The Modded section, because plugins or settings modify play. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.

Where does RustServer_bayadere appear across Rust Server Analytics's lists and filters?

These Rust Server Analytics lists include RustServer_bayadere: Modded Rust servers: live data. 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 24 hours.

Population

Where does RustServer_bayadere sit among Rust servers?

On player hours over seven days, RustServer_bayadere ranks #15,158, within the top 68% of ranked servers.

What is the population of RustServer_bayadere?

Of 10 slots, 0 are filled on RustServer_bayadere at this refresh. Averaging 0 players across seven days, the server reached a peak of 1. Across the last 48 hours, 16:00 UTC shows the highest average: 0 players.

Settings

What settings and rules does RustServer_bayadere use?

No gather rate is given in the name of RustServer_bayadere. The game's default 8-player group limit is in force. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. The Modded category lists it; plugins or settings change the game. Plugins from Oxide are in use. The server runs with VAC, Valve's anti-cheat, enabled.

The map on RustServer_bayadere: which one is it?

RustServer_bayadere uses a procedural map of size 3,000 with seed 1337, generated by the game. Size and seed fix the map, so a RustMaps view is available from this page. Named map: Custom Map.

How to join

What is the way onto RustServer_bayadere?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 160.251.139.124:28015.

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival, standard ruleset.
mp10
Max players Player slots: 10.
ts8
Group limit Team cap of 8, the stock game setting.
v2635
Protocol Joining needs your game on protocol 2635.
cs168909
Build Build number 168909.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code A region code is not set.

Mods and access

^o
Oxide It runs Oxide (uMod) for plugins.
^z
Modded The Modded section, because plugins or settings modify play.

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.