Offline 156.146.18.184:28017 checked 4d ago
Bam test
Connect
srv = rust.server("156.146.18.184:28018")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 24 Oct, 18:32 UTC4d ago | 0 | NaN | running | 0 |
| 1 | Sun 11 Oct, 22:23 UTC17d 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 156.146.18.184:28017
- region
- –
- max players
- 8
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Oct 2026, 18:32 UTC
- hostname
- –
- first seen
- 10 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 514 on average | 373/425 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 317 on average | 442/500 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 280 on average | 981/1000 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 276 on average | 58/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 265 on average | 986/1000 |
| 5 | Rustoria.co - US Main | NA · groups of 16+ · weekly · 235 on average | 31/250 |
Quick answers
From the figures on this page.
Population
What position does Bam test take in the server rankings?
Player hours over seven days put Bam test at #15,327, in the top 69% of the ranked set.
What population does Bam test carry?
The current row shows Bam test offline; the last response was 4 days 17 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is Bam test on?
The build is Rust network protocol 2634 and build 167398 on Linux, run by Bam test. Joining needs the same protocol on your game; Steam handles the update.
Is Bam test up, and what does its uptime show?
The latest sample has Bam test offline, with a last sighting 4 days 17 hours ago. Uptime of 22% across the last 7 full days: 37 hours of 168. Its earliest recorded date in Rust Data is 10 October 2026.
Where does Bam test sit?
There is no region published for Bam test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 156.146.18.184:28017.
Settings and map
What rules and settings are recorded for Bam test?
You will not find a gather rate in the string Bam test. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat status: VAC on.
What is the map on Bam test?
A procedural map runs on Bam test, generated by the game.
Wipe data
On what schedule does Bam test wipe?
The record for Bam test holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 4 days 22 hours ago, and that is the one in play.
On Bam test, what happens on wipe day?
Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 3.
Lists and tags
Which lists on Rust Data hold Bam test, and which filters?
On Rust Data, Bam test appears in these lists: Rust community servers, unfiltered. It appears under these filters 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.
How should you read the server tags on Bam test?
Read by the game's server browser, the tags Bam test publishes are: gmrust (Game mode): Survival play, standard Rust; mp8 (Max players): Slot count: 8; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Build number: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to Bam test?
The manual route: launch Rust, F1, then client.connect 156.146.18.184:28017. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.