Rust Server TrendsSeismic network · station log
Recording Stations11,904 Players102,408 Active3,941 Wipes · 3 h403 48 h

Station XX-15988 · no signal

Bam test

Offline 47.224.222.15:28017 checked 24d ago

Connect
Players now
0/ 8
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,988
top 71%
Last wipe
28d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-15988 · 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 8 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. 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
15k10k15k20k20 Sep24 Sep29 Sep3 Oct8 Oct12 Oct

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

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
5.1 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
50%else halves by day 1

The first 48 hours of its last wipes

Thu 1 OctSun 27 SepSun 20 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 1 Oct, 01:53 UTC28d ago M0.0rising 1 – running 0
Sun 27 Sep, 02:32 UTC32d ago M0.0rising 1 halved by day 1 4 days 0
Sun 20 Sep, 20:22 UTC38d ago M0.0rising 1 held half 6.3 days 0

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 · 514 on average
356/ 400
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 317 on average
450/ 500
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 280 on average
977/ 1000
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 276 on average
53/ 100
Rustoria.co - EU Main EU · groups of 16+ · weekly · 265 on average
985/ 1000
Rustoria.co - US Main NA · groups of 16+ · weekly · 235 on average
32/ 250
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Bam test?

Bam test uses a procedural map, which the game generates.

Which settings and rules apply on Bam test?

No gather rate appears in the name of Bam test. At the game's default, groups can have up to 8 players. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. Anti-cheat is on: VAC, from Valve.

Population

What is the current population on Bam test?

A reading taken now finds Bam test offline; the most recent activity was 24 days 9 hours ago.

How does Bam test rank against other Rust servers?

Over the last seven days, Bam test recorded enough player hours to reach #15,988 worldwide, placing it in the top 71% of all ranked servers.

Server details

How reliably does Bam test stay online?

No contact with Bam test right now, and the last recorded contact was 24 days 9 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does Bam test run from?

No region is published by Bam test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 47.224.222.15:28017.

What build of Rust does Bam test use?

On Linux, Bam test runs Rust network protocol 2633 and build 163794. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on Bam test?

On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 1 hours after the wipe. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 1.

On what timetable does Bam test run its wipes?

There is no next wipe to predict at Bam test, since its wipes fall at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 28 days 14 hours.

Server tags

What do the server tags on Bam test mean?

These are the tags Bam test publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp8 (Max players): 8 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs163794 (Build): Game build: 163794; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. 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 Bam test appear?

The Rust Server Trends lists that take in Bam test are: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

What steps get you onto Bam test?

Enter client.connect 47.224.222.15:28017 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp8,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp8
Max players 8 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs163794
Build Game build: 163794.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been 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.

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.