RustServer_14778
Server admin? Sign in with Steam to claim this server.
149 ms · Chicago
Last checked 4 m ago
0 / 50 players
Procedural Map
45 days live Avg ping 156.3 ms Avg jitter 8.1 ms Wipe cycle 14.8 ±13.2 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 160.251.255.86:28015
First seen 19.08.2026
Last wipe: (9 h ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 1.6 | |
| 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 6 Sep 8 · 12:03 UTC Median daily peak 2 (median of daily peaks, not average population)
Observed daily peak
45 full · 0 partial · 1 offline · 45 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 3
- Oct 1
- Sep 3
Server info
ルール
・モラルのある社会人であること
・このサーバーは初心者の育成をメインとしています。
・拠点には、必ずプレイヤーの名前を書いてください。
・初心者狩り、張り付き粘着等の行動は禁止です。
・チーミングは禁止です。
・初心者狩り、張り付き粘着等の行動は禁止です。
・基本はPVPですが、PVEエリアを設定します。D3の島をPVEエリアにします。
・PVEエリアのレイドは禁止です。
・PVPエリアの住人が、PVEエリアに逃げるのも禁止です。
・PVPエリアとPVEエリア両方に拠点を作るのは禁止です。
・レイド可能時間帯は21：00～24：00
・ご意見ご要望がある際は、Moga Corp.のDiscordで教えて下さい。
・楽しいRUSTライフをおくりましょう。
・ルール違反者やチート行為は即BAN致します。
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 149 ms | 0 | |
| Online | 160 ms | 1 | |
| Online | 147 ms | 0 | |
| Online | 165 ms | 0 | |
| Online | 158 ms | 0 | |
| Online | 141 ms | 0 | |
| Online | 144 ms | 0 | |
| Online | 165 ms | 0 | |
| Online | 164 ms | 0 | |
| Online | 164 ms | 0 | |
| Online | 155 ms | 0 | |
| Online | 152 ms | 0 | |
| Online | 155 ms | 0 | |
| Online | 142 ms | 0 | |
| Online | 156 ms | 0 | |
| Online | 155 ms | 0 | |
| Online | 155 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 159 ms | 0 | |
| Online | 150 ms | 0 | |
| Online | 150 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 166 ms | 0 | |
| Online | 161 ms | 0 | |
| Online | 155 ms | 0 | |
| Online | 152 ms | 0 | |
| Online | 159 ms | 0 | |
| Online | 153 ms | 2 | |
| Online | 152 ms | 0 | |
| Online | 156 ms | 0 | |
| Online | 142 ms | 0 | |
| Online | 160 ms | 0 | |
| Online | 169 ms | 0 | |
| Online | 172 ms | 0 | |
| Online | 150 ms | 0 | |
| Online | 152 ms | 0 | |
| Online | 146 ms | 0 | |
| Online | 146 ms | 0 | |
| Online | 158 ms | 0 | |
| Online | 158 ms | 0 | |
| Online | 155 ms | 0 | |
| Online | 157 ms | 0 | |
| Online | 149 ms | 0 | |
| Online | 160 ms | 0 | |
| Online | 148 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 164 ms | 0 | |
| Online | 161 ms | 0 | |
| Online | 150 ms | 0 | |
| Online | 148 ms | 0 |
Other servers in Japan (low ping)
1/125
Last checked 2 m ago
Wiped 2 d ago
0 avg wipe peak
Vanilla
Vanilla
Procedural Map
Rust 2x
0/100
Last checked 5 m ago
Wiped 2 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.