Rust Server Analytics 103,409 players11,892 servers
All servers
Drill-through Server detail

echostore local test

Offline 204.93.237.12:28315 checked 7d ago

Drill-through
FilterServeris echostore local test
Attributes
moddedoxide
Last refreshed
Players now 0/ 5
7-day average 0 peak –
Rank #15,339 top 69%
Last wipe 7d ago no schedule published
Next wipe – too few wipes seen yet
Capacity 0% full

Players

average and peak, with its wipes marked
No hourly history yet.

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
This server has not answered a direct query in the last 48 hours.

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 best
RankRank in region
15k10k15k20k21 Oct22 Oct24 Oct25 Oct27 Oct28 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap0.6 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Wed 21 OctWed 21 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
ShockRust | Blue | NoLimit no group limit · 151 on average 114 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 135 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average 185 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 95 on average 72 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 90 on average 215 / 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 85 on average 348 / 350

Quick answers

from the figures on this page

Wipe data

The wipe schedule for echostore local test: what is it?

With too few of its wipes on record, echostore local test's rhythm is not yet clear. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world now in play was created 7 days 20 hours ago.

On echostore local test, what happens on wipe day?

Recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe the crowd peaked.

Server details

Which location hosts echostore local test?

No region is published by echostore local test. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 204.93.237.12:28315 is its address.

What Rust build does echostore local test run?

The platform is Linux, with Rust network protocol 2634 and build 167781 running on echostore local test. The protocol has to match before you can join; Steam updates it automatically.

Is echostore local test up, and how steady is its uptime?

Last seen 7 days 20 hours ago, echostore local test now reports offline. Of 168 hours in the last 7 full days, 0 were up: 0%. It entered Rust Server Analytics records on 21 October 2026.

Lists and tags

How should the tags on echostore local test be read?

The game's server browser reads the tags echostore local test publishes: gmrust (Game mode): Rust survival, standard ruleset; mp5 (Max players): Capacity of 5 slots; ts8 (Group limit): The game default applies: 8 per team at most; v2634 (Protocol): Protocol 2634 is required: your game must match to connect; cs167781 (Build): Game build: 167781; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): No region code has been set; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): Plugins or settings change the game, so it sits under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Where does echostore local test appear across Rust Server Analytics's lists and filters?

The following Rust Server Analytics lists count echostore local test among their servers: Modded Rust servers: live data. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

Against other Rust servers, how does echostore local test compare?

The seven-day player-hours rank for echostore local test is #15,339, inside the top 69% of all ranked servers.

How many players does echostore local test carry?

No response from echostore local test at the latest check, with a last sighting 7 days 20 hours ago.

Settings

What settings and rules does echostore local test use?

No gather rate is given in the name of echostore local test. The default group cap of 8 players applies. survival is the game mode, the standard game: gather, build, raid. Raiding and PvP combat are available. Plugins or settings modify the game, and it is listed as Modded. The plugin framework is Oxide. The server runs with VAC, Valve's anti-cheat, disabled.

What is the map for echostore local test?

The game generates a procedural map for echostore local test.

Connection

How can a player join echostore local test?

In the Rust console (F1), enter client.connect 204.93.237.12:28315. Launch Rust on this page also works, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Rust survival, standard ruleset.
mp5
Max players Capacity of 5 slots.
ts8
Group limit The game default applies: 8 per team at most.
v2634
Protocol Protocol 2634 is required: your game must match to connect.
cs167781
Build Game build: 167781.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code No region code has been set.

Mods and access

^o
Oxide The Oxide (uMod) plugin framework is installed.
^z
Modded Plugins or settings change the game, so it sits under Modded.

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.