RUST METRICSFlight deck · live data
Data live Servers11,789 Players63,543 Populated3,532 Fresh wipes 3 h121 Scan5 min
‹ All servers2.84.244.226:35005
Offline Full Queue Fresh wipe Wipe due No query

Blood Steel and Bad Decisions

Offline 2.84.244.226:35005 checked 30d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#16,955top 71%
Last wipe34d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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, measured since 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Sep28 Sep30 Sep1 Oct3 Oct5 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

When does Blood Steel and Bad Decisions wipe?

Its rhythm cannot be told from the wipes of Blood Steel and Bad Decisions on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 34 days 3 hours ago the current world was made.

Tags

How should you read the tags on Blood Steel and Bad Decisions?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from Blood Steel and Bad Decisions. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Blood Steel and Bad Decisions?

Rust Metrics lists featuring Blood Steel and Bad Decisions: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does Blood Steel and Bad Decisions sit in the rankings?

Player hours over seven days put Blood Steel and Bad Decisions at #16,955, in the top 71% of all ranked servers.

How full does Blood Steel and Bad Decisions get?

Status for Blood Steel and Bad Decisions: offline. Last seen 30 days 9 hours ago.

Server

Where does Blood Steel and Bad Decisions sit?

Reading: location. Blood Steel and Bad Decisions gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 2.84.244.226:35005.

What Rust version is Blood Steel and Bad Decisions on?

Reading: Blood Steel and Bad Decisions, Rust network protocol 2633 and build 165217, Linux. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Blood Steel and Bad Decisions, and is it online now?

Blood Steel and Bad Decisions reports offline. The last reading came 30 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 26 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on Blood Steel and Bad Decisions?

Check: gather rate. The name Blood Steel and Bad Decisions does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Blood Steel and Bad Decisions?

Check: map. Procedural, size 6,000, seed 67821251, generated by the game on Blood Steel and Bad Decisions. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to Blood Steel and Bad Decisions?

Press F1 in Rust and enter client.connect 2.84.244.226:35005. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players The server holds 100 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

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.