RUST METRICSFlight deck · live data
Data live Servers11,891 Players102,658 Populated3,942 Fresh wipes 3 h337 Scan5 min
‹ All servers162.43.32.28:28015
Offline Full Queue Fresh wipe Wipe due No query

YAKOCHU

Offline 162.43.32.28:28015 checked 10d ago

pve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.8 1.5 2.2 3 PAX 0 /3

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,256top 69%
Last wipe41d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep4 Oct11 Oct18 Oct25 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

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

00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 8 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 18 Sep, 05:18 UTC41d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on YAKOCHU?

At their busiest, its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 8 hours in.

What wipe timing does YAKOCHU follow?

The rhythm of YAKOCHU's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 41 days 9 hours ago.

Tags

Which tags does YAKOCHU carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp3 (Max players): Slots: 3; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): The server runs game build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^p (PvE): No fighting between players: the world itself is the hazard from YAKOCHU. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does YAKOCHU appear in Rust Metrics lists and filters?

These Rust Metrics lists carry YAKOCHU: Rust community servers: live readings and Rust PvE servers. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.

Player count

Where does YAKOCHU sit in the rankings?

Ranking for YAKOCHU: #15,256 on seven-day player hours, top 69% of all ranked servers.

How full does YAKOCHU get?

YAKOCHU is not responding; status offline, last seen 10 days 22 hours ago.

Server details

What location is YAKOCHU hosted in?

No region tag on YAKOCHU. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 162.43.32.28:28015.

What Rust version is YAKOCHU on?

Version check: Rust network protocol 2633 and build 164530 on Linux, run by YAKOCHU. Matching protocol is required to join. Let Steam update your game.

What is the uptime on YAKOCHU, and is it online?

YAKOCHU reports offline. The last reading came 10 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 17 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on YAKOCHU?

Reading the name gives no gather rate for YAKOCHU. 8 players per group, the default value. Mode check gives pve; other players are not fought. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on YAKOCHU?

From seed 20260918, the game generates the procedural map on YAKOCHU. Its size is 5,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How can you get onto YAKOCHU?

To join: start Rust, press F1 and type client.connect 162.43.32.28:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp3,ptrak,$r?,v2633,^p,gmrust,cs164530,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp3
Max players Slots: 3.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build The server runs game build 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

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.