EchoChamber_JP_Rust
Online EA 160.251.166.192:28015 checked 11m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 66% of all ranked servers, top 87% in EA. Ranked on player hours over the last seven days.
Bx1Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 6d 23h. 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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on EchoChamber_JP_Rust?
Its recent wipes drew an average peak of 1 players. The crowd on the latest wipe reached its peak 2 hours in.
What is the wipe schedule on EchoChamber_JP_Rust?
The only wipe on EchoChamber_JP_Rust is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe, when all Rust servers wipe. The world in play now was made 27 days 17 hours ago. The tags list one wipe a month.
Population
How busy is EchoChamber_JP_Rust?
Of 69 slots on EchoChamber_JP_Rust, 0 are in use right now. A seven-day average of 0 players, with a peak of 1. Its busiest point in the last 48 hours was 12:00 UTC, averaging 0 players.
How does EchoChamber_JP_Rust rank against other Rust servers?
On player hours over the last seven days, EchoChamber_JP_Rust is #14,792 globally (top 66%) and #467 in Asia.
Map and rules
Which map does EchoChamber_JP_Rust run?
EchoChamber_JP_Rust runs a procedural map of size 4,500 with seed 1337, generated by the game. The map is the same for a given size and seed, so RustMaps can show it from this page. You play on a map named Custom Map.
What are the rules and settings on EchoChamber_JP_Rust?
No gather rate appears in the name EchoChamber_JP_Rust. 8 players is the default group size, and that is the limit here. pve is the game mode, other players cannot be fought. In the server browser it is Modded, meaning plugins or settings modify the game. Plugin count: Oxide. Anti-cheat: Valve's VAC is on.
About the server
Which version of Rust does EchoChamber_JP_Rust run?
The build on EchoChamber_JP_Rust is Rust network protocol 2635 and build 168909, running on Linux. Steam updates your game for you, and the protocol has to match for you to join.
Is EchoChamber_JP_Rust online, and how reliable is it?
The server is up at the moment: EchoChamber_JP_Rust is online. The uptime it reports puts the last restart at about 23 hours ago. 167 of 168 hours up over the last 7 full days, which is 99%. It first appears in Rust Heatmap records on 13 September 2026.
Where is EchoChamber_JP_Rust located?
With its EA tag, EchoChamber_JP_Rust lists itself in Asia. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. 160.251.166.192:28015 is its address.
Does EchoChamber_JP_Rust run smoothly?
It averaged 62 server fps over the last 48 hours, with a low of 42. Buildings, deployables and the rest of the world came to as much as 87,316 entities. The highest memory use was 4,761 MB. What players call lag is low fps together with a growing entity count.
Tags
Which Rust Heatmap lists and filters include EchoChamber_JP_Rust?
The Rust Heatmap lists that EchoChamber_JP_Rust fits are: Modded Rust servers, by live population and Best Rust PvE servers. Filtering the list by Region: Asia; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly brings it up.
What do the server tags on EchoChamber_JP_Rust mean?
These are the tags EchoChamber_JP_Rust publishes for the game's server browser to read: gmrust (Game mode): Rust survival, standard rules; mp69 (Max players): Slot count: 69; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): Build 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): A region code is not set; ^m (Monthly): The wipe cycle is monthly and follows Facepunch's force wipe; ^p (PvE): PvE: the danger is the world, not other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Settings or plugins alter the game, which puts it under Modded; modded (Modded): Settings or plugins alter the game, which puts it under Modded; EA (East Asia): East Asia is where the server browser puts it. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.
How to join
How do I join EchoChamber_JP_Rust?
Press F1 in Rust to open the console, then enter client.connect 160.251.166.192:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you. http://160.251.166.192/index.html is where its website is.