EchoChamber_JP_Rust
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 6m ago · 160.251.166.192:28015
Abstract
We describe the public Rust server EchoChamber_JP_Rust, reached at 160.251.166.192:28015 and hosted in EA. At the last check it held 0 of 69 places, against a seven-day mean of 0 and a peak of 11. It ranks #15,190 of all servers, the top 68%, and #499 in EA. It last wiped 27d ago on a published monthly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.
Keywordsmonthly wipes modded oxide pve premium
1Summary statistics

2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 68% of all ranked servers, the top 89% in EA. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: force wipes only
The next wipe is expected Thursday 5 November, 19:00 UTC, in 7d 14h. The force wipe (high confidence).
| Measure | Value | Note |
|---|---|---|
| Wipe-day peak | 1 | players, last three wipes |
| When (UTC) | In | Kind |
|---|---|---|
| Thu 5 Nov, 19:00 | 7d 14h | force wipefw |
| Thu 3 Dec, 19:00 | 35d 14h | force wipefw |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Fri 2 Oct, 01:4827d ago | 1 | – | 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 160.251.166.192:28015 |
|---|---|
| Region | EA |
| Max players | 69 |
| Group limit | 8, the default |
| Wipe schedule | monthly |
| Last wipe | 2 Oct 2026, 01:48 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
| Map | Custom Map |
| Size | 4500 |
| Seed | 1337 |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2], pve server list [3] and next Rust wipe times [4].
| Server | Players |
|---|---|
| [坚果PVE]宗门/合成/挂机/升级/召唤/副本/拍卖EA · groups of 8+ · monthly · 35 on average | 34/100 |
| 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average | 19/88 |
| [熊猫PVE]修仙升级/召唤/据点/10月新档正式服EA · groups of 8+ · monthly · 12 on average | 15/100 |
| [JP]ちょっぴりHard-PvE RiSu ServerEA · groups of 8+ · monthly · 11 on average | 11/100 |
| 【青岩-PVE服】原倍/萌新/突袭据点EA · groups of 8+ · monthly · 11 on average | 11/200 |
| 新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简EA · groups of 16+ · monthly · 10 on average | 10/100 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1How well does EchoChamber_JP_Rust run?
Over the past 48 hours, it ran at an average of 55 server fps, with a low of 21. Buildings, deployables and all other world objects counted together reached a maximum of 87,214 entities. Memory use peaked at 5,262 MB. Players experience lag when fps is low and the entity count is rising.
A.2In which location is EchoChamber_JP_Rust based?
Asia is where EchoChamber_JP_Rust lists itself, using the EA tag. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 160.251.166.192:28015.
A.3What is the reliability of EchoChamber_JP_Rust, and is it online?
EchoChamber_JP_Rust is online at this time. It last restarted around 7 hours ago, according to its reported uptime. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. The first record of it by Rust Statistics dates to 13 September 2026.
A.4What is the Rust version for EchoChamber_JP_Rust?
EchoChamber_JP_Rust is running Rust network protocol 2635 and build 168909 on the Linux operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.
Wipe timing
A.5On what cycle does EchoChamber_JP_Rust wipe?
Once a month, EchoChamber_JP_Rust wipes in line with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC; this server's next wipe is then. 27 days 2 hours have passed since the current world was generated. According to its tags, wipes happen once a month.
A.6How would you describe wipe day on EchoChamber_JP_Rust?
Across its recent wipes, the average peak population was 1 players. The crowd reached its maximum 2 hours after the latest wipe.
Population
A.7What is the rank of EchoChamber_JP_Rust among Rust servers?
The seven-day player-hours ranking gives EchoChamber_JP_Rust #15,190, in the top 68% of ranked servers and #499 in Asia.
A.8What is the population level of EchoChamber_JP_Rust?
On EchoChamber_JP_Rust, 0 of the 69 slots are occupied at present. The peak over seven days is 1, against an average of 0.
Tags, lists
A.9How should the tags on EchoChamber_JP_Rust be interpreted?
The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp69 (Max players): 69 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): A region code has not been set; ^m (Monthly): The cycle is monthly: Facepunch's force wipe is when it wipes; ^p (PvE): Player fighting is off; danger comes from the world; ^q (Premium): Rust's premium status is required to join; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game; modded (Modded): Modded listing: plugins or settings modify the game; EA (East Asia): East Asia is the region it appears under in the server browser, which EchoChamber_JP_Rust publishes as its tags. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.
A.10Where can EchoChamber_JP_Rust be found among the Rust Statistics lists and filters?
The Rust Statistics lists that EchoChamber_JP_Rust fits are: Modded Rust servers and Rust PvE servers: live list. It appears under the following filters on the server list: Region: Asia; Type: Modded; Game mode: PvE and Premium; Server tag: Monthly ^m, PvE ^p, Premium ^q, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Settings and map
A.11Under what rules and settings does EchoChamber_JP_Rust operate?
The name of EchoChamber_JP_Rust states no gather rate. The group cap is 8 players, which is the default in the game. The mode is pve, which means players cannot fight each other. It appears under Modded in the browser: the game is changed by plugins or settings. The plugin count is Oxide. Rust's premium status is required to join. The server has VAC on, Valve's anti-cheat.
A.12On which map does EchoChamber_JP_Rust take place?
Generated by the game from seed 1337, the procedural map on EchoChamber_JP_Rust measures 4,500. Because size and seed determine the map, RustMaps can show it, linked from this page. The name of the map is Custom Map.
Connection
A.13What is the process for joining EchoChamber_JP_Rust?
Press F1 inside Rust to open the console and enter client.connect 160.251.166.192:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection. Rust's premium status is required to join. Its website can be found at http://160.251.166.192/index.html.
Appendix BServer tags
What each of the server's tags means. Published as mp69,ptrak,$r?,v2635,^p,^m,EA,^p,gmrust,cs168909,^q,ts8,^o^z,modded.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Survival on standard Rust rules. |
mp69 | Max players. 69 slots are available. |
ts8 | Group limit. The team cap is 8, which is the game default. |
v2635 | Protocol. The game protocol is 2635; your client must match it to join. |
cs168909 | Build. Build 168909 is the one running. |
ptrak | Networking. RakNet is the network layer here, as it is by default in the game. |
$r? | Region code. A region code has not been set. |
| Wipe schedule | |
^m | Monthly. The cycle is monthly: Facepunch's force wipe is when it wipes. |
| Gameplay | |
^p | PvE. Player fighting is off; danger comes from the world. |
| Mods and access | |
^q | Premium. Rust's premium status is required to join. |
^o | Oxide. Plugins are handled by Oxide (uMod). |
^z | Modded. Modded listing: plugins or settings modify the game. |
modded | Modded. Modded listing: plugins or settings modify the game. |
| Region | |
EA | East Asia. East Asia is the region it appears under in the server browser. |
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Pve server list. ruststatistics.org/top-rust-pve-servers.
- [4]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.