Station XX-7380 · recording
MapTesting
Online 131.153.158.236:28125 checked 8m ago
- Players now
- 0/ 30
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 3
- Rank
- #7,380
- top 33%
- Last wipe
- 7d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 30 slots
- Motion · 24 h
- M0.0■steady+0 players
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
daily · 1 is bestTop 33% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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.
- 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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 20 Oct, 22:26 UTC7d ago | M0.5▲rising | 3 | – | running | 0 | |
| Sun 11 Oct, 22:56 UTC16d ago | M0.0▲rising | 1 | halved by day 1 | 9 days | 0 | |
| Sat 10 Oct, 01:02 UTC18d ago | M0.5▲rising | 3 | – | 1.9 days | 0 | |
| Sat 26 Sep, 13:24 UTC31d ago | M0.0▲rising | 1 | halved by day 1 | 13.5 days | 0 | |
| Tue 15 Sep, 00:50 UTC43d ago | M0.0▲rising | 1 | halved by day 1 | 11.5 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which settings and rules apply on MapTesting?
The name of MapTesting gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, gather, build and raid in the standard game. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Carbon is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on MapTesting?
A reading taken now shows 0 players on MapTesting, which has 30 slots. The seven-day average is 0 players, with a peak of 3.
How does MapTesting rank against other Rust servers?
The last seven days of player hours place MapTesting at #7,380, in the top 33% of all ranked servers.
Server facts
How reliably does MapTesting stay online?
As recorded now, MapTesting is running. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. 13 September 2026 is when Rust Server Trends first recorded it.
Which region does MapTesting run from?
No region is published by MapTesting. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 131.153.158.236:28125.
What build of Rust does MapTesting use?
MapTesting is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on MapTesting?
2 players, on average, was the busiest crowd at its recent wipes. 17 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 0% of its recent wipes. By day 1 it fell below half in the wipes where it didn't hold.
How often does MapTesting wipe, and on which days?
There is no next wipe to predict at MapTesting, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 7 days 3 hours.
Server tags
What do the server tags on MapTesting mean?
The game's server browser reads the tags MapTesting publishes: gmvanilla (Game mode): Survival in vanilla mode; mp30 (Max players): 30 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here; oxidation (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does MapTesting appear?
These Rust Server Trends lists include MapTesting: Modded Rust servers, tracked live. You will find it 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.
Connecting
What steps get you onto MapTesting?
You can connect by pressing F1 in Rust and typing client.connect 131.153.158.236:28125 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.