Rust Server TrendsSeismic network · station log
Recording Stations11,619 Players45,646 Active3,029 Wipes · 3 h120 48 h

Station XX-15120 · recording

RustServer_bayadere

Online 160.251.139.124:28015 checked 9m ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#15,120
top 68%
Last wipe
1d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15120 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 10 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+0into Thu 16:00 UTC
Peak · 48 h
1most players in any hour
Events picked
1wipe on this record, in red
Channel 1 · calibrated

Players

AveragePeakWipe
00.250.50.75108:0004:0011:0017:0000:0006:00Wiped Thu 29 Oct, 00:29 UTCWIPE

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

Server fpsWipe
05010015020008:0004:0011:0017:0000:0006: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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct9 Oct14 Oct20 Oct25 Oct30 Oct

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

Expected events

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 gap
15.8 daysbetween real wipes
wipe-day peak
3players, last three wipes
crowd held
0%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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 29 Oct, 00:29 UTC1d ago – – – – running 0
Tue 13 Oct, 04:50 UTC17d ago M0.5rising 3 halved by day 2 15.8 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 151 on average
51/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 127 on average
121/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 123 on average
83/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 97 on average
20/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 94 on average
73/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
65/ 200
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on RustServer_bayadere?

The procedural map on RustServer_bayadere is size 3,000 with seed 1337, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Custom Map.

Which settings and rules apply on RustServer_bayadere?

The name of RustServer_bayadere gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.

Player counts

How many players are recorded on RustServer_bayadere right now?

At this moment, RustServer_bayadere records 0 players across 10 slots. The seven-day average is 0 players, with a peak of 1. Averaged over the last 48 hours, the busiest hour was 16:00 UTC at 0 players.

How does RustServer_bayadere rank against other Rust servers?

Over the last seven days, RustServer_bayadere recorded enough player hours to reach #15,120 worldwide, placing it in the top 68% of all ranked servers.

Server facts

How reliably does RustServer_bayadere stay online?

As recorded now, RustServer_bayadere is running. Going by the uptime figure it reports, it restarted about 8 hours ago. It was up 92% of the time across the last 7 full days: 154 of 168 hours. 4 October 2026 is when Rust Server Trends first recorded it.

Does RustServer_bayadere hold a steady tick rate?

Its average server fps over the last 48 hours was 136, and it never dropped below 79. Buildings, deployables and all the rest of the world's entities brought it to a high of 45,524. It reached a ceiling of 1,976 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.

Which region does RustServer_bayadere run from?

A region is not published by RustServer_bayadere. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 160.251.139.124:28015.

What build of Rust does RustServer_bayadere use?

On Linux, RustServer_bayadere runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on RustServer_bayadere?

The recent wipes averaged a busiest count of 3 players. 33 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 2.

How often does RustServer_bayadere wipe, and on which days?

The rhythm of RustServer_bayadere cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 26 hours is how long the current world has been running.

Lists and tags

What do the server tags on RustServer_bayadere mean?

These are the tags RustServer_bayadere publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): 10 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does RustServer_bayadere appear?

You will find RustServer_bayadere on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

How to join

How do you connect to RustServer_bayadere?

You can connect by pressing F1 in Rust and typing client.connect 160.251.139.124:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

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 standard Rust survival.
mp10
Max players 10 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.