On the class lists: F (41), with population over 48 hours and no performance mark.
Players now0/ 690% full
7-day average0peak 1
Rank#15,194top 68% · #499 in EA
Last wipe27d agomonthly schedule
Next wipe7d 13hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 69 on average. Plenty of space to grow.
Standingrank on player hours
32/ 100
F
Working its way up from the back of the class: #15,194 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
92/ 100
A
Mostly smooth: 55 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
35/ 100
F
Slipped a little: down 4,542 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 68% of all ranked servers, top 89% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 13h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
7d 13hThu 5 Nov, 19:00 UTCFW
35d 13hThu 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
classmates: the same kind of game, then region, group limit, rate and wipes
You'll see EchoChamber_JP_Rust listed in Asia, tagged EA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 160.251.166.192:28015.
How dependable is EchoChamber_JP_Rust, and is it online at the moment?
You can join now: EchoChamber_JP_Rust is online. The uptime it reports puts the last restart at about 8 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
Does EchoChamber_JP_Rust perform well?
The average over the last 48 hours was 55 server fps, and it never went below 21. Buildings, deployables and everything else in the world added up to as many as 87,214 entities. At its highest, it used 5,262 MB of memory. Players feel lag when fps drops and entities pile up.
Which Rust version is EchoChamber_JP_Rust running?
You will find EchoChamber_JP_Rust on Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Resets
When does EchoChamber_JP_Rust wipe, and how often?
The force wipe each month is the only wipe EchoChamber_JP_Rust takes. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 27 days 3 hours. The tags show a monthly wipe schedule.
What happens on EchoChamber_JP_Rust when wipe day arrives?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 2 hours after it began.
Population
What position does EchoChamber_JP_Rust hold in the rankings?
Over the last seven days, EchoChamber_JP_Rust has #15,194 for player hours, in the top 68% of all ranked servers and #499 in Asia.
Is EchoChamber_JP_Rust a busy server?
With 69 slots available, EchoChamber_JP_Rust currently has 0 players. Averaging 0 players over seven days, it peaked at 1.
Lists and filters
What is meant by the tags on EchoChamber_JP_Rust?
You'll see EchoChamber_JP_Rust tagged with gmrust (Game mode): Survival in the standard Rust style; mp69 (Max players): Its slot count is 69; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^p (PvE): Players do not fight one another here; the world is the danger; ^q (Premium): You need Rust's premium status to get in; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; modded (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): The server browser lists it under East Asia in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does EchoChamber_JP_Rust appear in the Rust Server Score lists and filters?
These Rust Server Score lists count EchoChamber_JP_Rust among them: Modded Rust servers, graded and Rust PvE servers, graded. 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.
Rules and settings
What settings and rules apply on EchoChamber_JP_Rust?
Nothing in the name of EchoChamber_JP_Rust states a gather rate. The default of 8 players applies as the group cap. It runs pve, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You need Rust's premium status to get in. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map EchoChamber_JP_Rust uses?
A procedural map of size 4,500 and seed 1337, generated by the game, is what EchoChamber_JP_Rust runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
How to join
How should you connect to EchoChamber_JP_Rust?
Enter client.connect 160.251.166.192:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You need Rust's premium status to get in. You can find its website at http://160.251.166.192/index.html.
Server tags
what each one means
Published asmp69,ptrak,$r?,v2635,^p,^m,EA,^p,gmrust,cs168909,^q,ts8,^o^z,modded
Game
gmrust
Game modeSurvival in the standard Rust style.
mp69
Max playersIts slot count is 69.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^q
PremiumYou need Rust's premium status to get in.
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
modded
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
EA
East AsiaThe server browser lists it under 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.
A term to build on. Strongest in uptime (A+); population is the one to work on (F).