MapTesting
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 11m ago · 131.153.158.236:28125
Abstract
We describe the public Rust server MapTesting, reached at 131.153.158.236:28125. At the last check it held 0 of 30 places, against a seven-day mean of 0 and a peak of 31. It ranks #7,176 of all servers, the top 32%. It last wiped 6d ago.
Keywordsmodded carbon
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 32% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
| Measure | Value | Note |
|---|---|---|
| Usual gap | 10.3 days | between real wipes |
| On rhythm | 50% | of its recent wipes |
| Wipe-day peak | 2 | players, last three wipes |
| Crowd held | 0% | else halves by day 1 |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Tue 20 Oct, 22:266d ago | 3 | – | running | 0 |
| Sun 11 Oct, 22:5615d ago | 1 | halved by day 1 | 9 d | 0 |
| Sat 10 Oct, 01:0217d ago | 3 | – | 1.9 d | 0 |
| Sat 26 Sep, 13:2431d ago | 1 | halved by day 1 | 13.5 d | 0 |
| Tue 15 Sep, 00:5042d ago | 1 | halved by day 1 | 11.5 d | 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| 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 |
| Map | Custom Map |
| Size | – |
| Seed | – |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded server list with rates [2] and servers wiping soon [3].
| Server | Players |
|---|---|
| ShockRust | Blue | NoLimitno group limit · 164 on average | 99/500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average | 133/100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 112 on average | 105/225 |
| RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average | 30/200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 86 on average | 91/700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average | 29/1000 |
Appendix AQuick answers
From the figures on this page.
About the server
A.1In which location is MapTesting based?
There is no region published for MapTesting. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 131.153.158.236:28125 is its address.
A.2What is the online status and reliability of MapTesting?
MapTesting is online at this time. Of the 168 hours in the last 7 full days, 168 were served, an availability of 100%. The first record of it by Rust Statistics dates to 13 September 2026.
A.3What version of Rust is run on MapTesting?
MapTesting is running Rust network protocol 2635 and build 168909 on the Linux operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.
Wipe timing
A.4What schedule does MapTesting follow for wipes?
With irregular wipe times, MapTesting offers no next wipe to predict. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 6 days 23 hours have passed since the current world was generated.
A.5What happens on MapTesting when wipe day arrives?
The average busiest point of recent wipes was 2 players. The peak on the latest wipe came 17 hours after it began. For 0% of recent wipes, the population did not fall below half the peak before the next wipe. In the other cases, the population fell below half by day 1.
Population
A.6How does MapTesting compare with other Rust servers in the rankings?
The seven-day player-hours ranking puts MapTesting at #7,176, within the top 32% of ranked servers.
A.7At what level does MapTesting operate in terms of players?
The current population of MapTesting is 0, drawn from 30 slots. The peak over seven days is 3, against an average of 0.
Tags and filters
A.8How should the tags on MapTesting be interpreted?
Tags from MapTesting, read by the game's server browser, are gmvanilla (Game mode): This is survival in its vanilla form; mp30 (Max players): It offers 30 slots; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): A region code has not been set; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded; ^y (Carbon): Plugins run through Carbon; oxidation (Custom tag): A non-standard tag, applied by the owner or a plugin. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.
A.9Where can MapTesting be found among the Rust Statistics lists and filters?
Modded Rust servers are the Rust Statistics lists that MapTesting fits. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Rules, settings, map
A.10Under what rules and settings does MapTesting operate?
The name of MapTesting states no gather rate. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gathering, building and raiding, as the game is usually played. Players may raid and fight one another. The server browser lists it as Modded, where plugins or settings alter the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
How to join
A.11How do you connect to MapTesting?
Press F1 inside Rust to open the console and enter client.connect 131.153.158.236:28125. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.
Appendix BServer tags
What each of the server's tags means. Published as mp30,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,oxidation,^z,^y.
| Tag | Meaning |
|---|---|
| Game | |
gmvanilla | Game mode. This is survival in its vanilla form. |
mp30 | Max players. It offers 30 slots. |
ts8 | Group limit. Teams are limited to 8, as the game defaults. |
v2635 | Protocol. The game protocol is 2635; your client must match it to join. |
cs168909 | Build. Build 168909 is the one running. |
ptrak | Networking. RakNet is the network layer here, as it is by default in the game. |
$r? | Region code. A region code has not been set. |
| Mods and access | |
^z | Modded. The game is altered by plugins or settings, so it is listed as Modded. |
^y | Carbon. Plugins run through Carbon. |
| Other | |
oxidation | Custom tag. A non-standard tag, applied 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.
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.