RUST METRICSFlight deck · live data
Data live Servers11,677 Players48,863 Populated3,243 Fresh wipes 3 h129 Scan5 min
‹ All servers2.87.109.240:35005
Offline Full Queue Fresh wipe Wipe due No query

Blood Steel and Bad Decisions

Offline 2.87.109.240:35005 checked 15d ago

COM 1 · connect

Server instruments

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

Players now

2% 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#11,765top 54%
Last wipe20d 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 11 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
15k10k15k20k11 Oct13 Oct14 Oct16 Oct17 Oct19 Oct

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

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

To tell the rhythm of Blood Steel and Bad Decisions, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 20 days 6 hours ago.

Lists and filters

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167584 (Build): Game build reading: 167584; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from Blood Steel and Bad Decisions. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

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

Ranking for Blood Steel and Bad Decisions: #11,765 on seven-day player hours, top 54% of all ranked servers.

What player count does Blood Steel and Bad Decisions carry?

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

Server

Where does Blood Steel and Bad Decisions sit?

Reading: location. Blood Steel and Bad Decisions gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 2.87.109.240:35005.

What Rust version is Blood Steel and Bad Decisions on?

Rust network protocol 2634 and build 167584 on Linux is the build Blood Steel and Bad Decisions runs. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. Blood Steel and Bad Decisions last answered 15 days ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 11 October 2026.

Rules and settings

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

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

What map is Blood Steel and Bad Decisions on?

Size 6,000 and seed 2146026208: the game generates the procedural map on Blood Steel and Bad Decisions from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

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

Press F1 in Rust and enter client.connect 2.87.109.240: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?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players 100 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167584
Build Game build reading: 167584.
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.