Online EA 160.251.166.192:28015 checked 13m ago
EchoChamber_JP_Rust
Connect
srv = rust.server("160.251.166.192:28017")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 68% of all ranked servers, top 89% in EA. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 13h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 13h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 13h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 01:48 UTC27d ago | 1 | NaN | 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. A new world less than six hours after a wipe is a restart, not a wipe of its own.
display(srv.map, srv.info())Map
4500 · seed 1337
- map
- Custom Map
- size
- 4500
- seed
- 1337
Server
srv.info()- 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
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [坚果PVE]宗门/合成/挂机/升级/召唤/副本/拍卖 | EA · groups of 8+ · monthly · 35 on average | 39/100 |
| 1 | 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 20 on average | 18/88 |
| 2 | [熊猫PVE]修仙升级/召唤/据点/10月新档正式服 | EA · groups of 8+ · monthly · 12 on average | 14/100 |
| 3 | [JP]ちょっぴりHard-PvE RiSu Server | EA · groups of 8+ · monthly · 11 on average | 11/100 |
| 4 | 【青岩-PVE服】原倍/萌新/突袭据点 | EA · groups of 8+ · monthly · 11 on average | 9/200 |
| 5 | 新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 | EA · groups of 16+ · monthly · 10 on average | 10/100 |
Quick answers
From the figures on this page.
Player counts
How does EchoChamber_JP_Rust compare in the rankings?
On seven-day player hours EchoChamber_JP_Rust is #15,194 overall and #499 in Asia, inside the top 68% of all ranked servers.
What population does EchoChamber_JP_Rust carry?
Current row: 0 players on EchoChamber_JP_Rust, against 69 slots. Over the last seven days it averaged 0 players and peaked at 1.
Server data
How well does EchoChamber_JP_Rust perform?
Averaged over 48 hours: 55 server fps, never under 21. Entity numbers reached 87,214, and that includes buildings, deployables and the rest. The memory field tops out at 5,262 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on EchoChamber_JP_Rust?
Rust network protocol 2635 and build 168909 on Linux is what EchoChamber_JP_Rust runs. Steam updates your game for you, but the protocol must match to join.
How reliable is EchoChamber_JP_Rust, and is it up?
The current sample puts EchoChamber_JP_Rust online. The uptime it reports puts the last restart about 8 hours ago. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is EchoChamber_JP_Rust hosted?
With its EA tag, EchoChamber_JP_Rust lists itself in Asia. Rust Data does not look up where the machine stands; it shows where a server says it is. 160.251.166.192:28015 is its address.
Map and rules
What rules and settings are recorded for EchoChamber_JP_Rust?
You will not find a gather rate in the string EchoChamber_JP_Rust. No custom cap; the default of 8 players per group stands. pve is the game mode here, and no combat between players. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Only premium players get in. VAC, Valve's anti-cheat, is enabled.
Which map has EchoChamber_JP_Rust selected?
Size 4,500, seed 1337: the procedural map on EchoChamber_JP_Rust, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Recorded under map name: Custom Map.
Wipe data
When does EchoChamber_JP_Rust wipe, and on what schedule?
Once a month EchoChamber_JP_Rust wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 27 days 3 hours ago, and that is the one in play. Its tags carry a monthly wipe schedule.
What is wipe day on EchoChamber_JP_Rust like?
Across recent wipes the busiest point averaged 1 players. 2 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold EchoChamber_JP_Rust, and which filters?
These Rust Data lists include EchoChamber_JP_Rust: Modded Rust servers and Rust PvE servers. These filters bring it up 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.
Which meanings do the tags on EchoChamber_JP_Rust hold?
These tags are published by EchoChamber_JP_Rust and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp69 (Max players): The server lists 69 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^p (PvE): PvE: the world is the threat, not other players; ^q (Premium): Only premium players get in; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; modded (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): In the server browser it sits under East Asia. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way to join EchoChamber_JP_Rust?
Enter client.connect 160.251.166.192:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. Only premium players get in. http://160.251.166.192/index.html is the website recorded for it.