EchoChamber_JP_Rust
Online EA 160.251.166.192:28015 checked 9m ago
Measurements
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 69% of all ranked servers, top 92% in EA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 9d 0h. 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 UTC25d 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.
Quick answers
Player counts
How does EchoChamber_JP_Rust rank against other Rust servers?
Seven-day player hours put EchoChamber_JP_Rust at #15,204, or #500 in Asia, inside the top 69% of all ranked servers.
How busy is EchoChamber_JP_Rust?
Of its 69 slots, EchoChamber_JP_Rust is using 0 right now. Averaged over seven days, it drew 0 players and reached a peak of 1.
Lists and tags
What do the server tags on EchoChamber_JP_Rust mean?
The game's server browser reads the tags EchoChamber_JP_Rust publishes: gmrust (Game mode): Survival in the standard Rust style; mp69 (Max players): You can join up to 69 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): No region code is set; ^m (Monthly): Monthly wipes take place, following Facepunch's force wipe; ^p (PvE): The danger is the world, not other players: players do not fight each other; ^q (Premium): Joining requires Rust's premium status; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): Plugins or settings change the game; it is listed under Modded; modded (Modded): Plugins or settings change the game; it is listed under Modded; EA (East Asia): The server browser lists it under East Asia. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.
Which Rust Population lists and filters include EchoChamber_JP_Rust?
These Rust Population lists include EchoChamber_JP_Rust: Modded Rust servers, counted and PvE servers, counted. These are the filters it appears under when you browse the 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.
Wipe schedule
What does wipe day look like on EchoChamber_JP_Rust?
Averaged over recent wipes, 1 players were counted at the busiest point. 2 hours after the latest wipe the crowd peaked.
What is the wipe schedule on EchoChamber_JP_Rust?
EchoChamber_JP_Rust wipes with the force wipe and at no other time, once a month. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe, which takes every Rust server. Counted from 25 days 16 hours ago, that is how long the current world has stood. In its tags a monthly wipe schedule is published.
Settings
Which map does EchoChamber_JP_Rust run?
EchoChamber_JP_Rust uses a map the game generates, procedural, at size 4,500 with seed 1337. Size and seed together fix the map, so you can view it on RustMaps from this page. The name on the map is Custom Map.
What are the rules and settings on EchoChamber_JP_Rust?
No gather rate appears in the name of EchoChamber_JP_Rust. No limit is set beyond the standard 8 players per group. pve is what it runs, no player combat. The server browser files it under Modded, where plugins or settings alter the game. You will find Oxide running as plugins. Joining requires Rust's premium status. The anti-cheat VAC from Valve is enabled.
Server details
Which version of Rust does EchoChamber_JP_Rust run?
The setup is Rust network protocol 2635 and build 168909 on Linux for EchoChamber_JP_Rust. Steam updates your game automatically, but you need the same protocol to join.
Does EchoChamber_JP_Rust run smoothly?
In the last 48 hours, it averaged 46 server fps, with a low of 32. Entities peaked at 87,187, including buildings, deployables and everything else. Memory use peaked at 5,209 MB. Players feel lag when fps is low and the entity count climbs.
Is EchoChamber_JP_Rust online, and how reliable is it?
You will find EchoChamber_JP_Rust online now. The uptime it reports suggests a restart roughly 22 hours ago. It was up 100% of the time over the last 7 full days, 168 out of 168 hours. It was first seen by Rust Population on 13 September 2026.
Where is EchoChamber_JP_Rust located?
By its EA tag, EchoChamber_JP_Rust says it is in Asia. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. Connect at 160.251.166.192:28015.
Getting in
How do I join EchoChamber_JP_Rust?
To connect directly, open Rust's console with F1 and type client.connect 160.251.166.192:28015; or press Launch Rust on this page and Steam opens Rust and joins for you. Joining requires Rust's premium status. You can find its website at http://160.251.166.192/index.html.