Online 131.153.158.236:28125 checked 13m ago
MapTesting
Connect
srv = rust.server("131.153.158.236:28178")
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 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 3, 17 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 20 Oct, 22:26 UTC8d ago | 3 | NaN | running | 0 |
| 1 | Sun 11 Oct, 22:56 UTC17d ago | 1 | halved by day 1 | 9 days | 0 |
| 2 | Sat 10 Oct, 01:02 UTC19d ago | 3 | NaN | 1.9 days | 0 |
| 3 | Sat 26 Sep, 13:24 UTC33d ago | 1 | halved by day 1 | 13.5 days | 0 |
| 4 | Tue 15 Sep, 00:50 UTC44d ago | 1 | halved by day 1 | 11.5 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 131.153.158.236:28125
- region
- –
- max players
- 30
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Oct 2026, 22:26 UTC
- hostname
- –
- first seen
- 13 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 · 150 on average | 54/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 98/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 34/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 96/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 334/350 |
Quick answers
From the figures on this page.
Player counts
How does MapTesting compare in the rankings?
Over the last seven days MapTesting sits at #15,268 on player hours, in the top 68% of ranked servers.
What population does MapTesting carry?
Current row: 0 players on MapTesting, against 30 slots. Over the last seven days it averaged 0 players.
About the server
What Rust version does MapTesting run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by MapTesting. Steam updates your game for you, but the protocol must match to join.
How reliable is MapTesting, and is it up?
Online is the state at the latest refresh for MapTesting. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does MapTesting run from?
For MapTesting, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 131.153.158.236:28125 is its address.
Map and rules
What rules and settings are recorded for MapTesting?
The name MapTesting carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. VAC is running: Valve's anti-cheat is on.
Wipes and dates
When does MapTesting wipe, and on what schedule?
No next wipe can be predicted for MapTesting, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 8 days 23 hours ago, and that is the one in play.
What is wipe day on MapTesting like?
The average peak over recent wipes is 2 players. Peak population on the latest wipe came 17 hours in. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 1.
Lists and tags
Where does MapTesting appear among Rust Data lists and filters?
These Rust Data lists include MapTesting: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on MapTesting hold?
Read by the game's server browser, the tags MapTesting publishes are: gmvanilla (Game mode): Survival in vanilla form; mp30 (Max players): The server lists 30 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon; oxidation (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. 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
What is the way to join MapTesting?
In Rust, F1 opens the console: type client.connect 131.153.158.236:28125. Launch Rust on this page does the same by opening the game through Steam and connecting.