Rust Server Analytics 72,806 players11,737 servers
All servers
Drill-through Server detail

MapTesting

Online 131.153.158.236:28125 checked 9m ago

Drill-through
FilterServeris MapTesting
Attributes
moddedcarbon
Last refreshed
Players now 0/ 30
7-day average 0 peak 3
Rank #7,375 top 33%
Last wipe 7d ago no schedule published
Next wipe – no rhythm it keeps
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
0123414:0023:0008:0017:0002:0011:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
This server has not answered a direct query in the last 48 hours.

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 best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 33% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

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.

usual gap10.3 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Tue 20 OctSun 11 OctSat 10 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 17 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 20 Oct, 22:26 UTC7d ago 3 – running 0
Sun 11 Oct, 22:56 UTC16d ago 1 halved by day 1 9 days 0
Sat 10 Oct, 01:02 UTC18d 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 UTC43d 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
ServerProfilePlayers now
ShockRust | Blue | NoLimit no group limit · 156 on average 186 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average 129 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 116 on average 175 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 88 on average 138 / 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average 14 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 51 / 1000

Quick answers

from the figures on this page

Wipe cycle

The wipe schedule for MapTesting: what is it?

No next wipe can be predicted for MapTesting, which wipes 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 current world dates from 7 days 14 hours.

Wipe day on MapTesting: what should you expect?

Recent wipes averaged a busiest count of 2 players. Peak population for the latest wipe came 17 hours after it began. Recent wipes held the crowd above half that peak until the next wipe in 0% of cases. In the other cases the crowd dropped below half by day 1.

Server details

In which region does MapTesting sit?

A region is not published by MapTesting. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 131.153.158.236:28125 is its address.

Which Rust version is MapTesting on?

The platform is Linux, with Rust network protocol 2635 and build 168909 running on MapTesting. Your game must match the protocol to join, and Steam applies that update.

Is MapTesting up, and how steady is its uptime?

The current status of MapTesting is online. Of 168 hours in the last 7 full days, 168 were up: 100%. The first sighting of it by Rust Server Analytics was on 13 September 2026.

Lists and tags

How should the tags on MapTesting be read?

Tags from MapTesting, as read by the game's server browser, are: gmvanilla (Game mode): The vanilla survival format; mp30 (Max players): 30 slots in total; ts8 (Group limit): Default team size of 8; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): The region code is blank; ^z (Modded): Plugins or settings change the game, so it sits under Modded; ^y (Carbon): The Carbon plugin framework is installed; oxidation (Custom tag): A custom tag, set by the owner or a plugin, outside the standard set. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On Rust Server Analytics, which lists and filters feature MapTesting?

The following Rust Server Analytics lists count MapTesting among their servers: Modded Rust servers: live data. These filters bring it up 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.

Population

What position does MapTesting hold in the server rankings?

Player hours for the last seven days place MapTesting at #7,375, in the top 33% of the ranked field.

At what level does MapTesting run its population?

Of 30 slots, 0 are filled on MapTesting at this refresh. Seven-day figures: an average of 0 players and a peak of 3.

Map and rules

How is MapTesting configured, and what rules apply?

No gather rate is given in the name of MapTesting. The default group cap of 8 players applies. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. The Modded category lists it; plugins or settings change the game. Carbon plugins are run. The server runs with VAC, Valve's anti-cheat, enabled.

Connection

What is the way onto MapTesting?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 131.153.158.236:28125.

Server tags

what each one means

Published as mp30,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,oxidation,^z,^y

Game

gmvanilla
Game mode The vanilla survival format.
mp30
Max players 30 slots in total.
ts8
Group limit Default team size of 8.
v2635
Protocol To join, your game version must match protocol 2635.
cs168909
Build Game build: 168909.
ptrak
Networking RakNet is the network layer, the game's standard one.
$r?
Region code The region code is blank.

Mods and access

^z
Modded Plugins or settings change the game, so it sits under Modded.
^y
Carbon The Carbon plugin framework is installed.

Other

oxidation
Custom tag A custom tag, set by the owner or a plugin, outside the standard set.

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.