A quiet classroom so far: 0 of 30 on average. Plenty of space to grow.
Standingrank on player hours
67/ 100
C+
Working its way up from the back of the class: #7,384 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
53/ 100
D
Moving up: up 488 places this week.
A term to build on.
Strongest in uptime (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
Top 33% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·····
·····W·
·······
·····WW
·······
·W·····
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 3, 17 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by MapTesting. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 131.153.158.236:28125 is the address to use.
Is MapTesting up, and how steady is its uptime?
The server is up: MapTesting is online now. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Which Rust version is MapTesting running?
Rust network protocol 2635 and build 168909 on Linux is what MapTesting runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does MapTesting reset?
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 lands on Thursday 5 November at 19:00 UTC. 7 days 6 hours have passed since this world was made.
What should you expect from wipe day on MapTesting?
The average peak on its recent wipes was 2 players. 17 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Population
Where does MapTesting place in the wider field of Rust servers?
Over the last seven days, MapTesting has #7,384 for player hours, in the top 33% of all ranked servers.
What does the population on MapTesting look like?
Right now, 0 players are on MapTesting, which has 30 slots. It peaked at 3 and averaged 0 players over the last seven days.
Tags
How should you read the tags on MapTesting?
gmvanilla (Game mode): Survival, vanilla style; mp30 (Max players): Its slot count is 30; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon; oxidation (Custom tag): The owner or a plugin created this tag, so it is not standard Rust are the tags MapTesting publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature MapTesting?
These Rust Server Score lists count MapTesting among them: Modded Rust servers, graded. 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.
Map and rules
Which rules does MapTesting enforce, and what are its settings?
Nothing in the name of MapTesting states a gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. You are covered by VAC, Valve's anti-cheat.
Getting in
What is the way to join MapTesting?
To connect, start Rust, press F1, and type client.connect 131.153.158.236:28125. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp30,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,oxidation,^z,^y
Game
gmvanilla
Game modeSurvival, vanilla style.
mp30
Max playersIts slot count is 30.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: Carbon.
Other
oxidation
Custom tagThe owner or a plugin created this tag, so it 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.
A term to build on. Strongest in uptime (A+); population is the one to work on (F).