Offline 46.158.42.149:28015 checked 27d ago
TEST_MAP_CFG
Connect
srv = rust.server("46.158.42.149:28017")
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 70% 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 | Wed 30 Sep, 14:47 UTC27d ago | 0 | NaN | running | 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
- 46.158.42.149:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 30 Sep 2026, 14:47 UTC
- hostname
- –
- first seen
- 30 Sep 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 | ShockRust | Blue | NoLimit | no group limit · 160 on average | 43/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 46/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 19/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 7/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 6/1000 |
Quick answers
From the figures on this page.
Player counts
How does TEST_MAP_CFG compare in the rankings?
Player hours over seven days put TEST_MAP_CFG at #16,787, in the top 70% of the ranked set.
How many players does TEST_MAP_CFG hold at once?
TEST_MAP_CFG returns no live count at this refresh, having last been seen 27 days 12 hours ago.
About the server
Which Rust version is TEST_MAP_CFG on?
The build is Rust network protocol 2633 and build 165217 on Windows, run by TEST_MAP_CFG. The protocol has to match before you can join, and Steam does the updating.
How reliable is TEST_MAP_CFG, and is it up?
The latest sample has TEST_MAP_CFG offline, with a last sighting 27 days 12 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 30 September 2026.
In which location is TEST_MAP_CFG hosted?
For TEST_MAP_CFG, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 46.158.42.149:28015.
Settings and map
Which rules apply on TEST_MAP_CFG, and what settings?
No gather rate appears in the name: TEST_MAP_CFG. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has TEST_MAP_CFG selected?
A procedural map runs on TEST_MAP_CFG, generated by the game.
Wipes and dates
On what schedule does TEST_MAP_CFG wipe?
Too few wipes are on record for TEST_MAP_CFG to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 27 days 12 hours ago.
What is wipe day on TEST_MAP_CFG like?
The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does TEST_MAP_CFG appear among Rust Data lists and filters?
On Rust Data, TEST_MAP_CFG appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on TEST_MAP_CFG?
The game's server browser reads these tags from TEST_MAP_CFG: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): 2 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): The server runs build 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way to join TEST_MAP_CFG?
Enter client.connect 46.158.42.149:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.