Station XX-15339 · no signal
echostore local test
Offline 204.93.237.12:28315 checked 7d ago
- Players now
- 0/ 5
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,339
- top 69%
- Last wipe
- 7d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 5 slots
- Motion · 24 h
- M –not enough readings
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
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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.
- usual gap
- 0.6 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 21 Oct, 22:53 UTC7d ago | M0.0■steady | 0 | – | – | running | 0 |
| Wed 21 Oct, 08:35 UTC8d ago | M0.0■steady | 0 | – | 0.6 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on echostore local test?
The map on echostore local test is procedural, produced by the game.
Which settings and rules apply on echostore local test?
The name of echostore local test gives no gather rate. Groups hold up to 8 players, which is the default for the game. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC off, Valve's anti-cheat.
Live population
What is the current population on echostore local test?
No players are recorded on echostore local test at this moment; it is offline, and the last sighting was 7 days 11 hours ago.
How does echostore local test rank against other Rust servers?
On player hours for the past week, echostore local test sits at #15,339, which puts it inside the top 69% of every ranked server.
Server details
How reliably does echostore local test stay online?
echostore local test is down at the moment; the last recorded contact was 7 days 11 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 21 October 2026.
Where in the world is echostore local test hosted?
No region is published by echostore local test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 204.93.237.12:28315 is the address it uses.
Which Rust version is echostore local test running?
On Linux, echostore local test runs Rust network protocol 2634 and build 167781. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on echostore local test?
The recent wipes averaged a busiest count of 0 players. The peak on the most recent wipe came 0 hours after the wipe.
On what timetable does echostore local test run its wipes?
On record so far are too few of echostore local test's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 7 days 11 hours.
Server tags
What do the server tags on echostore local test mean?
These are the tags echostore local test publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp5 (Max players): The server has 5 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does echostore local test appear?
The Rust Server Trends lists that take in echostore local test are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Join the server
What steps get you onto echostore local test?
To join, enter client.connect 204.93.237.12:28315 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.