EchoChamber_JP_Rust
Online EA 160.251.166.192:28015 checked 14m ago
Vital stats
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 68% of all ranked servers, top 89% in EA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 14h. The force wipe · high confidence
Coming wipes
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 01:48 UTC27d 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. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Tags
Which Rust Pop Watch lists and filters include EchoChamber_JP_Rust?
These are the Rust Pop Watch lists that include EchoChamber_JP_Rust: Modded Rust servers, live and Rust PvE servers, ranked by who's hot. These are the filters that list it 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.
What do the server tags on EchoChamber_JP_Rust mean?
The game's server browser picks up these tags from EchoChamber_JP_Rust: gmrust (Game mode): Survival, standard Rust style; mp69 (Max players): Slots: 69; ts8 (Group limit): This uses the default limit of 8 players per team; v2635 (Protocol): To join, your game must be on the same protocol version: 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, which is the game's standard; $r? (Region code): Region code left blank; ^m (Monthly): A monthly wipe, synced to Facepunch's force wipe; ^p (PvE): No fighting between players: the world supplies the danger; ^q (Premium): Rust's premium status is required to join; ^o (Oxide): A plugin framework called Oxide (uMod) is running here; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing; modded (Modded): The game is changed by plugins or settings, hence the Modded listing; EA (East Asia): In the server browser it sits under East Asia. The tags also carry its current players, queue and world creation time, all shown at the top of this page.
Player counts
How does EchoChamber_JP_Rust rank against other Rust servers?
EchoChamber_JP_Rust takes #15,190 on seven-day player hours, a top 68% spot overall and #499 across Asia.
How many players are on EchoChamber_JP_Rust right now?
The current tally at EchoChamber_JP_Rust: 0 players across 69 slots. Averaging 0 players across seven days, it topped out at 1.
Server details
Is EchoChamber_JP_Rust online, and how reliable is it?
EchoChamber_JP_Rust is live at the moment. The uptime figure suggests it restarted roughly 7 hours ago. The last 7 full days saw uptime of 99%, with 167 out of 168 hours online. Rust Pop Watch's first record of it is 13 September 2026.
Does EchoChamber_JP_Rust run smoothly?
Its server fps over the last 48 hours averaged 55, with 21 as the lowest. The world carried as many as 87,214 entities, including buildings and deployables. Up to 5,262 MB of memory was used. What players experience as lag comes from low fps and a rising entity count.
Where is EchoChamber_JP_Rust located?
With its EA tag, EchoChamber_JP_Rust lists itself in Asia. Rust Pop Watch does not look up where the machine stands; it shows where a server says it is. You'll find it at 160.251.166.192:28015.
Which Rust version is EchoChamber_JP_Rust on?
On Linux, EchoChamber_JP_Rust runs Rust network protocol 2635 and build 168909. Steam updates your game so it matches the protocol needed to join.
The wipe schedule
What happens on EchoChamber_JP_Rust when wipe day comes around?
Recent wipes averaged a peak of 1 players at their busiest. The crowd on the latest wipe topped out 2 hours in.
What is the wipe schedule on EchoChamber_JP_Rust?
Wipes on EchoChamber_JP_Rust come once a month, alongside the force wipe. On Thursday 5 November at 19:00 UTC the force wipe arrives: its next wipe, and one that hits every Rust server. The world it is running now dates from 27 days 2 hours. A wipe schedule of one wipe a month is published in its tags.
Rules and settings
Which map does EchoChamber_JP_Rust run?
The procedural map on EchoChamber_JP_Rust measures 4,500 and comes from the game with seed 1337. RustMaps has it from this page, since identical size and seed give an identical map. Custom Map is how the map name reads.
What are the rules and settings on EchoChamber_JP_Rust?
The name of EchoChamber_JP_Rust says nothing about gather rate. Groups go up to 8 players, which is the default. no fighting other players: that is the pve mode. The server browser files it under Modded, where plugins or settings change the game. Oxide plugins power it. Rust's premium status is required to join. Anti-cheat is on: VAC, Valve's system.
Join up
How do I join EchoChamber_JP_Rust?
Enter client.connect 160.251.166.192:28015 in the console after pressing F1 in Rust. Or use Launch Rust here to open Rust through Steam and connect automatically. Rust's premium status is required to join. For more, see http://160.251.166.192/index.html.