Skip to the page
Network live 11,675 servers online 48,284 players aboard 118 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

MapTesting

Online 131.153.158.236:28125 checked 22m ago

moddedcarbon
Tracking number · connect
Wipe progress · wiped 7d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
0/ 30 players now 0% full
07-day averagepeak 3
#7,378ranktop 33%
7d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeak
0123402:0011:0020:0006:0015:0000:00

Hourly average and peak, UTC.

Server performance

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.

10.3 daysusual gapbetween real wipes
50%on rhythmof its recent wipes
2wipe-day peakplayers, last three wipes
0%crowd heldelse 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

every wipe as a delivery, newest first
  1. Tue 20 Oct, 22:26 UTC 23:26 UK · 7d ago
    Wipe delivered
    Peak
    3
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Sun 11 Oct, 22:56 UTC 23:56 UK · 16d ago
    Wipe delivered
    Peak
    1
    Crowd
    halved by day 1
    Lasted
    9 days
    Players before
    0
  3. Sat 10 Oct, 01:02 UTC 02:02 UK · 18d ago
    Wipe delivered
    Peak
    3
    Crowd
    –
    Lasted
    1.9 days
    Players before
    0
  4. Sat 26 Sep, 13:24 UTC 14:24 UK · 31d ago
    Wipe delivered
    Peak
    1
    Crowd
    halved by day 1
    Lasted
    13.5 days
    Players before
    0
  5. Tue 15 Sep, 00:50 UTC 01:50 UK · 43d ago
    Wipe delivered
    Peak
    1
    Crowd
    halved by day 1
    Lasted
    11.5 days
    Players before
    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 parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. ShockRust | Blue | NoLimitno group limit · 162 on average 35 / 500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average 128 / 100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average 50 / 225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 87 on average 39 / 700
  5. RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average 7 / 200
  6. CSL Scenery Budget Testgroups of 8+ · 85 on average 0 / 500
Help desk

Quick answers

From the figures on this page.

Player count

What is the ranking of MapTesting against other Rust servers?

In the top 33% of all ranked servers sits MapTesting, at #7,378 on hours played over seven days.

How many players are on MapTesting right now?

The current count is 0 players on 30 slots for MapTesting. The seven-day figures show an average of 0 players and a peak of 3.

Rules and settings

What settings and rules should you know for MapTesting?

No gather rate appears in the name of MapTesting. The game's default applies: 8 players to a group at most. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players is allowed. Because plugins or settings change the game, it is filed under Modded in the server browser. Plugins come from Carbon. VAC, the anti-cheat from Valve, is active.

About the server

What is the location of MapTesting?

There is no region published for MapTesting. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. 131.153.158.236:28125 is its address.

Is MapTesting up, and how good is its uptime?

MapTesting is up and online at the moment. 100% is the uptime for the last 7 full days, up for 168 of 168 hours. It was first seen by Rust Wipe Tracker on 13 September 2026.

What Rust version is MapTesting using?

On Linux, MapTesting runs Rust network protocol 2635 and build 168909. To join, your game must be on the same protocol; Steam handles that update for you.

Map resets

What happens on MapTesting when wipe day arrives?

At their busiest, its recent wipes drew an average of 2 players. After 17 hours the latest wipe's crowd hit its peak. Half the peak or more was held until the next wipe in 0% of recent wipes. By day 1 it had fallen below half where the crowd did not hold.

On what schedule does MapTesting reset its map?

There is no next wipe to predict for MapTesting: it wipes at irregular times. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. You are playing a world created 7 days 2 hours.

Tags and filters

On Rust Wipe Tracker, which lists and filters is MapTesting part of?

These Rust Wipe Tracker lists take MapTesting: Modded Rust servers. 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.

What is the meaning of the server tags on MapTesting?

gmvanilla (Game mode): Vanilla survival gameplay; mp30 (Max players): The server has 30 slots; ts8 (Group limit): Team limit: 8, the standard default; v2635 (Protocol): Protocol 2635 is required; a different version can't join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): It uses Carbon for plugins; oxidation (Custom tag): The owner or a plugin set this non-standard tag are the tags MapTesting publishes, and the server browser takes them as read. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.

How to join

What is the process to join MapTesting?

Enter client.connect 131.153.158.236:28125 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it 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
Game mode Vanilla survival gameplay.
mp30
Max players The server has 30 slots.
ts8
Group limit Team limit: 8, the standard default.
v2635
Protocol Protocol 2635 is required; a different version can't join.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code No region code is set.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon It uses Carbon for plugins.

Other

oxidation
Custom tag The owner or a plugin set this non-standard tag.

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.