Rust PopulationField survey · Rust servers
Observing 89,289 players 11,829 servers 4,008 with someone on 90 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 8,005habitat unknownfirst seen 13 Sep 2026

MapTesting

Online 131.153.158.236:28125 checked 1h ago

moddedcarbon

Measurements

Players now
0/ 30
0% full
7-day average
0
peak 2
Rank
#8,005
top 36%
Last wipe
7d ago
no schedule published
Next wipe
–
no rhythm it keeps
Obs. 1 · sightings

Players

AveragePeak
0123419:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Obs. 2 · condition

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.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Obs. 4 · the wipe cycle

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 days
usual gap
between real wipes
50%
on rhythm
of its recent wipes
2
wipe-day peak
players, last three wipes
0%
crowd held
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.

Log · wipes seen

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 UTC32d 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.

Field questions

Quick answers

from the figures on this page

Population

How does MapTesting rank against other Rust servers?

By player hours over the last seven days, MapTesting places at #8,005, within the top 36% of ranked servers.

How busy is MapTesting?

MapTesting holds 0 players at the moment, out of 30 slots. Averaged over seven days, it drew 0 players and reached a peak of 2.

Lists and tags

What do the server tags on MapTesting mean?

These are the tags MapTesting publishes, as read by the game's server browser: gmvanilla (Game mode): Survival in vanilla form; mp30 (Max players): You can join up to 30 slots; ts8 (Group limit): 8 per team is the default limit; v2635 (Protocol): The protocol is 2635; a different version will not connect; 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; ^z (Modded): Plugins or settings change the game; it is listed under Modded; ^y (Carbon): A plugin framework, Carbon, is in use; oxidation (Custom tag): The owner or a plugin applied this tag, which is not standard Rust. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.

Which Rust Population lists and filters include MapTesting?

On Rust Population, MapTesting is filed under these lists: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Wipe notes

What does wipe day look like on MapTesting?

The busiest point of its recent wipes averaged 2 players. The crowd on the latest wipe peaked 17 hours in. In 0% of recent wipes, half the peak was held until the next wipe. In those that did not hold, the fall below half came by day 1.

What is the wipe schedule on MapTesting?

Irregular times are when MapTesting wipes, which leaves no next wipe to predict. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The world it runs now dates from 7 days 20 hours ago.

Settings

What are the rules and settings on MapTesting?

Nothing in MapTesting's name says how gather works. No limit is set beyond the standard 8 players per group. survival is what it runs, the usual game, where you gather, build and raid. Combat between players, raids included, is permitted. You find it under Modded, since plugins or settings change how it plays. You will find Carbon running as plugins. You play with Valve's anti-cheat on: VAC.

Server details

Which version of Rust does MapTesting run?

The setup is Rust network protocol 2635 and build 168909 on Linux for MapTesting. Steam updates your game automatically, but you need the same protocol to join.

Is MapTesting online, and how reliable is it?

You will find MapTesting online now. Over the last 7 full days, 168 of 168 hours were online, or 100%. The first sighting by Rust Population was on 13 September 2026.

Where is MapTesting located?

Nothing published by MapTesting states a region. The location a server claims is what Rust Population shows, not the place where the machine stands. 131.153.158.236:28125 is where it lives.

How to join

How do I join MapTesting?

Open the console with F1 in Rust and enter client.connect 131.153.158.236:28125. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.

Key to its markings

Server tags

what each one means

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

Game

gmvanilla
Game mode Survival in vanilla form.
mp30
Max players You can join up to 30 slots.
ts8
Group limit 8 per team is the default limit.
v2635
Protocol The protocol is 2635; a different version will not connect.
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.

Mods and access

^z
Modded Plugins or settings change the game; it is listed under Modded.
^y
Carbon A plugin framework, Carbon, is in use.

Other

oxidation
Custom tag The owner or a plugin applied this tag, which is not standard Rust.

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.