Working its way up from the back of the class: #15,256 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
51/ 100
D
Moving up: up 392 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 8 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 18 Sep, 05:18 UTC39d ago
2
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by YAKOCHU. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 162.43.32.28:28015 is the address to use.
Is YAKOCHU up, and how steady is its uptime?
At this moment, YAKOCHU is offline; the last time it was seen was 9 days 3 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 17 September 2026.
What Rust version is YAKOCHU on?
Rust network protocol 2633 and build 164530 on Linux is what YAKOCHU runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does YAKOCHU wipe, and how often?
The record holds too few of YAKOCHU's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 39 days 14 hours.
What happens on YAKOCHU when wipe day arrives?
The average peak on its recent wipes was 2 players. Peak numbers came 8 hours into the latest wipe.
Player numbers
Where does YAKOCHU sit among Rust servers?
In the top 69% of all ranked servers, YAKOCHU sits at #15,256 for player hours over the last seven days.
How many players does YAKOCHU usually have?
The last sighting of YAKOCHU was 9 days 3 hours ago, and it is offline right now.
Tags and filters
What do YAKOCHU's tags stand for?
The game's browser takes its cue from the tags YAKOCHU has set: gmrust (Game mode): Rust survival, played by the standard rules; mp3 (Max players): 3 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): The game build is 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^p (PvE): Players do not fight one another here; the world is the danger. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show YAKOCHU?
Rust Server Score lists that include YAKOCHU: Best community servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Server rules
What settings and rules apply on YAKOCHU?
You will find no gather rate in the name of YAKOCHU. With no change from the game default, groups take up to 8 players. It runs pve, no PvP between players. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map YAKOCHU uses?
YAKOCHU runs a game-generated procedural map at size 5,000, seed 20260918. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How should you connect to YAKOCHU?
To connect, start Rust, press F1, and type client.connect 162.43.32.28:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp3,ptrak,$r?,v2633,^p,gmrust,cs164530,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp3
Max players3 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThe game build is 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
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 momentum (D); standing is the one to work on (F).