Working its way up from the back of the class: #13,797 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
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
47/ 100
D
Slipped a little: down 791 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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.
No daily history yet.
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 60% 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
No region is published for MUSHIMOCHI Server. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 175.134.251.133:28015.
How dependable is MUSHIMOCHI Server, and is it online at the moment?
The server is down: MUSHIMOCHI Server is offline now, with the last sighting 25 days 13 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 2 October 2026, Rust Server Score saw it for the first time.
On what Rust version does MUSHIMOCHI Server sit?
You will find MUSHIMOCHI Server on Rust network protocol 2634 and build 166586, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does MUSHIMOCHI Server wipe its map?
MUSHIMOCHI Server has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 25 days 14 hours have passed since this world was made.
Population
Where does MUSHIMOCHI Server place in the wider field of Rust servers?
Over the last seven days, MUSHIMOCHI Server has #13,797 for player hours, in the top 60% of all ranked servers.
What does the population on MUSHIMOCHI Server look like?
MUSHIMOCHI Server is offline at the moment; the last time it was seen was 25 days 13 hours ago.
Lists and filters
How should you read the tags on MUSHIMOCHI Server?
You'll see MUSHIMOCHI Server tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp8 (Max players): The server holds 8 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; cs166586 (Build): Build number: 166586; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here 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 MUSHIMOCHI Server appear in the Rust Server Score lists and filters?
Rust Server Score lists that include MUSHIMOCHI Server: Best community servers, graded. 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.
Server rules
Which rules does MUSHIMOCHI Server enforce, and what are its settings?
Nothing in the name of MUSHIMOCHI Server states a gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on MUSHIMOCHI Server?
A procedural map, generated by the game, is what MUSHIMOCHI Server runs.
Connecting
How should you connect to MUSHIMOCHI Server?
Enter client.connect 175.134.251.133:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp8,ptrak,$r?,v2634,gmrust,cs166586,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp8
Max playersThe server holds 8 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.
cs166586
BuildBuild number: 166586.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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. Even marks across the subjects, from F to D.