RUST METRICSFlight deck · live data
Data live Servers11,811 Players72,496 Populated3,745 Fresh wipes 3 h141 Scan5 min
‹ All servers2.84.253.158:35005
Offline Full Queue Fresh wipe Wipe due No query

Blood Steel and Bad Decisions

Offline 2.84.253.158:35005 checked 21d 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#15,998top 71%
Last wipe24d 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 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct5 Oct7 Oct9 Oct11 Oct13 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

Reset cycle

When does Blood Steel and Bad Decisions wipe?

To tell the rhythm of Blood Steel and Bad Decisions, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 24 days 1 hours ago.

Tag meanings

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

Tags published by Blood Steel and Bad Decisions, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): The server runs game build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does Blood Steel and Bad Decisions hold among Rust servers?

Ranking for Blood Steel and Bad Decisions: #15,998 on seven-day player hours, top 71% of all ranked servers.

How full does Blood Steel and Bad Decisions get?

Reading for Blood Steel and Bad Decisions: offline at this moment; last seen 21 days 4 hours ago.

Server details

Which location does Blood Steel and Bad Decisions run from?

Reading: location. Blood Steel and Bad Decisions gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 2.84.253.158:35005.

What Rust version is Blood Steel and Bad Decisions on?

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

What is the uptime on Blood Steel and Bad Decisions, and is it online?

Reading: offline. Blood Steel and Bad Decisions last answered 21 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 3 October 2026.

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. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Blood Steel and Bad Decisions?

From seed 67821251, the game generates the procedural map on Blood Steel and Bad Decisions. Its size is 6,000. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How can you get onto Blood Steel and Bad Decisions?

Check: join. Open Rust, press F1, then enter client.connect 2.84.253.158:35005. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players The server holds 100 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build The server runs game build 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.