Offline 126.217.67.194:28015 checked 7h ago
MITSUYOMI
Connect
srv = rust.server("126.217.67.194:28017")
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. 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 69% 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())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 126.217.67.194:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 09:27 UTC
- hostname
- –
- first seen
- 16 Oct 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 | 159/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 190/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 67/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 12/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 20/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does MITSUYOMI rank?
Over the last seven days MITSUYOMI sits at #15,323 on player hours, in the top 69% of ranked servers.
How full does MITSUYOMI run?
The current row shows MITSUYOMI offline; the last response was 7 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is MITSUYOMI on?
The build is Rust network protocol 2634 and build 167781 on Windows, run by MITSUYOMI. The protocol has to match before you can join, and Steam does the updating.
Is MITSUYOMI up, and what does its uptime show?
The latest sample has MITSUYOMI offline, with a last sighting 7 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 16 October 2026.
In which location is MITSUYOMI hosted?
There is no region published for MITSUYOMI. Rust Data does not look up where the machine stands; it shows where a server says it is. 126.217.67.194:28015 is its address.
Settings and map
What rules and settings are recorded for MITSUYOMI?
No gather rate appears in the name: MITSUYOMI. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. 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 MITSUYOMI?
MITSUYOMI runs a procedural map, which the game generates.
Wipes and dates
When does MITSUYOMI wipe, and on what schedule?
Too few wipes are on record for MITSUYOMI to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 13 days 2 hours ago.
Tags, lists
Which lists on Rust Data hold MITSUYOMI, and which filters?
On Rust Data, MITSUYOMI appears in these lists: 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; Last wipe: In the last 2 weeks.
Which meanings do the tags on MITSUYOMI hold?
The game's server browser reads these tags from MITSUYOMI: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^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
What is the way into MITSUYOMI?
Enter client.connect 126.217.67.194:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.