Offline 37.48.20.204:28015 checked 11d ago
Beastmaster DEV (local)
Connect
srv = rust.server("37.48.20.204:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 10 Oct, 13:28 UTC18d ago | 0 | NaN | running | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 37.48.20.204:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 9 Oct 2026, 17:33 UTC
- hostname
- –
- first seen
- 9 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 102/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 128/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 98/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 30/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 26/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Beastmaster DEV (local) rank?
Player hours over seven days put Beastmaster DEV (local) at #15,193, in the top 70% of the ranked set.
How full does Beastmaster DEV (local) run?
Offline now for Beastmaster DEV (local), with the last sample 11 days 11 hours ago.
Server facts
What Rust version does Beastmaster DEV (local) run?
Rust network protocol 2634 and build 167398 on Windows is what Beastmaster DEV (local) runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Beastmaster DEV (local), and is it online now?
The latest sample has Beastmaster DEV (local) offline, with a last sighting 11 days 11 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 9 October 2026.
In which location is Beastmaster DEV (local) hosted?
For Beastmaster DEV (local), no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 37.48.20.204:28015.
Map and rules
What rules and settings are recorded for Beastmaster DEV (local)?
You will not find a gather rate in the string Beastmaster DEV (local). No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Beastmaster DEV (local) selected?
Beastmaster DEV (local) runs a procedural map, which the game generates.
Wipes and dates
When does Beastmaster DEV (local) wipe, and on what schedule?
The record for Beastmaster DEV (local) holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 19 days 3 hours ago.
On Beastmaster DEV (local), what happens on wipe day?
The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which Rust Data filters and lists contain Beastmaster DEV (local)?
On Rust Data, Beastmaster DEV (local) appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Beastmaster DEV (local) hold?
These tags are published by Beastmaster DEV (local) and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): The server lists 4 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to Beastmaster DEV (local)?
Enter client.connect 37.48.20.204:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.