EchoChamber_JP_Rust
Online EA 160.251.166.192:28015 checked 8m ago
Server instruments
last reading Thu 03:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 21 · below 20 is lag, below 10 is badEntities
48 h range 83,792–87,214 · memory 3,728 MBUptime
7 h 59 min since its last restart, at the last readingPlayers
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 68% of all ranked servers, top 89% 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 13h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC7d 13hFW
- WPT 2Thu 3 Dec, 19:00 UTC35d 13hFW
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- 39/100
- 20/88
- 14/100
- 11/100
- 11/200
- 10/100
Quick answers
from the figures on this pageWipe timing
What happens on EchoChamber_JP_Rust when wipe day comes?
At their busiest, its recent wipes drew 1 players on average. 2 hours after the wipe, the crowd peaked on the latest wipe.
What wipe timing does EchoChamber_JP_Rust follow?
With the force wipe, once a month, EchoChamber_JP_Rust wipes. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 27 days 3 hours ago the current world was made. Its tags carry a monthly wipe schedule.
Tags
How should you read the tags on EchoChamber_JP_Rust?
These are the tags EchoChamber_JP_Rust publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp69 (Max players): Slots: 69; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^q (Premium): Check: access. Premium players only; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server; modded (Modded): Plugins or settings make this a modded server; EA (East Asia): The server browser files it under East Asia. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show EchoChamber_JP_Rust?
On Rust Metrics, EchoChamber_JP_Rust sits in these lists: Modded Rust servers, checked live 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.
Player count
Where does EchoChamber_JP_Rust sit in the rankings?
Player hours over the last seven days put EchoChamber_JP_Rust at #15,194, #499 in Asia, in the top 68% of all ranked servers.
What is the population on EchoChamber_JP_Rust?
Current headcount on EchoChamber_JP_Rust: 0 players, 69 slots available. Check: players over seven days. Average 0, peak 1.
Server details
Which location does EchoChamber_JP_Rust run from?
EchoChamber_JP_Rust gives Asia as its location, with the EA tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 160.251.166.192:28015.
What Rust version is EchoChamber_JP_Rust on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by EchoChamber_JP_Rust. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for EchoChamber_JP_Rust?
Check: fps. Average 55 server fps over the last 48 hours, low of 21. Within range. Reading: 87,214 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 5,262 MB. What players call lag comes from low fps and an entity count on the rise.
How reliable is EchoChamber_JP_Rust, and is it online now?
Check: connection. EchoChamber_JP_Rust is online at this moment. By its reported uptime, the last restart was roughly 7 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on EchoChamber_JP_Rust?
Reading the name gives no gather rate for EchoChamber_JP_Rust. The group cap is 8 players, which is the default in the game. Mode check gives pve; other players are not fought. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Check: access. Premium players only. VAC is on. That is Valve's anti-cheat.
Which map is live on EchoChamber_JP_Rust?
Check: map. Procedural, size 4,500, seed 1337, generated by the game on EchoChamber_JP_Rust. View it on RustMaps from this page: matching size and seed give an identical map. Map name, as listed: Custom Map.
Connection
What do you do to join EchoChamber_JP_Rust?
Press F1 in Rust and enter client.connect 160.251.166.192:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. Check: access. Premium players only. You can find its website at http://160.251.166.192/index.html.