Offline 91.1.111.20:28015 checked 2d ago
mapgentest
Connect
srv = rust.server("91.1.111.20:28016")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 28% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 10 Oct, 01:34 UTC18d ago | 1 | NaN | running | 0 |
| 1 | Fri 9 Oct, 01:28 UTC19d ago | 1 | NaN | 1 days | 0 |
| 2 | Sun 27 Sep, 00:27 UTC31d ago | 1 | halved by day 4 | 12 days | 0 |
| 3 | Sat 26 Sep, 16:14 UTC32d ago | 2 | NaN | 0.3 days | 1 |
# 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.
display(srv.map, srv.info())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does mapgentest rank?
Player hours over seven days put mapgentest at #6,220, in the top 28% of the ranked set.
What population does mapgentest carry?
mapgentest returns no live count at this refresh, having last been seen 2 days 19 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server data
What is the Rust version on mapgentest?
The build is Rust network protocol 2634 and build 167303 on Windows, run by mapgentest. Joining needs the same protocol on your game; Steam handles the update.
Is mapgentest up, and what does its uptime show?
mapgentest is offline at this refresh; the last response came 2 days 19 hours ago. Over the last 7 full days the hours up number 49 of 168, 29%. Its earliest recorded date in Rust Data is 15 September 2026.
Which location does mapgentest run from?
For mapgentest, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 91.1.111.20:28015 is its address.
Map and rules
Which settings and rules does mapgentest run?
You will not find a gather rate in the string mapgentest. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. VAC, Valve's anti-cheat, is enabled.
Which map has mapgentest loaded?
The game generates the map on mapgentest: procedural, size 6,000, seed 1337. Size and seed fix the map, so RustMaps can show it, linked from this page. Under map name you will find: Custom Map.
Wipes and dates
When does mapgentest wipe, and on what schedule?
Irregular wipe times on mapgentest leave no next wipe to forecast. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 18 days 16 hours ago.
On mapgentest, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 1 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 4.
Lists and tags
Which lists on Rust Data hold mapgentest, and which filters?
These Rust Data lists include mapgentest: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z; Group limit: 5 or more.
Which meanings do the tags on mapgentest hold?
Read by the game's server browser, the tags mapgentest publishes are: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167303 (Build): Build number: 167303; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to mapgentest?
The manual route: launch Rust, F1, then client.connect 91.1.111.20:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.