RUST METRICSFlight deck · live data
Data live Servers11,596 Players34,117 Populated2,818 Fresh wipes 3 h69 Scan5 min
‹ All servers2.84.255.88:35005
Offline Full Queue Fresh wipe Wipe due No query

Blood Steel and Bad Decisions

Offline 2.84.255.88:35005 checked 16d 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,750top 71%
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 Oct12 Oct14 Oct15 Oct17 Oct18 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

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

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. 20 days 9 hours ago the current world was made.

Tag meanings

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

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): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): The server runs game build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty 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.

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

On Rust Metrics, Blood Steel and Bad Decisions sits in these lists: 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.

Occupancy

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,750, in the 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 16 days 9 hours ago.

Server details

Which location does Blood Steel and Bad Decisions run from?

No region tag on Blood Steel and Bad Decisions. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 2.84.255.88:35005.

What Rust version is Blood Steel and Bad Decisions on?

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

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

Reading: offline. Blood Steel and Bad Decisions last answered 16 days 9 hours 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.

Settings and map

How is Blood Steel and Bad Decisions configured, and what rules are in force?

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. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is Blood Steel and Bad Decisions on?

Check: map. Procedural, size 6,000, seed 2146026208, generated by the game on Blood Steel and Bad Decisions. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How do you connect to Blood Steel and Bad Decisions?

To join: start Rust, press F1 and type client.connect 2.84.255.88: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,cs167398,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players 100 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build The server runs game build 167398.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.