echostore local test
Offline 204.93.237.12:28315 checked 7d ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
too few wipes seen yetNot 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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on echostore local test?
At their busiest, its recent wipes averaged 0 players. 0 hours after the latest wipe, the crowd peaked.
What is the wipe schedule on echostore local test?
Its rhythm cannot yet be told: too few of echostore local test's wipes are on record. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 7 days 14 hours ago.
Player counts
How busy is echostore local test?
Last seen 7 days 14 hours ago, echostore local test is offline at the moment.
How does echostore local test rank against other Rust servers?
The top 69% of ranked servers includes echostore local test, at #15,339 for player hours over the last seven days.
Settings and rules
Which map does echostore local test run?
A procedural map, generated by the game, runs on echostore local test.
What are the rules and settings on echostore local test?
The name echostore local test does not specify a gather rate. 8 players is the default group size, and that is the limit here. survival is the game mode, standard play: gathering, building and raiding. Combat between players and raiding are both possible. In the server browser it is Modded, meaning plugins or settings modify the game. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, turned off.
Location and uptime
Which version of Rust does echostore local test run?
Rust network protocol 2634 and build 167781 on Linux is what echostore local test runs. Your game must run the same protocol to join, and Steam takes care of updating it.
Is echostore local test online, and how reliable is it?
Offline at the moment: echostore local test was last seen 7 days 14 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. It first appears in Rust Heatmap records on 21 October 2026.
Where is echostore local test located?
Nothing about a region comes from echostore local test. Rust Heatmap shows the location a server states. It does not look up the machine's location. 204.93.237.12:28315 is its address.
Lists and filters
Which Rust Heatmap lists and filters include echostore local test?
Modded Rust servers, by live population are the Rust Heatmap lists that echostore local test fits. Filtering the list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks brings it up.
What do the server tags on echostore local test mean?
These are the tags echostore local test publishes for the game's server browser to read: gmrust (Game mode): Rust survival, standard rules; mp5 (Max players): The slot count is 5; ts8 (Group limit): The game default applies: 8 per team at most; v2634 (Protocol): Your game must match protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Settings or plugins alter the game, which puts it under Modded. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
How to join
How do I join echostore local test?
To join by console, open it with F1 in Rust and enter client.connect 204.93.237.12:28315. Or press Launch Rust on this page, which connects you through Steam.