Working its way up from the back of the class: #15,193 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
37/ 100
F
Slipped a little: down 3,843 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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 peak0players, last three wipes
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
Wiped
Peak
Crowd
Lasted
Players before
Sat 10 Oct, 13:28 UTC18d ago
0
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by Beastmaster DEV (local). Rust Server Score reports the location a server gives; it does not check where the machine actually is. 37.48.20.204:28015 is the address to use.
How reliable is Beastmaster DEV (local), and is it up?
You cannot join now: Beastmaster DEV (local) is offline, last seen 11 days 17 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 9 October 2026, Rust Server Score saw it for the first time.
Which Rust version is Beastmaster DEV (local) running?
The server Beastmaster DEV (local) is on Rust network protocol 2634 and build 167398 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Beastmaster DEV (local) reset?
There are too few wipes on record for Beastmaster DEV (local) to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 19 days 10 hours have passed since this world was made.
What should you expect from wipe day on Beastmaster DEV (local)?
Recent wipes have peaked at 0 players on average. 0 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does Beastmaster DEV (local) sit among Rust servers?
Over the last seven days, Beastmaster DEV (local) has #15,193 for player hours, in the top 70% of all ranked servers.
What does the population on Beastmaster DEV (local) look like?
Beastmaster DEV (local) is offline at the moment; the last time it was seen was 11 days 17 hours ago.
Tags
What do Beastmaster DEV (local)'s tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp4 (Max players): 4 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167398 (Build): Build number: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags Beastmaster DEV (local) publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Beastmaster DEV (local)?
These Rust Server Score lists count Beastmaster DEV (local) among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on Beastmaster DEV (local)?
You will find no gather rate in the name of Beastmaster DEV (local). With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Beastmaster DEV (local) runs which map?
A procedural map, generated by the game, is what Beastmaster DEV (local) runs.
How to join
What is the way to join Beastmaster DEV (local)?
Enter client.connect 37.48.20.204:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp4
Max players4 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167398
BuildBuild number: 167398.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A term to build on. Even marks across the subjects, from F to F.