Rust Server TrendsSeismic network · station log
Recording Stations11,715 Players68,833 Active3,595 Wipes · 3 h119 48 h

Station XX-15193 · no signal

Beastmaster DEV (local)

Offline 37.48.20.204:28015 checked 11d ago

moddedoxide
Connect
Players now
0/ 4
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,193
top 70%
Last wipe
18d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15193 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 4 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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. 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
15k10k15k20k9 Oct12 Oct15 Oct18 Oct21 Oct24 Oct

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

wipe-day peak
0players, last three wipes

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 0, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 10 Oct, 13:28 UTC17d ago M0.0steady 0 – running 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 · 155 on average
180/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 127 on average
120/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 116 on average
173/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 88 on average
143/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
16/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
49/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Beastmaster DEV (local)?

Beastmaster DEV (local) uses a procedural map, which the game generates.

Which settings and rules apply on Beastmaster DEV (local)?

No gather rate appears in the name of Beastmaster DEV (local). At the game's default, groups can have up to 8 players. In survival mode, gather, build and raid in the standard game. 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. VAC, Valve's anti-cheat, is switched on.

Live population

How many players are recorded on Beastmaster DEV (local) right now?

No players are recorded on Beastmaster DEV (local) at this moment; it is offline, and the last sighting was 11 days 2 hours ago.

How does Beastmaster DEV (local) rank against other Rust servers?

The last seven days of player hours place Beastmaster DEV (local) at #15,193, in the top 70% of all ranked servers.

Operator and location

How reliably does Beastmaster DEV (local) stay online?

Beastmaster DEV (local) is down at the moment; the last recorded contact was 11 days 2 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 9 October 2026.

Which region does Beastmaster DEV (local) run from?

No region is published by Beastmaster DEV (local). Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 37.48.20.204:28015 is the address it uses.

Which Rust version is Beastmaster DEV (local) running?

Beastmaster DEV (local) is running Rust network protocol 2634 and build 167398 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on Beastmaster DEV (local)?

0 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.

How often does Beastmaster DEV (local) wipe, and on which days?

Too few wipes of Beastmaster DEV (local) are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 18 days 18 hours is how long the current world has been running.

Tags

What do the server tags on Beastmaster DEV (local) mean?

These are the tags Beastmaster DEV (local) publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp4 (Max players): 4 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167398 (Build): It runs game build 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Beastmaster DEV (local) appear?

These Rust Server Trends lists include Beastmaster DEV (local): Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Join the server

What steps get you onto Beastmaster DEV (local)?

To join, enter client.connect 37.48.20.204:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp4,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp4
Max players 4 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167398
Build It runs game build 167398.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running 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.