1/125
Last checked 1 m ago
Wiped 1 d ago
0 avg wipe peak
Vanilla
Vanilla
Procedural Map
Japan Tokyo - Chill PvE|JP
Server admin? Sign in with Steam to claim this server.
156 ms · Chicago
Jitter 0.7 ms
Last checked 1 m ago
89 / 150 players
Custom Map
45 days live Avg ping 153.8 ms Avg jitter 9.4 ms
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 162.222.17.4:30010
First seen 18.08.2026
Last wipe: (1 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 28 | |
| — |
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 137 Sep 4 Median daily peak 79 (median of daily peaks, not average population)
Observed daily peak
47 full · 0 partial · 0 offline · 44 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.
- Oct 1
- Sep 3
Server info
次回ワイプ予定: 11/6 18:00(サーバー停止は当日午前3時)
【基本設定】
Outpostで車両購入が可能
季節限定イベントを定期的に実施
毎日 6:00/18:00 に定期再起動
/otp でOutpostへテレポート可能
【TC関連ルール】
5日以上ログインがない拠点は自動削除対象
(TC登録している誰かがログインすれば維持可能)
【窃盗対策】
ほとんどの物にコードロック装着可
【禁止行為】
他プレイヤーの体験を害する行為は禁止
4人以下のチーム分割禁止(ロック制限回避防止)
5人以上は4人単位で分割可(例: 10人→4+4+2)
違反は運営が個別に判断・措置します
【補填・免責】
アイテム/車両の補填は基本なし(MODバグのみ検討)
ヘリ/カーゴ等はサーバー再起動で消滅します
データ消失の責任は負いかねます
詳細はDiscordをご確認ください
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 156 ms | 118 | |
| Online | 157 ms | 75 | |
| Online | 151 ms | 89 | |
| Online | 144 ms | 73 | |
| Online | 164 ms | 63 | |
| Online | 156 ms | 56 | |
| Online | 157 ms | 32 | |
| Online | 153 ms | 36 | |
| Online | 158 ms | 52 | |
| Online | 147 ms | 89 | |
| Online | 144 ms | 120 | |
| Online | 145 ms | 115 | |
| Online | 144 ms | 80 | |
| Online | 148 ms | 2 | |
| Online | 145 ms | 0 | |
| Online | 143 ms | 2 | |
| Online | 155 ms | 1 | |
| Online | 141 ms | 0 | |
| Online | 143 ms | 0 | |
| Online | 148 ms | 14 | |
| Online | 144 ms | 34 | |
| Online | 162 ms | 44 | |
| Online | 161 ms | 23 | |
| Online | 151 ms | 20 | |
| Online | 156 ms | 11 | |
| Online | 156 ms | 11 | |
| Online | 161 ms | 9 | |
| Online | 157 ms | 2 | |
| Online | 155 ms | 13 | |
| Online | 161 ms | 14 | |
| Online | 150 ms | 50 | |
| Online | 164 ms | 54 | |
| Online | 152 ms | 31 | |
| Online | 162 ms | 21 | |
| Online | 278 ms | 19 | |
| Online | 160 ms | 13 | |
| Online | 157 ms | 14 | |
| Online | 150 ms | 11 | |
| Online | 156 ms | 12 | |
| Online | 157 ms | 26 | |
| Online | 157 ms | 47 | |
| Online | 150 ms | 59 | |
| Online | 156 ms | 39 | |
| Online | 150 ms | 13 | |
| Online | 157 ms | 10 | |
| Online | 153 ms | 13 | |
| Online | 156 ms | 14 | |
| Online | 152 ms | 12 | |
| Offline | — | — | |
| Online | 157 ms | 19 |
Other servers in Japan (low ping)
Rust 2x
0/100
Last checked 5 m ago
Wiped 1 d ago
2x Gather1 avg wipe peakVanilla
VanillaProcedural Map
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.