Players now
Live- Full
- 0%
- In queue
- 0
- Peak, 48 hours
- 1
- Peak, 7 days
- 1
0% full
Rank
top 67% · #475 in EA
7-day average
peak 1
Last wipe
monthly schedule
Next wipe
Thu 5 Nov, 19:00 UTC FW
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
daily · 1 is bestTop 67% of all ranked servers, top 88% in EA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 3h. The force wipe · high confidence
Coming wipes
- 7d 3hThu 5 Nov, 19:00 UTCFW
- 35d 3hThu 3 Dec, 19:00 UTCFW
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| 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- 1 38/ 100
- 2 19/ 88
- 3 15/ 100
- 4 14/ 100
- 5 11/ 200
- 6 11/ 100
Quick answers
from the figures on this pageServer details
Is EchoChamber_JP_Rust online, and how reliable is it?
EchoChamber_JP_Rust is up and taking players now. The uptime it reports puts its last restart about 18 hours ago. It was online 99% of the last 7 full days, which is 167 of 168 hours. Our records for it start on 13 September 2026, when Rust Dashboard first saw it.
Which version of Rust does EchoChamber_JP_Rust run?
Rust network protocol 2635 and build 168909 is running on EchoChamber_JP_Rust, which sits on Linux. Joining needs the same protocol on your side, and Steam handles that update.
Where is EchoChamber_JP_Rust located?
In Asia, EchoChamber_JP_Rust lists itself with the EA tag. A server's stated location is what Rust Dashboard displays; it does not check where the machine stands. 160.251.166.192:28015 is where it lives.
Does EchoChamber_JP_Rust run smoothly?
Across the last 48 hours the average was 60 fps, with a floor of 21. Buildings, deployables and everything else added up to a peak of 87,214 entities. Memory use peaked at 5,262 MB. Players feel lag when fps drops and the entity count climbs.
Tags, lists
Which Rust Dashboard lists and filters include EchoChamber_JP_Rust?
The Rust Dashboard lists that carry EchoChamber_JP_Rust are: Modded Rust servers, live now 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.
What do the server tags on EchoChamber_JP_Rust mean?
The browser in the game reads gmrust (Game mode): The game runs on standard Rust survival settings; mp69 (Max players): It holds 69 slots; ts8 (Group limit): This is the game's own limit of 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code is blank; ^m (Monthly): Expect one wipe a month: it lands with the Facepunch force wipe; ^p (PvE): There is no player fighting: the world provides the danger; ^q (Premium): You need Rust's premium status to get in; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Modded is where it sits: plugins or settings change how the game plays; modded (Modded): Modded is where it sits: plugins or settings change how the game plays; EA (East Asia): East Asia is where the server browser puts it from EchoChamber_JP_Rust as its tags. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
Player counts
How busy is EchoChamber_JP_Rust?
EchoChamber_JP_Rust has 0 of its 69 slots filled at the moment. Averaged across the last seven days: 0 players, peaking at 1. The busiest point in the last 48 hours was 12:00 UTC, averaging 0 players.
How does EchoChamber_JP_Rust rank against other Rust servers?
Player hours over seven days put EchoChamber_JP_Rust at #14,838 overall and #475 in Asia, in the top 67% of all ranked servers.
Reset times
What does wipe day look like on EchoChamber_JP_Rust?
Its recent wipes averaged a peak of 1 players. Peak crowd on the latest wipe came 2 hours after it began.
What is the wipe schedule on EchoChamber_JP_Rust?
Wipes come once a month on EchoChamber_JP_Rust, in step with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes, and that is its next wipe, as it is for every Rust server. The world it runs now dates from 27 days 13 hours ago. The tags carry a wipe schedule of once a month.
Map and rules
What are the rules and settings on EchoChamber_JP_Rust?
You will not find a gather rate in the name of EchoChamber_JP_Rust. The group limit is 8 players, which is the game's default. pve is what it plays, no PvP between players. The server browser lists it under Modded, where plugins or settings change the game. The plugin count is Oxide. You need Rust's premium status to get in. VAC is on: that is Valve's anti-cheat.
Which map does EchoChamber_JP_Rust run?
A procedural map of size 4,500 with seed 1337 is what EchoChamber_JP_Rust runs, generated by the game. This page links to RustMaps, where the map looks the same for its size and seed. This is the map name: Custom Map.
Join
How do I join EchoChamber_JP_Rust?
The console in Rust opens with F1, and client.connect 160.251.166.192:28015 goes in there. Launch Rust on this page is the other route, opening Rust through Steam to connect you. You need Rust's premium status to get in. You can find it online at http://160.251.166.192/index.html.
