RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h50 Scan5 min
‹ All servers2.84.253.127:35005
Offline Full Queue Fresh wipe Wipe due No query

Blood Steel and Bad Decisions

Offline 2.84.253.127:35005 checked 10d 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,272top 70%
Last wipe10d agono schedule published
Next wipe–too few wipes 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 13 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
15k10k15k20k13 Oct15 Oct18 Oct20 Oct23 Oct25 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 19:45 UTC10d ago 2 – running 2

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

What happens on Blood Steel and Bad Decisions when wipe day comes?

The busiest point of its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 0 hours in.

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. 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 10 days 23 hours ago.

Lists and filters

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): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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; Last wipe: In the last 2 weeks.

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 #15,272, in the top 70% of all ranked servers.

What is the population on Blood Steel and Bad Decisions?

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

Operator and location

What location is Blood Steel and Bad Decisions hosted in?

Reading: location. Blood Steel and Bad Decisions gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 2.84.253.127:35005.

What Rust version is Blood Steel and Bad Decisions on?

Reading: Blood Steel and Bad Decisions, Rust network protocol 2634 and build 167781, Linux. 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?

Check: connection. Blood Steel and Bad Decisions is offline at this moment. Last contact was 10 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 October 2026.

Map and rules

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

Check: gather rate. The name Blood Steel and Bad Decisions does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is Blood Steel and Bad Decisions on?

From seed 2078145132, the game generates the procedural map on Blood Steel and Bad Decisions. Its size is 6,000. Check: map view. Size and seed match, so the map is the same; view 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.84.253.127: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 The game mode is plain Rust survival.
mp100
Max players The server holds 100 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.