echostore local test
Offline 204.93.237.12:28315 checked 7d 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 21 Oct, 22:53 UTC7d ago | 0 | – | running | 0 |
| Wed 21 Oct, 08:35 UTC8d ago | 0 | – | 0.6 days | 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
Population
How does echostore local test rank against other Rust servers?
The last seven days of player hours place echostore local test at #15,339, within the top 69% of all ranked servers.
How busy is echostore local test?
echostore local test is offline at this count; we last saw it 7 days 17 hours ago.
Lists and tags
What do the server tags on echostore local test mean?
These are the tags echostore local test publishes, as read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp5 (Max players): You can join up to 5 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2634 (Protocol): Your game needs the same version, protocol 2634, to join; cs167781 (Build): Game build: 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): This server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include echostore local test?
echostore local test appears among the Rust Population lists that follow: Modded Rust servers, counted. Filter the server list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks and it will show up.
Wipe schedule
What does wipe day look like on echostore local test?
The busiest point of its recent wipes averaged 0 players. The crowd on the latest wipe peaked 0 hours in.
What is the wipe schedule on echostore local test?
Its rhythm cannot be told yet: too few of echostore local test's wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 7 days 17 hours ago the current world was made.
Settings
Which map does echostore local test run?
echostore local test uses a map the game generates: procedural.
What are the rules and settings on echostore local test?
Nothing in echostore local test's name says how gather works. Eight players per group is the default, and it applies here. This server runs survival, raid, build and gather: the standard game. Fighting and raiding between players is allowed. Modded is its browser category: plugins or settings change the game. You will find Oxide running as plugins. The anti-cheat VAC from Valve is disabled.
Server details
Which version of Rust does echostore local test run?
The setup is Rust network protocol 2634 and build 167781 on Linux for echostore local test. Steam updates your game automatically, but you need the same protocol to join.
Is echostore local test online, and how reliable is it?
We last saw echostore local test 7 days 17 hours ago, and it is offline now. Over the last 7 full days, 0 of 168 hours were online, or 0%. On 21 October 2026, Rust Population saw it for the first time.
Where is echostore local test located?
Nothing published by echostore local test states a region. The location a server claims is what Rust Population shows, not the place where the machine stands. Connect at 204.93.237.12:28315.
How to join
How do I join echostore local test?
Open the console with F1 in Rust and enter client.connect 204.93.237.12:28315. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.