Offline 91.1.96.152:28015 checked 3h ago
mapgentest
Connect
srv = rust.server("91.1.96.152: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 26 Oct. 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 38% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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 · 158 on average | 54/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 41/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 30/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 13/1000 |
Quick answers
From the figures on this page.
Player counts
What position does mapgentest take in the server rankings?
Over the last seven days mapgentest sits at #8,473 on player hours, in the top 38% of ranked servers.
How full does mapgentest run?
The current row shows mapgentest offline; the last response was 3 hours ago. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 16:00 UTC, averaging 1 players.
Server facts
What does performance look like on mapgentest?
Server fps over the last 48 hours averages 237; the floor is 184. The entity count peaked at 25, covering buildings, deployables and the rest of the world. A high of 1,930 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
What Rust version does mapgentest run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by mapgentest. The protocol has to match before you can join, and Steam does the updating.
How reliable is mapgentest, and is it online now?
The latest sample has mapgentest offline, with a last sighting 3 hours ago. Count back 4 minutes from its reported uptime to get the last restart. Uptime of 60% across the last 2 full days: 29 hours of 48. The first row Rust Data holds for it is dated 25 October 2026.
Where does mapgentest sit?
There is no region published for mapgentest. Rust Data does not look up where the machine stands; it shows where a server says it is. 91.1.96.152:28015 is its address.
Map and rules
What rules and settings are recorded for mapgentest?
The name mapgentest carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. VAC is running: Valve's anti-cheat is on.
Which map has mapgentest selected?
Size 6,000, seed 1337: the procedural map on mapgentest, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Recorded under map name: Custom Map.
Wipe data
On what schedule does mapgentest wipe?
Too few wipes are on record for mapgentest to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 18 days 2 hours ago, and that is the one in play.
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): Survival play, standard Rust; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to mapgentest?
In Rust, F1 opens the console: type client.connect 91.1.96.152:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.