Offline 204.93.237.12:28315 checked 7d ago
echostore local test
Connect
srv = rust.server("204.93.237.12:28316")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.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 · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 21 Oct, 22:53 UTC7d ago | 0 | NaN | running | 0 |
| 1 | Wed 21 Oct, 08:35 UTC8d ago | 0 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 204.93.237.12:28315
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 21 Oct 2026, 22:53 UTC
- hostname
- –
- first seen
- 21 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 36/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 120 on average | 65/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 24/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 73/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 281/310 |
Quick answers
From the figures on this page.
Player counts
What position does echostore local test take in the server rankings?
Player hours over seven days put echostore local test at #15,339, in the top 69% of the ranked set.
What population does echostore local test carry?
echostore local test returns no live count at this refresh, having last been seen 7 days 23 hours ago.
Server facts
What Rust version does echostore local test run?
Rust network protocol 2634 and build 167781 on Linux is what echostore local test runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is echostore local test, and is it online now?
echostore local test is offline at this refresh; the last response came 7 days 23 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 21 October 2026.
Which location does echostore local test run from?
For echostore local test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 204.93.237.12:28315.
Rules, settings, map
Which settings and rules does echostore local test run?
No gather rate appears in the name: echostore local test. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC off.
Which map has echostore local test selected?
echostore local test runs a procedural map, which the game generates.
Wipe schedule
On what schedule does echostore local test wipe?
Too few wipes are on record for echostore local test to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 7 days 23 hours ago.
On echostore local test, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which Rust Data filters and lists contain echostore local test?
These Rust Data lists include echostore local test: Modded Rust servers. 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.
How should you read the server tags on echostore local test?
The game's server browser reads these tags from echostore local test: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): 5 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to echostore local test?
Enter client.connect 204.93.237.12:28315 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.