Offline 162.43.32.28:28015 checked 9d ago
YAKOCHU
Connect
srv = rust.server("162.43.32.28:29015")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 18 Sep, 05:18 UTC40d ago | 2 | NaN | 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.
display(srv.map, srv.info())
Map
5000 · seed 20260918- map
- Procedural Map
- size
- 5000
- seed
- 20260918
Server
srv.info()- address
- 162.43.32.28:28015
- region
- –
- max players
- 3
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Sep 2026, 08:19 UTC
- hostname
- –
- first seen
- 17 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ABYSS | PvE | US | Vanilla | Noob Friendly | NA · groups of 8+ · monthly · 53 on average | 18/200 |
| 1 | [EU] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | EU · groups of 8+ · monthly · 34 on average | 20/200 |
| 2 | [US] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | NA · groups of 8+ · monthly · 32 on average | 17/200 |
| 3 | 【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍 | EA · groups of 30+ · monthly · 22 on average | 41/200 |
| 4 | [PvE] Skyline PvE - No Raiding/Killing, No Decay, Noob Friendly | groups of 8+ · monthly · 21 on average | 7/150 |
| 5 | [EU/GER] Rust Norddeutschland PVE | EU · groups of 8+ · biweekly · 18 on average | 4/100 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does YAKOCHU rank?
Over the last seven days YAKOCHU sits at #15,256 on player hours, in the top 69% of ranked servers.
How full does YAKOCHU run?
Offline now for YAKOCHU, with the last sample 9 days 16 hours ago.
Server data
Which Rust version is YAKOCHU on?
Rust network protocol 2633 and build 164530 on Linux is what YAKOCHU runs. Steam updates your game for you, but the protocol must match to join.
How reliable is YAKOCHU, and is it up?
Offline now for YAKOCHU, last seen 9 days 16 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 17 September 2026.
In which location is YAKOCHU hosted?
No region is published by YAKOCHU. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 162.43.32.28:28015 is its address.
Settings and map
Which rules apply on YAKOCHU, and what settings?
The name YAKOCHU carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode pve, with this note: no combat between players. The server browser lists it under Community. Anti-cheat status: VAC on.
What is the map on YAKOCHU?
The game generates the map on YAKOCHU: procedural, size 5,000, seed 20260918. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does YAKOCHU wipe, and how often?
The record for YAKOCHU holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 40 days 4 hours ago.
What is wipe day on YAKOCHU like?
Across recent wipes the busiest point averaged 2 players. 8 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does YAKOCHU appear among Rust Data lists and filters?
The Rust Data lists that YAKOCHU fits are: Rust community servers, unfiltered and Rust PvE servers. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
How should you read the server tags on YAKOCHU?
These tags are published by YAKOCHU and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp3 (Max players): The server lists 3 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs164530 (Build): The server runs build 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^p (PvE): No player-versus-player combat; the danger comes from the world. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into YAKOCHU?
In Rust, F1 opens the console: type client.connect 162.43.32.28:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.