Rust Data LabData lab · live
Live readings Servers11,842 Players65,813 Populated3,613 Fresh wipes · 3h129 Sampled every 5 min

Element card · group Modded · atomic number 7,176, its rank

MapTesting

Online 131.153.158.236:28125 checked 8m ago

moddedcarbon
Join the experiment
Atomic mass · players now 0/ 30 0% full Room to join
7-day average0peak 3
Rank · atomic number#7,176top 32%
Last wipe6d agono schedule published
Next wipe–no rhythm it keeps
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0123423:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Reaction kinetics

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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Sh ShockRust | Bl… 97
    ShockRust | Blue | NoLimit no group limit · 164 on average 97/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 122
    МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average 122/ 100
  3. 3 Re RETRO RUST #1 … 105
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 112 on average 105/ 225
  4. 4 Ru RustSpain.com … 31
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average 31/ 200
  5. 5 Ru 404 RUST 2Х|ДЛ… 91
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 86 on average 91/ 700
  6. 6 Ru 404 RUST 2Х|ДЛ… 30
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average 30/ 1,000

Quick answers

from the figures on this page

Settings and map

What rules has MapTesting set, and what settings are in force?

The name of MapTesting carries no gather rate. Eight players per group is the limit, the game's default. Play runs as survival, raiding, building and gathering: the standard game. Fighting and raiding between players are allowed. In the server browser it sits under Modded: the game is changed by plugins or settings. Plugins in use: Carbon. The VAC anti-cheat from Valve is enabled.

About the server

What region hosts MapTesting?

Nothing about a region is published by MapTesting. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. Connect at 131.153.158.236:28125.

Which Rust version is MapTesting on?

On Linux, MapTesting is running Rust network protocol 2635 and build 168909. Your game needs to match the protocol to join, and Steam updates it automatically.

Does MapTesting stay up, and how reliable is its uptime?

MapTesting is live as of now. For the last 7 full days, 168 of 168 hours were online, giving 100% uptime. On 13 September 2026, Rust Data Lab saw it for the first time.

Wipes and resets

What is the wiping pattern on MapTesting?

With no fixed rhythm, MapTesting wipes at irregular times, so the next wipe cannot be predicted. The next monthly force wipe, which wipes all Rust servers, is scheduled for Thursday 5 November at 19:00 UTC. 6 days 23 hours ago the current world was made.

How does MapTesting look on the day of a wipe?

Averaged across its recent wipes, the busiest point drew 2 players. The latest wipe's peak fell 17 hours after it began. Half that peak was held until the next wipe in 0% of recent wipes. Where it did not hold, the crowd dropped below half by day 1.

Lists and tags

Which meanings sit behind the tags on MapTesting?

These are the tags MapTesting makes public for the server browser to read: gmvanilla (Game mode): This is vanilla survival; mp30 (Max players): Player slots: 30; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): The region field is left blank; ^z (Modded): Because plugins or settings change the game, it is filed under Modded; ^y (Carbon): The plugin framework here is Carbon; oxidation (Custom tag): Not a standard Rust tag, so either a plugin or the owner applied it. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Which Rust Data Lab filters and lists does MapTesting appear in?

The Rust Data Lab lists that include MapTesting are: Modded Rust servers, measured. Applying these filters on the server list returns it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.

Population

What position does MapTesting hold among Rust servers?

Player hours over the last week put MapTesting at #7,176, inside the top 32% of ranked servers.

How many players does MapTesting have at the moment?

MapTesting currently shows 0 players across 30 slots. A seven-day sample gives 0 players on average and 3 at the top.

How to join

What steps get you onto MapTesting?

You can connect by pressing F1 in Rust and entering client.connect 131.153.158.236:28125, or by pressing Launch Rust here, which starts the game through Steam and joins for you.

Server tags

what each one means

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

Game

gmvanilla
Game mode This is vanilla survival.
mp30
Max players Player slots: 30.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code The region field is left blank.

Mods and access

^z
Modded Because plugins or settings change the game, it is filed under Modded.
^y
Carbon The plugin framework here is Carbon.

Other

oxidation
Custom tag Not a standard Rust tag, so either a plugin or the owner applied it.

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.