MapTesting
Online 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 32% 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
- 10.3 daysbetween real wipes
- on rhythm
- 50%of its recent wipes
- wipe-day peak
- 2players, 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, 17 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
20 OCT 2026Tue 20 Oct, 22:26 UTC6d ago |
3 | – | running | 0 |
11 OCT 2026Sun 11 Oct, 22:56 UTC15d ago |
1 | halved by day 1 | 9 days | 0 |
10 OCT 2026Sat 10 Oct, 01:02 UTC17d ago |
3 | – | 1.9 days | 0 |
26 SEP 2026Sat 26 Sep, 13:24 UTC31d ago |
1 | halved by day 1 | 13.5 days | 0 |
15 SEP 2026Tue 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Rules and settings
On MapTesting, which rules and settings apply?
You will find no gather rate in the name of MapTesting. The group limit is 8 players, the game's default. Filed under survival, gather, build and raid: the standard game. Fighting and raiding other players is permitted. The server browser lists it under Modded; plugins or settings alter the game. Filed under plugins: Carbon. VAC is on: Valve's anti-cheat is enabled.
Tags
On Rust Server Index, which lists and filters carry MapTesting?
Filed under these Rust Server Index lists is MapTesting: Modded Rust servers, filed by play style. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Which tags are attached to MapTesting, and what do they stand for?
Filed under these tags, as published by MapTesting and read by the game's server browser: gmvanilla (Game mode): Survival in vanilla form; mp30 (Max players): The queue ceiling sits at 30; ts8 (Group limit): The team limit is 8, as in the standard game; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): The game build here is 168909; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): A region code is absent; ^z (Modded): Modded: the game is changed by plugins or settings; ^y (Carbon): The Carbon plugin framework runs here; oxidation (Custom tag): This one is not a standard Rust tag; an owner or plugin put it there. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe schedule
What should you expect on MapTesting when wipe day comes?
The average peak across its recent wipes is 2 players. The latest wipe peaked 17 hours in. Half that peak was held until the next wipe in 0% of its recent wipes. In the other cases, numbers dropped below half by day 1.
When does MapTesting wipe?
No next wipe can be predicted for MapTesting: its wipes fall at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 6 days 23 hours.
Player counts
Where does MapTesting sit in the rankings?
Filed under rankings: #7,176 for MapTesting on seven-day player hours, top 32% overall.
Is MapTesting quiet or crowded?
Filed under live counts: MapTesting, 0 players on 30 slots at present. Filed under seven-day figures: an average of 0 players and a peak of 3.
Operator and status
What Rust version is MapTesting on?
Rust network protocol 2635 and build 168909, on Linux, is what MapTesting runs. The protocol must match before you can join, and Steam takes care of updating it.
What is the uptime and current status of MapTesting?
You will find MapTesting online as of now. Of the last 7 full days, 168 of 168 hours were up, 100% of the time. It was first recorded by Rust Server Index on 13 September 2026.
Where in the world is MapTesting hosted?
MapTesting gives no region at all. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. You will reach it at 131.153.158.236:28125.
How to join
How can you connect to MapTesting?
Two ways in. Type client.connect 131.153.158.236:28125 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp30,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,oxidation,^z,^y
Game
gmvanilla
mp30
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^z
^y
Other
oxidation
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.