Rust Server TrendsSeismic network · station log
Recording Stations11,683 Players54,666 Active3,397 Wipes · 3 h92 48 h

Station XX-15750 · no signal

Blood Steel and Bad Decisions

Offline 2.84.255.88:35005 checked 16d ago

Connect
Players now
0/ 100
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,750
top 71%
Last wipe
20d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15750 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 100 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 540 on average
517/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
339/ 325
Rustoria.co - EU Main EU · groups of 16+ · weekly · 314 on average
34/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 313 on average
40/ 250
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 273 on average
154/ 200
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 265 on average
78/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Blood Steel and Bad Decisions?

Generated by the game, the map on Blood Steel and Bad Decisions is procedural, size 6,000 with seed 2146026208. You can view it on RustMaps from this page: the same size and seed produce the same map.

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

The name of Blood Steel and Bad Decisions gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, gather, build and raid in the standard game. You can raid and fight other players here. Under Community in the server browser, it runs as a community server. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on Blood Steel and Bad Decisions?

No players are recorded on Blood Steel and Bad Decisions at this moment; it is offline, and the last sighting was 16 days 15 hours ago.

How does Blood Steel and Bad Decisions rank against other Rust servers?

Over the last seven days, Blood Steel and Bad Decisions recorded enough player hours to reach #15,750 worldwide, placing it in the top 71% of all ranked servers.

Server facts

How reliably does Blood Steel and Bad Decisions stay online?

No contact with Blood Steel and Bad Decisions right now, and the last recorded contact was 16 days 15 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 11 October 2026.

Which region does Blood Steel and Bad Decisions run from?

No region is published by Blood Steel and Bad Decisions. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 2.84.255.88:35005 is the address it uses.

Which Rust version is Blood Steel and Bad Decisions running?

On Linux, Blood Steel and Bad Decisions runs Rust network protocol 2634 and build 167398. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

How often does Blood Steel and Bad Decisions wipe, and on which days?

Too few wipes of Blood Steel and Bad Decisions are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 20 days 15 hours is how long the current world has been running.

Tags

What do the server tags on Blood Steel and Bad Decisions mean?

These are the tags Blood Steel and Bad Decisions publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): Slots: 100; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167398 (Build): It runs game build 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Blood Steel and Bad Decisions appear?

You will find Blood Steel and Bad Decisions on the following Rust Server Trends lists: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

What steps get you onto Blood Steel and Bad Decisions?

You can connect by pressing F1 in Rust and typing client.connect 2.84.255.88:35005 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp100
Max players Slots: 100.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167398
Build It runs game build 167398.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.