Rust Data

rustdata.spaceservers122.59.124.222:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 122.59.124.222:28015 checked 8d ago

Echo 10X TEST

10x moddedoxide

Connect

srv = rust.server("122.59.124.222:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 1/4 # 25% full
7-day average 0 # peak –
rank #14,387 # top 65%
last wipe 8d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k16 Oct18 Oct21 Oct23 Oct26 Oct28 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.3 daysbetween real wipes
on rhythm71%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 21 Oct, 09:19 UTC8d ago 1 NaN running 0
1 Wed 21 Oct, 01:34 UTC8d ago 1 NaN 0.3 days 0
2 Tue 20 Oct, 12:25 UTC9d ago 1 NaN 0.5 days 0
3 Tue 20 Oct, 06:19 UTC9d ago 1 NaN 0.3 days 0
4 Sat 17 Oct, 10:06 UTC12d ago 1 NaN 2.8 days 1
5 Sat 17 Oct, 03:11 UTC12d ago 1 NaN 0.3 days 0
6 Fri 16 Oct, 20:36 UTC13d ago 1 NaN 0.3 days 1
7 Fri 16 Oct, 13:34 UTC13d ago 1 NaN 0.3 days 1

# 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
122.59.124.222:28015
region
–
max players
4
group limit
8, the default
wipe schedule
–
last wipe
21 Oct 2026, 10:05 UTC
hostname
–
first seen
16 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Atlas - EU 10x | No BPs | Kits | ShopEU · groups of 20+ · 10x · weekly · 350 on average421/500
1TemplarGaming 10x Swift Loot++|PvP|MyMini|SkinBox|x10 JUST WIPENA · groups of 8+ · 10x · weekly · 181 on average130/200
2Atlas - US 10x | No BPs | Kits | ShopNA · groups of 30+ · 10x · weekly · 181 on average175/200
3KRAKEN | X10 | EU | KITS | RP | FPS+EU · groups of 14+ · 10x · weekly · 154 on average222/400
4HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop]EU · groups of 8+ · 10x · biweekly · 76 on average90/150
5HollowServers.co AU 10x No BPs [Loot++|Events|MyMini|Shop]OC · groups of 8+ · 10x · biweekly · 66 on average13/150

Quick answers

From the figures on this page.

Population data

How does Echo 10X TEST compare in the rankings?

Over the last seven days Echo 10X TEST sits at #14,387 on player hours, in the top 65% of ranked servers.

What population does Echo 10X TEST carry?

Echo 10X TEST returns no live count at this refresh, having last been seen 8 days 6 hours ago.

Server facts

What Rust version does Echo 10X TEST run?

Version Rust network protocol 2634 and build 167781 on Windows is reported by Echo 10X TEST. The protocol has to match before you can join, and Steam does the updating.

Is Echo 10X TEST up, and what does its uptime show?

The latest sample has Echo 10X TEST offline, with a last sighting 8 days 6 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 16 October 2026.

Which location does Echo 10X TEST run from?

No region is published by Echo 10X TEST. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 122.59.124.222:28015 is its address.

Map and rules

Which rules apply on Echo 10X TEST, and what settings?

The name carries the figure: Echo 10X TEST runs 10x gather. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC off.

Which map has Echo 10X TEST loaded?

Echo 10X TEST runs a procedural map, which the game generates.

Wipe data

When does Echo 10X TEST wipe, and on what schedule?

Irregular wipe times on Echo 10X TEST leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 8 days 11 hours ago, and that is the one in play.

What is wipe day on Echo 10X TEST like?

The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 1 hours after it began.

Tags, lists

Which lists on Rust Data hold Echo 10X TEST, and which filters?

On Rust Data, Echo 10X TEST appears in these lists: Modded Rust servers and 10x Rust servers: the live sample. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 10x.

How should you read the server tags on Echo 10X TEST?

The game's server browser reads these tags from Echo 10X TEST: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): Slot count: 4; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

How can I connect to Echo 10X TEST?

In Rust, F1 opens the console: type client.connect 122.59.124.222:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp4
Max players Slot count: 4.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build The server runs build 167781.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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.

Rust Data 91,985 players 11,829 servers online