Rust Server Analytics 32,585 players11,628 servers
All servers
Drill-through Server detail

EchoChamber_JP_Rust

Online EA 160.251.166.192:28015 checked 11m ago

Drill-through
FilterServeris EchoChamber_JP_Rust
Attributes
monthly wipes moddedoxidepvepremium
Last refreshed
Players now 0/ 69
7-day average 0 peak 1
Rank #15,180 top 68% · #499 in EA
Last wipe 27d ago monthly schedule
Next wipe 7d 12h Thu 5 Nov, 19:00 UTC FW
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
0123407:0016:0001:0009:0019:0004:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
025507510007:0016:0001:0009:0019:0004:00

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 best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 68% of all ranked servers, top 89% in EA. Ranked on player hours over the last seven days.

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h. The force wipe · high confidence

wipe-day peak1players, last three wipes

Coming wipes

InWhen, UTCKind
7d 12hThu 5 Nov, 19:00 UTCFW force wipe
35d 12hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers 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
ServerProfilePlayers now
[坚果PVE]宗门/合成/挂机/升级/召唤/副本/拍卖 EA · groups of 8+ · monthly · 35 on average 35 / 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 EA · groups of 8+ · monthly · 20 on average 18 / 88
[熊猫PVE]修仙升级/召唤/据点/10月新档正式服 EA · groups of 8+ · monthly · 12 on average 13 / 100
[JP]ちょっぴりHard-PvE RiSu Server EA · groups of 8+ · monthly · 11 on average 10 / 100
【青岩-PVE服】原倍/萌新/突袭据点 EA · groups of 8+ · monthly · 11 on average 10 / 200
新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 EA · groups of 16+ · monthly · 10 on average 12 / 100

Quick answers

from the figures on this page

Wipe cycle

The wipe schedule for EchoChamber_JP_Rust: what is it?

Once a month EchoChamber_JP_Rust wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC, the force wipe that reaches every Rust server. The current world dates from 27 days 4 hours. The tags carry a monthly wipe schedule.

Wipe day on EchoChamber_JP_Rust: what should you expect?

The average busiest count over recent wipes is 1 players. Peak population for the latest wipe came 2 hours after it began.

Server

In which region does EchoChamber_JP_Rust sit?

Its EA tag puts EchoChamber_JP_Rust in Asia. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 160.251.166.192:28015 is its address.

Which Rust version is EchoChamber_JP_Rust on?

On Linux, EchoChamber_JP_Rust runs Rust network protocol 2635 and build 168909. Your game must match the protocol to join, and Steam applies that update.

What uptime does EchoChamber_JP_Rust show, and is it up?

The current status of EchoChamber_JP_Rust is online. Its reported uptime indicates a restart roughly 8 hours ago. Of 168 hours in the last 7 full days, 167 were up: 99%. 13 September 2026 is when Rust Server Analytics first recorded it.

Is performance on EchoChamber_JP_Rust stable?

Over 48 hours the average held at 56 server fps, and the minimum was 21. At its highest the entity count was 87,214, including buildings, deployables and all else. Peak memory was 5,262 MB. Players experience lag as low fps combined with a rising entity count.

Tags

How should the tags on EchoChamber_JP_Rust be read?

Tags from EchoChamber_JP_Rust, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp69 (Max players): 69 slots in total; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set; ^m (Monthly): Monthly wipes, aligned with the force wipe; ^p (PvE): Player combat is off; the world supplies the danger; ^q (Premium): Only premium-status players can connect; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section, because plugins or settings modify play; modded (Modded): The Modded section, because plugins or settings modify play; EA (East Asia): Its browser listing sits in East Asia. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.

Where does EchoChamber_JP_Rust appear across Rust Server Analytics's lists and filters?

These Rust Server Analytics lists include EchoChamber_JP_Rust: Modded Rust servers: live data and PvE Rust servers by live population. 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 numbers

What position does EchoChamber_JP_Rust hold in the server rankings?

For player hours over the last seven days, EchoChamber_JP_Rust places #15,180 globally and #499 in Asia, in the top 68% of all ranked servers.

How many players does EchoChamber_JP_Rust carry?

Of 69 slots, 0 are filled on EchoChamber_JP_Rust at this refresh. Averaging 0 players across seven days, the server reached a peak of 1.

Settings

What settings and rules does EchoChamber_JP_Rust use?

Gather rate is not mentioned in the name of EchoChamber_JP_Rust. The default group cap of 8 players applies. pve is the game mode, no fighting other players. In the server browser it sits under Modded, where plugins or settings alter the game. Oxide plugins are run. Only premium-status players can connect. VAC, Valve's anti-cheat, is enabled.

The map on EchoChamber_JP_Rust: which one is it?

EchoChamber_JP_Rust uses a procedural map of size 4,500 with seed 1337, generated by the game. The map is reproducible from its size and seed and can be seen on RustMaps from here. Named map: Custom Map.

How to join

What is the way onto EchoChamber_JP_Rust?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 160.251.166.192:28015. Only premium-status players can connect. Find it online at http://160.251.166.192/index.html.

Server tags

what each one means

Published as mp69,ptrak,$r?,v2635,^p,^m,EA,^p,gmrust,cs168909,^q,ts8,^o^z,modded

Game

gmrust
Game mode Survival in the standard Rust format.
mp69
Max players 69 slots in total.
ts8
Group limit Team cap of 8, the stock game setting.
v2635
Protocol Joining needs your game on protocol 2635.
cs168909
Build Game build: 168909.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code No region code has been set.

Wipe schedule

^m
Monthly Monthly wipes, aligned with the force wipe.

Gameplay

^p
PvE Player combat is off; the world supplies the danger.

Mods and access

^q
Premium Only premium-status players can connect.
^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section, because plugins or settings modify play.
modded
Modded The Modded section, because plugins or settings modify play.

Region

EA
East Asia Its browser listing sits in East Asia.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.