MapTesting
Online 131.153.158.236:28125 checked 11m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 32% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
no rhythm it keepsIts 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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 20 Oct, 22:26 UTC6d ago | 3° | – | running | 0 |
| Sun 11 Oct, 22:56 UTC15d ago | 1° | halved by day 1 | 9 days | 0 |
| Sat 10 Oct, 01:02 UTC17d ago | 3° | – | 1.9 days | 0 |
| Sat 26 Sep, 13:24 UTC31d ago | 1° | halved by day 1 | 13.5 days | 0 |
| Tue 15 Sep, 00:50 UTC42d 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on MapTesting?
At their busiest, its recent wipes averaged 2 players. The crowd on the latest wipe reached its peak 17 hours in. Half the peak was held until the next wipe in 0% of its recent wipes. In the wipes that did not hold, numbers dropped below half by day 1.
What is the wipe schedule on MapTesting?
No next wipe can be predicted: MapTesting wipes when it chooses, at irregular times. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 6 days 23 hours ago.
Population
How busy is MapTesting?
The current population of MapTesting is 0, against 30 slots. The average across the last seven days is 0 players; the peak reached 3.
How does MapTesting rank against other Rust servers?
Player hours over seven days put MapTesting at #7,176, in the top 32% of ranked servers.
Map and rules
What are the rules and settings on MapTesting?
The name MapTesting does not specify a gather rate. Groups can contain up to 8 players, the default in the game. survival is the game mode, gather, build and raid in the standard game. You can fight other players and raid their bases. Plugins or settings change the game, and it is listed under Modded in the server browser. Carbon plugins are in use. The server has VAC, Valve's anti-cheat, turned on.
Server details
Which version of Rust does MapTesting run?
Rust network protocol 2635 and build 168909 on Linux is what MapTesting runs. Your game must run the same protocol to join, and Steam takes care of updating it.
Is MapTesting online, and how reliable is it?
Right now MapTesting shows as online. It was up 168 of 168 hours across the last 7 full days, or 100% of the time. It first appears in Rust Heatmap records on 13 September 2026.
Where is MapTesting located?
Nothing about a region comes from MapTesting. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. To connect, use 131.153.158.236:28125.
Tags
Which Rust Heatmap lists and filters include MapTesting?
These Rust Heatmap lists include MapTesting: Modded Rust servers, by live population. Filtering the list by Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week brings it up.
What do the server tags on MapTesting mean?
The game's server browser reads the tags MapTesting publishes: gmvanilla (Game mode): Survival in vanilla form; mp30 (Max players): Slot count: 30; ts8 (Group limit): At most 8 per team: the default the game ships with; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): Build 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): No region code is set; ^z (Modded): Settings or plugins alter the game, which puts it under Modded; ^y (Carbon): The plugin framework in use is Carbon; oxidation (Custom tag): The owner or a plugin set this, which is not a standard Rust tag. The top of this page also shows the tags for players now, the queue and when the world was made.
How to join
How do I join MapTesting?
To join by console, open it with F1 in Rust and enter client.connect 131.153.158.236:28125. Or press Launch Rust on this page, which connects you through Steam.