MapTesting
131.153.158.236:28125 checked 14m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 38% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 11.5 days between real wipes
- on rhythm
- 33% of its recent wipes
- wipe-day peak
- 2 players, last three wipes
- crowd held
- 0% else halves by day 1
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 22 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 11 Oct, 22:56 UTC 1d ago | – | – | running | 0 |
| Sat 10 Oct, 01:02 UTC 3d ago | 3 | – | 1.9 days | 0 |
| Sat 26 Sep, 13:24 UTC 17d ago | 1 | halved by day 1 | 13.5 days | 0 |
| Tue 15 Sep, 00:50 UTC 28d 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.
Similar servers
Quick answers
Player Count
MapTesting ranking: what position does it hold?
Over the last seven days, MapTesting ranks #8,461 in player hours, which is in the top 38% of ranked servers.
Is MapTesting busy?
0 of 90 slots are filled on MapTesting at the moment. Averaged across the last seven days: 0 players, peaking at 3. Over the last 48 hours, the peak hour was 23:00 UTC, averaging 1 players.
Tags and Filters
How should the tags on MapTesting be interpreted?
For MapTesting, the game's server browser reads the following tags: gmvanilla (Game mode): Survival, vanilla style; mp90 (Max players): Slots: 90; ts8 (Group limit): Teams are limited to 8, the default; v2634 (Protocol): Protocol 2634: join only if your game matches this version; cs167398 (Build): Running build 167398; ptrak (Networking): RakNet is the network layer in use; $r? (Region code): Region code not set; ^z (Modded): Plugins or settings alter the game, so it appears under Modded; ^y (Carbon): Carbon provides the plugin framework here; oxidation (Custom tag): A non-standard tag, set by the owner or a plugin. The top of this page also shows its current players, its queue and the time its world was made, all from the tags.
MapTesting in BestRustServers.xyz lists and filters: which ones?
The BestRustServers.xyz lists that include MapTesting are: Best modded Rust servers. These filters on the server list display it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
Server Information
MapTesting Rust version: which one?
The combination is Rust network protocol 2634 and build 167398 on Linux for MapTesting. Steam updates your game automatically, but it needs to match the protocol to join.
How reliable is MapTesting and is it online?
The server is online: MapTesting. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by BestRustServers.xyz on 13 September 2026.
What is the location of MapTesting?
No region is published by MapTesting. BestRustServers.xyz shows the stated location of a server; the actual location of the machine is not looked up. 131.153.158.236:28125 is its address.
Settings & Map
What are the settings and rules for MapTesting?
No gather rate appears in the name of MapTesting. With no stated limit, groups default to 8 players. It runs survival, gather, build, raid: the standard game. Player combat and raiding are enabled. The Modded section of the browser holds it: plugins or settings apply. Carbon plugins are used. VAC protection is on.
Wipe Cycle
When does MapTesting wipe?
With irregular wipe times on MapTesting, no next wipe is predictable. On Thursday 5 November at 19:00 UTC the next force wipe arrives, when all Rust servers wipe. The world in play was made 47 hours.
What happens on wipe day on MapTesting?
An average peak of 2 players was drawn by its recent wipes. 22 hours into the latest wipe, the crowd reached its peak. The crowd held above half the peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half the peak was lost by day 1.
How to Join
What is the process to join MapTesting?
To connect, type client.connect 131.153.158.236:28125 in the F1 console. Launch Rust on this page opens Rust through Steam and joins you.
Server tags
Published as mp90,ptrak,$r?,v2634,gmvanilla,cs167398,ts8,oxidation,^z,^y
Game
gmvanilla- Game mode Survival, vanilla style.
mp90- Max players Slots: 90.
ts8- Group limit Teams are limited to 8, the default.
v2634- Protocol Protocol 2634: join only if your game matches this version.
cs167398- Build Running build 167398.
ptrak- Networking RakNet is the network layer in use.
$r?- Region code Region code not set.
Mods and access
^z- Modded Plugins or settings alter the game, so it appears under Modded.
^y- Carbon Carbon provides the plugin framework here.
Other
oxidation- Custom tag A non-standard tag, set by the owner or a plugin.
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.