Rust Data

rustdata.spaceservers38.64.18.124:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 38.64.18.124:28015 checked 2d ago

RustDev release test (local only)

moddedoxide

Connect

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

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak 1
rank #12,824 # top 58%
last wipe 24d 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 Oct19 Oct21 Oct24 Oct26 Oct29 Oct

Top 58% 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 gap1.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Fri 23 OctTue 20 OctMon 19 Oct
00.250.50.751+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 Fri 23 Oct, 01:51 UTC5d ago 1 NaN running 0
1 Tue 20 Oct, 22:42 UTC8d ago 0 NaN 2.1 days 0
2 Mon 19 Oct, 22:47 UTC9d ago 1 NaN 1 days 0
3 Sun 18 Oct, 23:44 UTC10d ago 1 NaN 1 days 0
4 Fri 16 Oct, 23:12 UTC12d ago 0 NaN 2 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
38.64.18.124:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
4 Oct 2026, 20:38 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
0ShockRust | Blue | NoLimitno group limit · 155 on average36/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average127/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average41/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average35/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average7/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average5/1000

Quick answers

From the figures on this page.

Player counts

What position does RustDev release test (local only) take in the server rankings?

Over the last seven days RustDev release test (local only) sits at #12,824 on player hours, in the top 58% of ranked servers.

How full does RustDev release test (local only) run?

The current row shows RustDev release test (local only) offline; the last response was 2 days 6 hours ago. Over the last seven days it averaged 0 players and peaked at 1.

Server facts

What Rust version does RustDev release test (local only) run?

Version Rust network protocol 2635 and build 168909 on Windows is reported by RustDev release test (local only). Joining needs the same protocol on your game; Steam handles the update.

How reliable is RustDev release test (local only), and is it up?

The latest sample has RustDev release test (local only) offline, with a last sighting 2 days 6 hours ago. Over the last 7 full days the hours up number 35 of 168, 21%. Rust Data logged it first on 16 October 2026.

Where does RustDev release test (local only) sit?

For RustDev release test (local only), no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 38.64.18.124:28015.

Settings and map

What rules and settings are recorded for RustDev release test (local only)?

No gather rate appears in the name: RustDev release test (local only). No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has RustDev release test (local only) selected?

RustDev release test (local only) runs a procedural map, which the game generates.

Wipe schedule

When does RustDev release test (local only) wipe, and on what schedule?

Irregular wipe times on RustDev release test (local only) 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. The world it runs now was generated 24 days 4 hours ago.

What is wipe day on RustDev release test (local only) like?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 1 hours in.

Tags and filters

Which Rust Data filters and lists contain RustDev release test (local only)?

The Rust Data lists that RustDev release test (local only) fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on RustDev release test (local only)?

Read by the game's server browser, the tags RustDev release test (local only) publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.

Join steps

What is the way to join RustDev release test (local only)?

In Rust, F1 opens the console: type client.connect 38.64.18.124: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 mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players 10 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^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 45,091 players 11,692 servers online