Offline 210.131.223.197:28015 checked 24d ago
mizugamiempire
Connect
srv = rust.server("210.131.223.197:29015")
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 71% 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 2, 6 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 10:31 UTC27d ago | 2 | NaN | running | 0 |
| 1 | Fri 18 Sep, 11:20 UTC41d ago | 6 | halved by day 5 | 14 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.
display(srv.map, srv.info())
Map
3000 · seed 50000
- map
- Procedural Map
- size
- 3000
- seed
- 50000
Server
srv.info()- address
- 210.131.223.197:28015
- region
- –
- max players
- 16
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 10:31 UTC
- hostname
- –
- first seen
- 13 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 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 21/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 36/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 10/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 44/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 182/215 |
Quick answers
From the figures on this page.
Player counts
How does mizugamiempire compare in the rankings?
Over the last seven days mizugamiempire sits at #15,964 on player hours, in the top 71% of ranked servers.
What population does mizugamiempire carry?
Offline now for mizugamiempire, with the last sample 24 days 4 hours ago.
Server data
Which Rust version is mizugamiempire on?
The build is Rust network protocol 2634 and build 166586 on Linux, run by mizugamiempire. Steam updates your game for you, but the protocol must match to join.
Is mizugamiempire up, and what does its uptime show?
The latest sample has mizugamiempire offline, with a last sighting 24 days 4 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 13 September 2026.
In which location is mizugamiempire hosted?
No region is published by mizugamiempire. Rust Data does not look up where the machine stands; it shows where a server says it is. 210.131.223.197:28015 is its address.
Map and rules
Which rules apply on mizugamiempire, and what settings?
The name mizugamiempire carries no gather rate. 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. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on mizugamiempire?
mizugamiempire runs a procedural map of size 3,000 with seed 50000, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
On what schedule does mizugamiempire wipe?
Too few wipes are on record for mizugamiempire 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. The world it runs now was generated 27 days 14 hours ago.
What is wipe day on mizugamiempire like?
The average peak over recent wipes is 4 players. Peak population on the latest wipe came 6 hours in. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 5.
Lists and tags
Which lists on Rust Data hold mizugamiempire, and which filters?
These Rust Data lists include mizugamiempire: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on mizugamiempire?
These tags are published by mizugamiempire and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp16 (Max players): Slot count: 16; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166586 (Build): Build number: 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^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
What is the way into mizugamiempire?
The manual route: launch Rust, F1, then client.connect 210.131.223.197:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.