RUST METRICSFlight deck · live data
Data live Servers11,856 Players101,030 Populated3,903 Fresh wipes 3 h542 Scan5 min
‹ All servers160.251.201.21:28015
Offline Full Queue Fresh wipe Wipe due No query

Rust_bayadere

Offline 160.251.201.21:28015 checked 25d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#16,001top 71%
Last wipe25d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

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 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 Oct5 Oct7 Oct8 Oct10 Oct11 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

How often does Rust_bayadere wipe, and when?

Its rhythm cannot be told from the wipes of Rust_bayadere on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 25 days 11 hours ago.

Tags

How should you read the tags on Rust_bayadere?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $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 Rust_bayadere. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Rust_bayadere?

These Rust Metrics lists carry Rust_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.

Player count

What position does Rust_bayadere hold among Rust servers?

Player hours over seven days put Rust_bayadere at #16,001, in the top 71% of all ranked servers.

What player count does Rust_bayadere carry?

Reading for Rust_bayadere: offline at this moment; last seen 25 days 6 hours ago.

Operator and location

Where does Rust_bayadere sit?

Reading: location. Rust_bayadere gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 160.251.201.21:28015.

What Rust version is Rust_bayadere on?

Reading: Rust_bayadere, Rust network protocol 2634 and build 166652, Linux. To get in, your game needs the same protocol; Steam applies the update.

Is Rust_bayadere up, and how often does it stay up?

Rust_bayadere reports offline. The last reading came 25 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 4 October 2026.

Rules and settings

What settings and rules apply on Rust_bayadere?

Reading the name gives no gather rate for Rust_bayadere. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Rust_bayadere?

Check: map. Procedural, size 3,000, seed 11777, generated by the game on Rust_bayadere. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How do you connect to Rust_bayadere?

Check: join. Open Rust, press F1, then enter client.connect 160.251.201.21: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?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Game build reading: 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.