RUST METRICSFlight deck · live data
Data live Servers11,789 Players78,653 Populated3,571 Fresh wipes 3 h243 Scan5 min
‹ All servers47.224.222.15:28017
Offline Full Queue Fresh wipe Wipe due No query

Bam test

Offline 47.224.222.15:28017 checked 24d 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,988top 71%
Last wipe28d agono schedule published
Next wipe–no rhythm it keeps
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
15k10k15k20k20 Sep24 Sep29 Sep3 Oct8 Oct12 Oct

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

PLAN

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 gap5.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 01:53 UTC28d ago 1 – running 0
Sun 27 Sep, 02:32 UTC32d ago 1 halved by day 1 4 days 0
Sun 20 Sep, 20:22 UTC39d ago 1 held half 6.3 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 timing

What happens on Bam test when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 1 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. It fell below half by day 1 when it didn't.

How often does Bam test wipe, and when?

No next wipe can be predicted for Bam test, which wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 28 days 19 hours ago the current world was made.

Tags

How should you read the tags on Bam test?

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): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none 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 Bam test?

On Rust Metrics, Bam test 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.

Player count

Where does Bam test sit in the rankings?

Ranking for Bam test: #15,988 on seven-day player hours, top 71% of all ranked servers.

What is the population on Bam test?

Reading for Bam test: offline at this moment; last seen 24 days 14 hours ago.

Operator and location

Where does Bam test sit?

Reading: location. Bam test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 47.224.222.15:28017.

What Rust version is Bam test on?

Reading: Bam test, Rust network protocol 2633 and build 163794, Linux. To get in, your game needs the same protocol; Steam applies the update.

Is Bam test up, and how often does it stay up?

Reading: offline. Bam test last answered 24 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

What settings and rules apply on Bam test?

Check: gather rate. The name Bam test does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. 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

What do you do to join Bam test?

To join: start Rust, press F1 and type client.connect 47.224.222.15: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?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp8
Max players Slots: 8.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Build 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.