Rust Server TrendsSeismic network · station log
Recording Stations11,624 Players39,995 Active3,014 Wipes · 3 h94 48 h

Station XX-15256 · no signal

YAKOCHU

Offline 162.43.32.28:28015 checked 9d ago

pve
Connect
Players now
0/ 3
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,256
top 69%
Last wipe
39d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15256 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 3 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

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 peak
2players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 18 Sep, 05:18 UTC40d ago M0.3rising 2 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ABYSS | PvE | US | Vanilla | Noob Friendly NA · groups of 8+ · monthly · 52 on average
6/ 200
[EU] RustEZ Pure PvE | Low Decay | No Killing | No Raiding EU · groups of 8+ · monthly · 35 on average
11/ 200
[US] RustEZ Pure PvE | Low Decay | No Killing | No Raiding NA · groups of 8+ · monthly · 32 on average
13/ 200
【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍 EA · groups of 30+ · monthly · 22 on average
22/ 200
[PvE] Skyline PvE - No Raiding/Killing, No Decay, Noob Friendly groups of 8+ · monthly · 21 on average
13/ 150
[EU/GER] Rust Norddeutschland PVE EU · groups of 8+ · biweekly · 18 on average
2/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on YAKOCHU?

The procedural map on YAKOCHU is size 5,000 with seed 20260918, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on YAKOCHU?

The name of YAKOCHU gives no gather rate. At the game's default, groups can have up to 8 players. In pve mode, no combat against other players. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on YAKOCHU?

A reading taken now finds YAKOCHU offline; the most recent activity was 9 days 11 hours ago.

How does YAKOCHU rank against other Rust servers?

The last seven days of player hours place YAKOCHU at #15,256, in the top 69% of all ranked servers.

Server details

How reliably does YAKOCHU stay online?

No contact with YAKOCHU right now, and the last recorded contact was 9 days 11 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 17 September 2026.

Where in the world is YAKOCHU hosted?

A region is not published by YAKOCHU. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 162.43.32.28:28015.

What build of Rust does YAKOCHU use?

On Linux, YAKOCHU runs Rust network protocol 2633 and build 164530. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on YAKOCHU?

The recent wipes averaged a busiest count of 2 players. 8 hours after the latest wipe, the crowd peaked.

How often does YAKOCHU wipe, and on which days?

The rhythm of YAKOCHU cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 39 days 23 hours is how long the current world has been running.

Server tags

What do the server tags on YAKOCHU mean?

The game's server browser reads the tags YAKOCHU publishes: gmrust (Game mode): Survival in standard Rust; mp3 (Max players): The server has 3 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs164530 (Build): Game build: 164530; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^p (PvE): There's no player combat; the world provides the threat. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does YAKOCHU appear?

The Rust Server Trends lists that take in YAKOCHU are: Rust community servers without the side modes and Rust PvE servers. You will find it under these 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.

Join the server

How do you connect to YAKOCHU?

You can connect by pressing F1 in Rust and typing client.connect 162.43.32.28:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp3
Max players The server has 3 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs164530
Build Game build: 164530.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Gameplay

^p
PvE There's no player combat; the world provides the threat.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.