StatusLive Servers online11,688 Players63,966 Populated3,456 Wiped · 3 h120 Interval5 min Date28 OCT 2026

DWG RG-S10146Server sheetchecked 7h ago

Hex Dev

Offline 172.93.160.200:28015 checked 7h ago

moddedoxide
Connect
Players now 0/ 40 0% full
7-day average0peak 1
Rank#10,146top 46%
Last wipe13d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
00.250.50.75112:0020:0004:0012:0020:0004:00

Hourly average and peak, UTC.

Fig. 1Players on Hex Dev
Fig. 2

Server performance

0510152012:0020:0004:0012:0020:0004: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

no rhythm it keeps

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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 14 Oct, 18:04 UTC13d ago 4 – running 0
Mon 12 Oct, 13:02 UTC15d ago 1 held half 2.2 days 1
Sun 11 Oct, 18:44 UTC16d ago 1 – 0.8 days 0
Fri 2 Oct, 15:23 UTC25d ago 1 halved by day 1 9.1 days 0
Tue 29 Sep, 23:26 UTC28d ago 5 held half 2.7 days 0
Tue 29 Sep, 05:33 UTC29d ago 2 – 0.7 days 0
Sun 27 Sep, 02:49 UTC31d ago 3 held half 2.1 days 0
Fri 18 Sep, 17:11 UTC39d ago 1 halved by day 1 8.4 days 0
Thu 17 Sep, 07:46 UTC41d ago 3 – 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 155 on average
176 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average
126 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average
177 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average
132 / 700
05
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average
15 / 200
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
55 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

Is Hex Dev online, and what uptime has been recorded?

Hex Dev is offline at this moment; 7 hours ago is when it was last seen. About 5 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. On 13 September 2026 is when Rust Graphs first saw it.

How does Hex Dev perform, as measured?

12 server fps on average over the last 48 hours, and never under 1. Counted at its highest: 150,445 entities, buildings, deployables and the rest of the world included. Memory use peaked at 4,559 MB. What players feel as lag is low fps together with a climbing entity count.

In which location is Hex Dev hosted?

A region is not published by Hex Dev. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 172.93.160.200:28015 is its address.

On which Rust version is Hex Dev running?

Rust network protocol 2635 and build 168909 on Linux: that is what Hex Dev runs. To join, your game must be on the same protocol; Steam handles the update.

Player data

What player count is recorded on Hex Dev?

The latest refresh records Hex Dev as offline, last seen 7 hours ago. The seven-day mean is 0 players; the peak over the same period is 1. Over the last 48 hours the busiest hour was 10:00 UTC, at an average of 0 players.

In the rankings, which position does Hex Dev hold?

Over the last seven days, Hex Dev records #10,146 for player hours: the top 46% of all ranked servers.

Schedules

On Hex Dev, what does the data show for wipe day?

The recent wipes averaged a busiest count of 2 players. 15 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 67% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 1.

Which times and days are wipes plotted at on Hex Dev?

Hex Dev wipes at times that follow no pattern, so no next wipe can be predicted. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The world it runs now was made 13 days 17 hours ago.

Map and rules

What settings and rules apply on Hex Dev?

The name of Hex Dev records no gather rate. The group limit is 8 players, the game's default. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. Listed as Modded in the server browser: the game is changed by plugins or settings. The plugin count is Oxide. VAC is on: that is Valve's anti-cheat.

What is the map for Hex Dev?

Size 5,250 with seed 1337: that is the procedural map Hex Dev runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. The name of the map reads: Fallout Vault 117 Map.

Filters

Where does Hex Dev appear among the Rust Graphs lists and filters?

The Rust Graphs lists that carry Hex Dev are: Modded Rust servers. On the server list, these filters bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

On Hex Dev, what is meant by each tag?

gmrust (Game mode): Standard survival, as Rust plays; mp40 (Max players): The slot count is 40; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded are the tags Hex Dev publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

How to join

By what method do you join Hex Dev?

Connect with client.connect 172.93.160.200:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Standard survival, as Rust plays.
mp40
Max players The slot count is 40.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol Your game must match protocol 2635 to join.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is recorded.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is 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.

KeyTag string decoded