Rust Data

rustdata.spaceservers172.93.160.200:28014.ipynb

Run all rust-data · live

‹ All servers

Online 172.93.160.200:28015 checked 6m ago

Hex Dev

moddedoxide

Connect

srv = rust.server("172.93.160.200:28014")
print(srv.connect_command)

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 0 # peak 1
rank #9,657 # top 44%
last wipe 13d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75123:0008:0017:0002:0011:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
0510152023:0008:0017:0002:0011:0020:00

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, measured since 17 Sep. 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
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 44% 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 gap2.2 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak2players, last three wipes
crowd held67%else halves by day 1

The first 48 hours of its last wipes

Wed 14 OctMon 12 OctSun 11 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 14 Oct, 18:04 UTC13d ago 4 NaN running 0
1 Mon 12 Oct, 13:02 UTC15d ago 1 held half 2.2 days 1
2 Sun 11 Oct, 18:44 UTC16d ago 1 NaN 0.8 days 0
3 Fri 2 Oct, 15:23 UTC25d ago 1 halved by day 1 9.1 days 0
4 Tue 29 Sep, 23:26 UTC27d ago 5 held half 2.7 days 0
5 Tue 29 Sep, 05:33 UTC28d ago 2 NaN 0.7 days 0
6 Sun 27 Sep, 02:49 UTC30d ago 3 held half 2.1 days 0
7 Fri 18 Sep, 17:11 UTC39d ago 1 halved by day 1 8.4 days 0
8 Thu 17 Sep, 07:46 UTC40d ago 3 NaN 1.4 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

5250 · seed 1337
Map of Hex Dev
map
Fallout Vault 117 Map
size
5250
seed
1337

Server

srv.info()
address
172.93.160.200:28015
region
–
max players
40
group limit
8, the default
wipe schedule
–
last wipe
14 Oct 2026, 18:04 UTC
hostname
–
first seen
13 Sep 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 · 164 on average104/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average135/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 112 on average113/225
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average29/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 86 on average105/700
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average33/1000

Quick answers

From the figures on this page.

Population data

What position does Hex Dev take in the server rankings?

Over the last seven days Hex Dev sits at #9,657 on player hours, in the top 44% of ranked servers.

What population does Hex Dev carry?

Current row: 0 players on Hex Dev, against 40 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 10:00 UTC, mean 0 players.

About the server

What does performance look like on Hex Dev?

Averaged over 48 hours: 12 server fps, never under 1. The entity count peaked at 150,433, covering buildings, deployables and the rest of the world. The memory field tops out at 4,559 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does Hex Dev run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by Hex Dev. Joining needs the same protocol on your game; Steam handles the update.

Is Hex Dev up, and what does its uptime show?

Hex Dev reports itself online at the current refresh. Count back 9 hours from its reported uptime to get the last restart. 168 of 168 hours up over the last 7 full days, or 100%. Rust Data logged it first on 13 September 2026.

In which location is Hex Dev hosted?

For Hex Dev, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 172.93.160.200:28015 is its address.

Map and rules

Which settings and rules does Hex Dev run?

You will not find a gather rate in the string Hex Dev. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has Hex Dev selected?

Size 5,250, seed 1337: the procedural map on Hex Dev, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Under map name you will find: Fallout Vault 117 Map.

Wipe schedule

When does Hex Dev wipe, and how often?

No next wipe can be predicted for Hex Dev, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 13 days 3 hours ago, and that is the one in play.

On Hex Dev, what happens on wipe day?

Recent wipes averaged 2 players at their peak. 15 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 67% of the time. Otherwise the crowd fell below half by day 1.

Tags, lists

Which lists on Rust Data hold Hex Dev, and which filters?

These Rust Data lists include Hex Dev: Modded Rust servers. 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.

How should you read the server tags on Hex Dev?

The game's server browser reads these tags from Hex Dev: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): The server lists 40 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; 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): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

What is the way into Hex Dev?

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

Game

gmrust
Game mode Rust survival in its standard form.
mp40
Max players The server lists 40 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
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 Modded listing: the game is changed by plugins or settings.

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 70,411 players 11,811 servers online