No signal: too few hourly readings to draw a record yet.
Now
0of 2 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Channel 2 · instrument health
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Channel 3 · rank movement
Rank
daily · 1 is best
RankRank in region
Top 28% of all ranked servers. Ranked on player hours over the last seven days.
Expected events
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 gap
0.4 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
0%else halves by day 4
The first 48 hours of its last wipes
Sat 10 OctFri 9 OctSun 27 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Event catalogue
Wipes
newest first
Wiped
M
Peak
First 48 h
Crowd
Lasted
Players before
Sat 10 Oct, 01:34 UTC18d ago
M0.0▲rising
1
–
running
0
Fri 9 Oct, 01:28 UTC19d ago
M0.0▲rising
1
–
1 days
0
Sun 27 Sep, 00:27 UTC31d ago
M0.0▲rising
1
halved by day 4
12 days
0
Sat 26 Sep, 16:14 UTC32d ago
M0.0▲rising
2
–
0.3 days
1
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Nearby stations
Similar servers
the same kind of game, then region, group limit, rate and wipes
mapgentest runs a procedural map of size 6,000 with seed 1337, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. You will find the map named Custom Map.
Which settings and rules apply on mapgentest?
The name of mapgentest gives no gather rate. The group limit is 8 players, the game's default. survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on mapgentest right now?
No players are recorded on mapgentest at this moment; it is offline, and the last sighting was 2 days 22 hours ago. Across seven days this server recorded an average of 1 players and a peak of 1.
How does mapgentest rank against other Rust servers?
On player hours for the past week, mapgentest sits at #6,265, which puts it inside the top 28% of every ranked server.
Server details
How reliably does mapgentest stay online?
As recorded now, mapgentest is not reachable, the last contact having been 2 days 22 hours ago. 49 of 168 hours in the last 7 full days were up time, 29% of the total. On 15 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is mapgentest hosted?
Nothing about a region comes from mapgentest. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 91.1.111.20:28015.
Which Rust version is mapgentest running?
Rust network protocol 2634 and build 167303 on Windows is what mapgentest runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on mapgentest?
On average, the busiest point of its recent wipes drew 1 players. 1 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. By day 4 it fell below half in the wipes where it didn't hold.
How often does mapgentest wipe, and on which days?
No next wipe can be predicted for mapgentest, 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. It has run its current world for 18 days 19 hours.
Tags
What do the server tags on mapgentest mean?
Tags published by mapgentest and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp2 (Max players): 2 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167303 (Build): It runs game build 167303; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does mapgentest appear?
The Rust Server Trends lists that take in mapgentest are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z; Group limit: 5 or more.
How to join
What steps get you onto mapgentest?
To join, enter client.connect 91.1.111.20:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Instrument codes
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,gmrust,cs167303,ts8,^z
Game
gmrust
Game modeThe game mode is standard Rust survival.
mp2
Max players2 slots are available.
ts8
Group limitTeams max out at 8, the default set by the game.
v2634
ProtocolGame protocol 2634: to join, your game must match this version.
cs167303
BuildIt runs game build 167303.
ptrak
NetworkingRakNet is the standard network layer for the game, and it's used here.
$r?
Region codeA region code has not been set.
Mods and access
^z
ModdedPlugins or settings alter the game, so it's listed under Modded.
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.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.