Rust Player Count
42,245 playing now

OnlineEA160.251.166.192:28015checked 7m ago

EchoChamber_JP_Rust

monthly wipes moddedoxidepvepremium
Players now 0/ 69 0% full
7-day average 0 peak 1
Rank #7,920 top 36% · #413 in EA
Last wipe 12d ago monthly schedule
Next wipe 21d 17h Thu 5 Nov, 19:00 UTC FW

Players

AveragePeak
00.250.50.75102:0011:0020:0006:0015:0000:00

Hourly average and peak, UTC.

Server performance

02040608002:0011:0020:0006:0015:0000: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 Sep25 Sep30 Sep5 Oct10 Oct15 Oct

Top 36% of all ranked servers, top 79% 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 21d 17h. The force wipe · high confidence

Wipe-day peak 1 players, last three wipes

Coming wipes

21d 17hThu 5 Nov, 19:00 UTC FW

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 UTC12d 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
桃乐丝 PVE - 经济 | 养殖 | 技能 | 钓鱼 | 传奇装EA · groups of 8+ · monthly · 71 on average 26/ 100
[坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼EA · groups of 8+ · monthly · 41 on average 34/ 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average 16/ 88
[JP][PvE]ゆるラス☮YURU RUSTEA · groups of 12+ · monthly · 17 on average 11/ 75
[JP]ちょっぴりHard-PvE RiSu ServerEA · groups of 8+ · monthly · 16 on average 11/ 100
【青岩-PVE服】原倍/萌新/突袭据点EA · groups of 8+ · monthly · 14 on average 7/ 200

Quick answers

from the figures on this page

Rules, map and settings

Which rules govern EchoChamber_JP_Rust?

A gather rate is absent from the name of EchoChamber_JP_Rust. Groups are capped at 8 players, the default in the game. pve is the game mode, no player-versus-player fighting. The server browser lists it under Modded, because plugins or settings alter the game. Plugins: Oxide. Entry requires Rust's premium status. VAC is on, Valve's anti-cheat.

What is the map on EchoChamber_JP_Rust?

EchoChamber_JP_Rust runs a procedural map of size 4,500 with seed 1337, generated by the game. You can see it on RustMaps from this page, because the same size and seed give the same map. Its map is called: Custom Map.

Tags and filters

Where can EchoChamber_JP_Rust be found in Rust Player Count lists and filters?

These Rust Player Count lists include EchoChamber_JP_Rust: Modded Rust servers and Rust PvE servers. You can find it on the server list using these filters: 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; Last wipe: In the last 2 weeks.

How should you interpret the tags on EchoChamber_JP_Rust?

These are the tags EchoChamber_JP_Rust publishes for the game's server browser: gmrust (Game mode): The usual Rust survival experience; mp69 (Max players): Capacity: 69 slots; ts8 (Group limit): This uses the default team cap: 8 players; v2634 (Protocol): Your game version needs to be on protocol 2634 to connect; cs167781 (Build): It runs on game build 167781; ptrak (Networking): RakNet is the game's usual network protocol, and this server uses it; $r? (Region code): A region code is not present; ^m (Monthly): Expect one wipe per month, alongside the forced wipe from Facepunch; ^p (PvE): No player-versus-player combat: the environment provides the danger; ^q (Premium): Entry requires Rust's premium status; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): It appears under Modded because plugins or settings modify the game; modded (Modded): It appears under Modded because plugins or settings modify the game; EA (East Asia): It appears under East Asia when browsing servers. You will also find its current players, its queue and its world creation time in the tags, displayed at the top of this page.

Player numbers

How many players does EchoChamber_JP_Rust have?

With 69 slots, EchoChamber_JP_Rust has 0 players at the moment. The seven-day average is 0 players, with a peak of 1. The busiest time in the last 48 hours was 10:00 UTC, with an average of 1 players.

Where does EchoChamber_JP_Rust sit in the rankings?

In the last seven days, EchoChamber_JP_Rust is #7,920 for player hours, #413 in Asia, and within the top 36% of ranked servers.

About the server

How reliable is EchoChamber_JP_Rust, and is it online?

Right now, EchoChamber_JP_Rust is up. Based on the uptime it reports, the last restart was about 5 hours ago. It was up 89% of the time over the last 7 full days, 149 of 168 hours. Rust Player Count recorded it for the first time on 13 September 2026.

What Rust version is used on EchoChamber_JP_Rust?

Rust network protocol 2634 and build 167781 on Linux is what EchoChamber_JP_Rust uses. Joining requires the same protocol on your game; Steam updates it for you.

Where can you find EchoChamber_JP_Rust?

In Asia, EchoChamber_JP_Rust lists itself with its EA tag. Rust Player Count displays the location a server claims, not the physical location of the machine. You can reach it at 160.251.166.192:28015.

What is the performance like on EchoChamber_JP_Rust?

Over the last 48 hours, the average server fps was 47, and it never dropped below 23. The highest entity count was 85,538, covering buildings, deployables and all other objects. At its highest, it used 5,063 MB of memory. Lag, as players experience it, is caused by low fps and increasing entities.

Wipe days

What should you expect on EchoChamber_JP_Rust during a wipe?

Across its recent wipes, the busiest times averaged 1 players. 2 hours after the latest wipe, the crowd hit its peak.

When does EchoChamber_JP_Rust wipe?

The only wipes for EchoChamber_JP_Rust are monthly, tied to the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and it affects all Rust servers. The present world dates from 12 days 23 hours ago. Its tags declare wipes on a monthly schedule.

Connect to the server

How can I connect to EchoChamber_JP_Rust?

To get in, press F1 in Rust and enter client.connect 160.251.166.192:28015. You can also click Launch Rust here, which opens the game through Steam and brings you onto the server. Entry requires Rust's premium status. http://160.251.166.192/index.html is its website.

Server tags

what each one means

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

Game

gmrust
Game mode The usual Rust survival experience.
mp69
Max players Capacity: 69 slots.
ts8
Group limit This uses the default team cap: 8 players.
v2634
Protocol Your game version needs to be on protocol 2634 to connect.
cs167781
Build It runs on game build 167781.
ptrak
Networking RakNet is the game's usual network protocol, and this server uses it.
$r?
Region code A region code is not present.

Wipe schedule

^m
Monthly Expect one wipe per month, alongside the forced wipe from Facepunch.

Gameplay

^p
PvE No player-versus-player combat: the environment provides the danger.

Mods and access

^q
Premium Entry requires Rust's premium status.
^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded It appears under Modded because plugins or settings modify the game.
modded
Modded It appears under Modded because plugins or settings modify the game.

Region

EA
East Asia It appears under East Asia when browsing servers.

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.