
[JP] Vanilla/kokuuServer/PvE/V2/beeginner
Server admin? Sign in with Steam to claim this server.
151 ms · Chicago
Jitter 3.1 ms
Last checked 2 m ago
7 / 100 players
Procedural Map
46 days live Avg ping 147.4 ms Avg jitter 3.7 ms Wipe cycle 15.3 ±13.5 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 162.43.16.5:28015
First seen 02.10.2026
Last wipe: (8 h ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 11.4 | |
| 33.4 | |
| 1 | |
| — |
Player count history
Wipe timing behind this data is sometimes inferred rather than confirmed, so daily figures right around a wipe boundary can land on the wrong day. Accuracy improves over time as detection gets more precise.
Highest peak 18 Nov 7 Median daily peak 8 (median of daily peaks, not average population)
Observed daily peak
37 full · 0 partial · 0 offline · 54 no data
Population persistence across recent wipes
Each line follows one wipe cycle from the moment it started, lined up by days since that wipe rather than by calendar date — so you can compare how well this server held onto its population after different resets, independent of when each one happened.
- Nov 17
- Nov 5
- Oct 3
- Oct 2
Server info
完全VanillaServer※
※ビギナーさん大歓迎
※ストリーマー様も是非配信や参加型にご活用ください
当Server独自の特徴※
1、荒らしなどによる被害の場合物資の補填対応
2、少しでも快適にプレイが出来るように常にServer負荷の軽減実施
3、参加者様の意見を取り入れ常にServerの成長
※その他※
※必ずdiscord内利用規約のご確認をお願い致します
※原則3日以上活動が無い拠点は削除となります
(急な行事などの際は管理者までご報告を下されば最長1週間の猶予あり
※discordServer※
※discordは左下の外部ウェブサイトより参加ください
※お知らせ、ルール、お問い合わせはdiscordまで
※次回ワイプは12月4日(金)
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 151 ms | 8 | |
| Online | 147 ms | 3 | |
| Online | 145 ms | 2 | |
| Online | 149 ms | 1 | |
| Online | 145 ms | 2 | |
| Online | 147 ms | 4 | |
| Online | 151 ms | 3 | |
| Online | 147 ms | 4 | |
| Online | 147 ms | 5 | |
| Online | 147 ms | 8 | |
| Online | 145 ms | 6 | |
| Online | 147 ms | 3 | |
| Online | 149 ms | 4 | |
| Online | 147 ms | 3 | |
| Online | 147 ms | 2 | |
| Online | 147 ms | 3 | |
| Online | 145 ms | 2 | |
| Online | 145 ms | 1 | |
| Online | 148 ms | 1 | |
| Online | 145 ms | 3 | |
| Online | 151 ms | 2 | |
| Online | 149 ms | 1 | |
| Online | 149 ms | 2 | |
| Online | 145 ms | 3 | |
| Online | 147 ms | 5 | |
| Online | 145 ms | 5 | |
| Online | 145 ms | 5 | |
| Online | 150 ms | 5 | |
| Online | 148 ms | 5 |
Other servers in Japan (low ping)


Frequently asked questions
What does "wipe" mean in Rust?
A wipe resets a server's map and usually player progress too — bases, resources, and blueprints, unless the server keeps blueprints through wipes (shown here as "No BP wipe"). Most servers wipe on a regular schedule, often weekly.
What does "force wipe" mean?
Facepunch pushes a mandatory update on the first Thursday of each month that requires every Rust server to wipe, regardless of its own schedule — a "force wipe," distinct from a server's regular map wipe.
How do I know when this server wipes?
The "Next wipe" time above is extracted from the server's own published schedule. "High confidence" means the server stated an explicit date or time; "Predicted" means it's estimated from the server's typical cadence and isn't guaranteed.
How do I connect to this server?
Copy the server address above, open Rust's in-game console with F1, and run client.connect followed by the address — or connect directly through Steam's server browser using the same address.