1/125
Last checked 51 s ago
Wiped 1 d ago
0 avg wipe peak
Vanilla
Vanilla
Procedural Map
[JP][Slo Duo Trio]Under development Survivor
Server admin? Sign in with Steam to claim this server.
143 ms · Chicago
Last checked 6 m ago
0 / 60 players
Procedural Map
Max 3 29 days live Avg ping 149.8 ms Avg jitter 9.7 ms Wipe cycle 5.3 ±2.6 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 126.235.65.137:28015
First seen 04.09.2026
Last wipe: (1 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 7.1 | |
| 6 | |
| 1 | |
| 7.2 | |
| — |
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 7 Sep 16 · 13:48 UTC Median daily peak 3 (median of daily peaks, not average population)
Observed daily peak
27 full · 0 partial · 3 offline · 1 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 2
- Sep 25
- Sep 19
- Sep 18
- Sep 11
Server info
JP PvP | Solo/Duo/Trio | Weekly Wipe | MAX PING 120ms | UNDER DEVELOPMENT / 讒狗ｯ峨・繝・せ繝井ｸｭ | 豁｣蠑冗ｨｼ蜒阪↓蜷代￠縺ｦ隱ｿ謨ｴ荳ｭ縺ｧ縺吶ゅし繝ｼ繝舌・蜷阪・莠ｺ謨ｰ繝ｻMAP繝ｻ繝ｫ繝ｼ繝ｫ繝ｻ繝励Λ繧ｰ繧､繝ｳ遲峨・莉雁ｾ悟､画峩縺輔ｌ繧句ｴ蜷医′縺ゅｊ縺ｾ縺吶・| Currently under development. Name, player limit, map, rules and plugins are subject to change.
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 143 ms | 1 | |
| Online | 160 ms | 1 | |
| Online | 151 ms | 1 | |
| Online | 160 ms | 1 | |
| Online | 151 ms | 1 | |
| Online | 158 ms | 1 | |
| Online | 148 ms | 1 | |
| Online | 170 ms | 1 | |
| Online | 148 ms | 2 | |
| Online | 139 ms | 2 | |
| Online | 152 ms | 1 | |
| Online | 138 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 138 ms | 0 | |
| Online | 149 ms | 0 | |
| Online | 142 ms | 0 | |
| Online | 151 ms | 0 | |
| Online | 152 ms | 0 | |
| Online | 151 ms | 0 | |
| Online | 141 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 148 ms | 0 | |
| Online | 158 ms | 0 | |
| Online | 138 ms | 0 | |
| Online | 138 ms | 0 | |
| Online | 157 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 151 ms | 0 | |
| Online | 143 ms | 0 | |
| Online | 171 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 152 ms | 0 | |
| Online | 152 ms | 0 | |
| Online | 161 ms | 0 | |
| Online | 152 ms | 0 | |
| Online | 138 ms | 0 | |
| Online | 148 ms | 0 | |
| Online | 148 ms | 0 | |
| Online | 142 ms | 0 | |
| Online | 162 ms | 2 | |
| Online | 170 ms | 1 | |
| Online | 163 ms | 1 | |
| Online | 152 ms | 1 | |
| Online | 151 ms | 0 | |
| Online | 140 ms | 0 | |
| Online | 148 ms | 0 | |
| Online | 170 ms | 0 | |
| Online | 160 ms | 0 |
Other servers in Japan (low ping)
Rust 2x
0/100
Last checked 4 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.