RUST METRICSFlight deck · live data
Data live Servers11,886 Players104,326 Populated3,964 Fresh wipes 3 h514 Scan5 min
‹ All servers2.84.242.197:35005
Offline Full Queue Fresh wipe Wipe due No query

Blood Steel and Bad Decisions

Offline 2.84.242.197:35005 checked 23d ago

COM 1 · connect

Server instruments

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

Players now

1% 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#14,453top 65%
Last wipe25d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 Oct

Top 65% 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 timing

How often does Blood Steel and Bad Decisions wipe, and when?

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. The world in play was created 25 days 23 hours ago.

Tag meanings

Which tags does Blood Steel and Bad Decisions carry, and what do they mean?

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): 100 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Blood Steel and Bad Decisions appear in Rust Metrics lists and filters?

These Rust Metrics lists carry 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.

Population

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

Player hours over seven days put Blood Steel and Bad Decisions at #14,453, in the top 65% of all ranked servers.

What player count does Blood Steel and Bad Decisions carry?

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

Operator and location

Where does Blood Steel and Bad Decisions sit?

No region comes from Blood Steel and Bad Decisions. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 2.84.242.197: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.

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

Blood Steel and Bad Decisions reports offline. The last reading came 23 days 1 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 6 October 2026.

Rules and settings

What rules does Blood Steel and Bad Decisions enforce, and what are its settings?

Check: gather rate. The name Blood Steel and Bad Decisions does not state one. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is Blood Steel and Bad Decisions on?

Check: map. Procedural, generated by the game, on Blood Steel and Bad Decisions.

How to join

What do you do to join Blood Steel and Bad Decisions?

Check: join. Open Rust, press F1, then enter client.connect 2.84.242.197: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 100 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Game build reading: 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.