RUST METRICSFlight deck · live data
Data live Servers11,757 Players71,129 Populated3,435 Fresh wipes 3 h212 Scan5 min
‹ All servers156.146.18.184:28017
Offline Full Queue Fresh wipe Wipe due No query

Bam test

Offline 156.146.18.184:28017 checked 4d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 4 6 8 PAX 0 /8

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,290top 69%
Last wipe5d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k10 Oct14 Oct18 Oct21 Oct25 Oct29 Oct

Top 69% 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.

usual gap12.8 daysbetween real wipes
wipe-day peak0players, last three wipes
crowd held0%else halves by day 3

The first 48 hours of its last wipes

Sat 24 OctSun 11 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 24 Oct, 18:32 UTC5d ago 0 – running 0
Sun 11 Oct, 22:23 UTC18d ago 1 halved by day 3 12.8 days 0

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

What should you expect from wipe day on Bam test?

The busiest point of its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 3 it fell below half when it didn't.

What wipe timing does Bam test follow?

To tell the rhythm of Bam test, 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 5 days 4 hours ago.

Tag meanings

Which tags does Bam test carry, and what do they mean?

These are the tags Bam test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp8 (Max players): Slots: 8; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. 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 Bam test?

These Rust Metrics lists carry Bam test: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Population

Where does Bam test sit in the rankings?

Player hours over seven days put Bam test at #15,290, in the top 69% of all ranked servers.

What player count does Bam test carry?

Bam test is not responding; status offline, last seen 4 days 22 hours ago. Check: player average. 0 over the last seven days.

Server

Where does Bam test sit?

No region tag on Bam test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 156.146.18.184:28017.

What Rust version is Bam test on?

Version check: Rust network protocol 2634 and build 167398 on Linux, run by Bam test. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Bam test, and is it online?

Bam test reports offline. The last reading came 4 days 22 hours ago. Reading: 22% uptime over the last 7 full days. It was up 37 of 168 hours. Reading: first seen 10 October 2026, recorded by Rust Metrics.

Map and rules

What rules does Bam test enforce, and what are its settings?

Reading the name gives no gather rate for Bam test. The group cap is 8 players, which is the default in the game. 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. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Bam test?

Check: map. Procedural, generated by the game, on Bam test.

Connection

How can you get onto Bam test?

To join: start Rust, press F1 and type client.connect 156.146.18.184:28017. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp8
Max players Slots: 8.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build 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.