On air · chart position #15,183
EchoChamber_JP_Rust
Online EA 160.251.166.192:28015 checked 8m ago
Players
EchoChamber_JP_Rust
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 11h. 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
Quick answers
Host and version
Is EchoChamber_JP_Rust online, and how reliable is it?
Right now EchoChamber_JP_Rust is running. Going by the reported uptime, it restarted roughly 10 hours ago. 167 of 168 hours is what it managed over the past 7 full days, 99% of the time. The first record Rust Charts holds of it is 13 September 2026.
Where is EchoChamber_JP_Rust located?
EchoChamber_JP_Rust gives its location as Asia, using the EA tag. Rust Charts shows the location a server claims, not where the machine actually is. Connect at 160.251.166.192:28015.
Which version of Rust does EchoChamber_JP_Rust run?
Rust network protocol 2635 and build 168909 on Linux is the version EchoChamber_JP_Rust runs. Steam updates your game for you; all you need is the same protocol to join.
Does EchoChamber_JP_Rust run smoothly?
The 48-hour average was 56 server fps; the lowest point was 21. At its fullest it held 87,214 entities: buildings, deployables and the rest of the world. At most it took 5,262 MB of memory. Rising entity counts and low fps are the source of the lag players report.
Who is on
How busy is EchoChamber_JP_Rust?
EchoChamber_JP_Rust has 0 of its 69 slots filled right now. Over the last week it averaged 0 players; the high point was 1.
How does EchoChamber_JP_Rust rank against other Rust servers?
On player hours for the past week, EchoChamber_JP_Rust is #15,183: top 68% overall and #496 in Asia.
Wipe days
What does wipe day look like on EchoChamber_JP_Rust?
The busiest point of its recent wipes averaged 1 players. 2 hours into the latest wipe, the crowd reached its peak.
What is the wipe schedule on EchoChamber_JP_Rust?
The force wipe is the only wipe on EchoChamber_JP_Rust, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 27 days 5 hours is how long ago its current world was made. Its tags carry a wipe schedule of once a month.
Rules and world
What are the rules and settings on EchoChamber_JP_Rust?
No gather rate appears in the name EchoChamber_JP_Rust. The default group size of 8 players applies here. You play pve, other players cannot be fought. Modded in the server browser is where it sits; plugins or settings alter the game. Oxide plugins are running on it. Join only if you hold Rust's premium status. Valve's VAC anti-cheat is active.
Which map does EchoChamber_JP_Rust run?
A procedural map of size 4,500 with seed 1337, generated by the game, is what EchoChamber_JP_Rust runs. From this page you can look at it on RustMaps; the same size and seed make the same map. You will see the map name as: Custom Map.
Tags explained
Which Rust Charts lists and filters include EchoChamber_JP_Rust?
These Rust Charts lists include EchoChamber_JP_Rust: Modded Rust servers and Rust PvE servers. It appears under these 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.
What do the server tags on EchoChamber_JP_Rust mean?
The game's server browser sees these tags from EchoChamber_JP_Rust: gmrust (Game mode): Standard survival rules apply; mp69 (Max players): The server holds 69 slots; ts8 (Group limit): 8 per team, as the game ships it; v2635 (Protocol): Protocol 2635: join only if your game matches that version; cs168909 (Build): Build 168909 is what runs here; ptrak (Networking): RakNet is the network layer here, the game's default; $r? (Region code): No region code has been set; ^m (Monthly): One wipe a month, together with the force wipe; ^p (PvE): This is PvE: the world is the danger, not other players; ^q (Premium): Join only if you hold Rust's premium status; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Listed as modded because plugins or settings differ from the base game; modded (Modded): Listed as modded because plugins or settings differ from the base game; EA (East Asia): East Asia is where the server browser lists it. Player numbers now, queue size and world creation time sit in the tags as well, shown at the top of this page.
Join details
How do I join EchoChamber_JP_Rust?
The console is behind F1 in Rust: enter client.connect 160.251.166.192:28015 there. Or join on this page with Launch Rust, which opens Rust through Steam and connects you. Join only if you hold Rust's premium status. You can find its website at http://160.251.166.192/index.html.