Online 202.36.95.80:21708 checked 12m ago
M1M1KA
Connect
srv = rust.server("202.36.95.80:21709")
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 bestTop 38% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. 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, 23 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 21:23 UTC26d ago | 1 | NaN | running | 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.
display(srv.map, srv.info())Map
4000 · seed 50001
- map
- Procedural Map
- size
- 4000
- seed
- 50001
Server
srv.info()- address
- 202.36.95.80:21708
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 21:23 UTC
- hostname
- –
- first seen
- 15 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 553 on average | 324/375 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 217/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 294 on average | 35/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 293 on average | 31/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 273 on average | 57/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 252 on average | 73/200 |
Quick answers
From the figures on this page.
Player counts
How does M1M1KA compare in the rankings?
Rank #8,515 on seven-day player hours for M1M1KA, within the top 38% of all ranked servers.
What population does M1M1KA carry?
The sample now reads 0 players for M1M1KA, out of 10 slots. Over the last seven days it averaged 0 players and peaked at 1.
Server data
What does performance look like on M1M1KA?
Server fps over the last 48 hours averages 94; the floor is 32. Entity numbers reached 89,860, and that includes buildings, deployables and the rest. Memory peaked at 4,380 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does M1M1KA run?
Rust network protocol 2635 and build 168909 on Linux is what M1M1KA runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is M1M1KA, and is it online now?
M1M1KA reports itself online at the current refresh. Count back 15 hours from its reported uptime to get the last restart. 161 of 168 hours up over the last 7 full days, or 96%. Its earliest recorded date in Rust Data is 15 September 2026.
Where does M1M1KA sit?
No region is published by M1M1KA. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 202.36.95.80:21708.
Settings and map
What rules and settings are recorded for M1M1KA?
No gather rate appears in the name: M1M1KA. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Community is its browser category. Anti-cheat status: VAC on.
Which map has M1M1KA loaded?
M1M1KA runs a procedural map of size 4,000 with seed 50001, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does M1M1KA wipe, and on what schedule?
Too few wipes are on record for M1M1KA to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 26 days 2 hours ago, and that is the one in play.
What is wipe day on M1M1KA like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 23 hours after it began.
Tags, lists
Which Rust Data filters and lists contain M1M1KA?
On Rust Data, M1M1KA appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on M1M1KA hold?
Read by the game's server browser, the tags M1M1KA publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
How can I connect to M1M1KA?
In Rust, F1 opens the console: type client.connect 202.36.95.80:21708. Launch Rust on this page does the same by opening the game through Steam and connecting.