RUST METRICSFlight deck · live data
Data live Servers11,694 Players45,403 Populated3,140 Fresh wipes 3 h97 Scan5 min
‹ All servers2.87.111.237:35005
Offline Full Queue Fresh wipe Wipe due No query

Blood Steel and Bad Decisions

Offline 2.87.111.237:35005 checked 9d ago

COM 1 · connect
Launch Rust and join

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,306top 70%
Last wipe11d 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 18 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
15k10k15k20k18 Oct20 Oct21 Oct23 Oct24 Oct26 Oct

Top 70% 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

When does Blood Steel and Bad Decisions wipe?

The rhythm of Blood Steel and Bad Decisions's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 11 days 5 hours ago.

Tags

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

These are the tags Blood Steel and Bad Decisions publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $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. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

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

Player hours over seven days put Blood Steel and Bad Decisions at #15,306, in the top 70% of all ranked servers.

What is the population on Blood Steel and Bad Decisions?

Blood Steel and Bad Decisions is not responding; status offline, last seen 9 days 7 hours ago.

Operator and location

Which location does Blood Steel and Bad Decisions run from?

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. Check: address. It reads 2.87.111.237:35005.

What Rust version is Blood Steel and Bad Decisions on?

Version check: Rust network protocol 2634 and build 167781 on Linux, run by Blood Steel and Bad Decisions. To get in, your game needs the same protocol; Steam applies the update.

Is Blood Steel and Bad Decisions up, and how often does it stay up?

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

Settings and map

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

Reading the name gives no gather rate for Blood Steel and Bad Decisions. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Blood Steel and Bad Decisions?

From seed 2078145132, the game generates the procedural map on Blood Steel and Bad Decisions. Its size is 6,000. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

How do you connect to Blood Steel and Bad Decisions?

To join: start Rust, press F1 and type client.connect 2.87.111.237:35005. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.