A quiet classroom so far: 0 of 1 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,323 on player hours.
Uptimehours on the list, last 48
2/ 100
F
Attendance needs work: on the list only 1 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
24/ 100
F
Lost ground: down 7,831 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Wiped
Peak
Crowd
Lasted
Players before
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by MITSUYOMI. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 126.217.67.194:28015.
How reliable is MITSUYOMI, and is it up?
At this moment, MITSUYOMI is offline; the last time it was seen was 6 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 16 October 2026.
On what Rust version does MITSUYOMI sit?
The server MITSUYOMI is on Rust network protocol 2634 and build 167781 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does MITSUYOMI reset?
MITSUYOMI has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 13 days 1 hours.
Population
What position does MITSUYOMI hold in the rankings?
In the top 69% of all ranked servers, MITSUYOMI sits at #15,323 for player hours over the last seven days.
Is MITSUYOMI a busy server?
It has been 6 hours since MITSUYOMI was last seen, and it is offline right now. A seven-day average of 0 players applies here.
Lists and filters
What do MITSUYOMI's tags stand for?
You'll see MITSUYOMI tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does MITSUYOMI appear in the Rust Server Score lists and filters?
Rust Server Score lists that include MITSUYOMI: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules and settings
How is MITSUYOMI set up, and what rules does it keep?
Nothing in the name of MITSUYOMI states a gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
MITSUYOMI runs which map?
MITSUYOMI runs a procedural map, which the game generates.
How to join
What is the way to join MITSUYOMI?
To connect, start Rust, press F1, and type client.connect 126.217.67.194:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A term to build on. Strongest in standing (F); population is the one to work on (F).