RUST METRICSFlight deck · live data
Data live Servers11,834 Players90,952 Populated3,739 Fresh wipes 3 h423 Scan5 min
‹ All servers160.251.139.124:28015
Online Full Queue Fresh wipe Wipe due No query

RustServer_bayadere

Online 160.251.139.124:28015 checked 9m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Thu 20:00 UTC
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 164 SERVER FPS

Server fps

48 h low 79 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 42,240 ×1000

Entities

48 h range 41,958–45,524 · memory 1,300 MB
1239 ET SINCE RESTART 00:51

Uptime

0 h 51 min since its last restart, at the last reading
7-day average0peak 1
Rank#15,119top 68%
Last wipe16h agono schedule published
Next wipe–too few wipes seen yet
Memory1,300MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75122:0004:0001:0007:0014:0020:00Wiped Thu 29 Oct, 00:29 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
05010015020022:0004:0001:0007:0014:0020: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.

REC 3

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.

PLAN

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 00:29 UTC20h 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on RustServer_bayadere?

The busiest point of its recent wipes drew 3 players on average. Peak crowd on the latest wipe: 33 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell below half by day 2 when it didn't.

What wipe timing does RustServer_bayadere follow?

To tell the rhythm of RustServer_bayadere, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 16 hours ago.

Tags

Which tags does RustServer_bayadere carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game from RustServer_bayadere. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does RustServer_bayadere appear in Rust Metrics lists and filters?

These Rust Metrics lists carry RustServer_bayadere: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.

Population

What position does RustServer_bayadere hold among Rust servers?

Player hours over seven days put RustServer_bayadere at #15,119, in the top 68% of all ranked servers.

How full does RustServer_bayadere get?

Current headcount on RustServer_bayadere: 0 players, 10 slots available. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 16:00 UTC, averaging 0 players at that hour.

Server

What location is RustServer_bayadere hosted in?

No region comes from RustServer_bayadere. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 160.251.139.124:28015.

What Rust version is RustServer_bayadere on?

Rust network protocol 2635 and build 168909 on Linux is the build RustServer_bayadere runs. To get in, your game needs the same protocol; Steam applies the update.

How does RustServer_bayadere perform?

Check: fps. Average 124 server fps over the last 48 hours, low of 79. Within range. Peak entity count: 45,524. Buildings, deployables and all else included. Memory peak: 1,976 MB. What players call lag comes from low fps and an entity count on the rise.

How reliable is RustServer_bayadere, and is it online now?

RustServer_bayadere reports online. Status: normal. Reading: uptime. About 51 minutes ago it restarted, on its own count. Uptime for the last 7 full days: 154 of 168 hours, or 92%. The first sighting on Rust Metrics was 4 October 2026.

Rules and settings

What settings and rules apply on RustServer_bayadere?

Check: gather rate. The name RustServer_bayadere does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

What map is RustServer_bayadere on?

From seed 1337, the game generates the procedural map on RustServer_bayadere. Its size is 3,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Map name, as listed: Custom Map.

Connection

How can you get onto RustServer_bayadere?

Check: join. Open Rust, press F1, then enter client.connect 160.251.139.124:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock 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.