Working its way up from the back of the class: #15,222 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
48/ 100
D
Slipped a little: down 583 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (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.
No daily history yet.
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 64% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
BastionDEV [RELEASE] leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 212.112.119.248:28015.
How reliable is BastionDEV [RELEASE], and is it up?
The server is down: BastionDEV [RELEASE] is offline now, with the last sighting 28 days 4 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 1 October 2026, Rust Server Score saw it for the first time.
Which Rust version is BastionDEV [RELEASE] running?
The server BastionDEV [RELEASE] is on Rust network protocol 2634 and build 166462 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does BastionDEV [RELEASE] reset?
There are too few wipes on record for BastionDEV [RELEASE] to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 28 days 5 hours.
Player numbers
Where does BastionDEV [RELEASE] place in the wider field of Rust servers?
In the top 64% of all ranked servers, BastionDEV [RELEASE] sits at #15,222 for player hours over the last seven days.
How many players does BastionDEV [RELEASE] usually have?
The last sighting of BastionDEV [RELEASE] was 28 days 4 hours ago, and it is offline right now.
Lists and filters
What do BastionDEV [RELEASE]'s tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166462 (Build): This runs on build 166462; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags BastionDEV [RELEASE] 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.
Where does BastionDEV [RELEASE] appear in the Rust Server Score lists and filters?
Rust Server Score lists that include BastionDEV [RELEASE]: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
Which rules does BastionDEV [RELEASE] enforce, and what are its settings?
Nothing in the name of BastionDEV [RELEASE] states a gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in 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 Carbon. You are covered by VAC, Valve's anti-cheat.
Which map is in play on BastionDEV [RELEASE]?
A procedural map, generated by the game, is what BastionDEV [RELEASE] runs.
How to join
How do you get onto BastionDEV [RELEASE]?
Enter client.connect 212.112.119.248: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 asmp10,ptrak,$r?,v2634,gmrust,cs166462,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max players10 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166462
BuildThis runs on build 166462.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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. Strongest in momentum (D); standing is the one to work on (F).