Hex Dev
Online 172.93.160.200:28015 checked 12m ago
Server instruments
last reading Tue 21:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 1 · below 20 is lag, below 10 is badEntities
48 h range 120,937–150,433 · memory 4,174 MBUptime
10 h 3 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 46% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. 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 4, 15 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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 UTC27d ago | 5 | held half | 2.7 days | 0 |
| Tue 29 Sep, 05:33 UTC28d ago | 2 | – | 0.7 days | 0 |
| Sun 27 Sep, 02:49 UTC30d 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 UTC40d 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 74/500
- 131/100
- 84/225
- 31/200
- 77/700
- 17/1000
Quick answers
from the figures on this pageWipe timing
What happens on Hex Dev when wipe day comes?
An average of 2 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 15 hours. The crowd stayed above half that peak until the next wipe in 67% of its recent wipes. When it didn't hold, by day 1 it fell below half.
How often does Hex Dev wipe, and when?
There is no next wipe to predict: Hex Dev wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 13 days 5 hours ago the current world was made.
Tags
Which tags does Hex Dev carry, and what do they mean?
These are the tags Hex Dev publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Hex Dev appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Hex Dev: Modded Rust servers, checked live. 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.
Occupancy
Where does Hex Dev sit in the rankings?
Ranking for Hex Dev: #10,118 on seven-day player hours, top 46% of all ranked servers.
What is the population on Hex Dev?
0 of 40 slots are filled on Hex Dev right now. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 10:00 UTC, averaging 0 players at that hour.
Server
What location is Hex Dev hosted in?
No region tag on Hex Dev. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 172.93.160.200:28015.
What Rust version is Hex Dev on?
Reading: Hex Dev, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.
How does Hex Dev perform?
Over the last 48 hours the average was 12 server fps; the floor was 1. Reading: 150,433 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 4,559 MB. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on Hex Dev, and is it online?
Hex Dev reports online. Status: normal. Reading: uptime. About 10 hours ago it restarted, on its own count. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Map and rules
How is Hex Dev configured, and what rules are in force?
Check: gather rate. The name Hex Dev does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Hex Dev?
From seed 1337, the game generates the procedural map on Hex Dev. Its size is 5,250. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Read the map name: Fallout Vault 117 Map.
Connection
How can you get onto Hex Dev?
Check: join. Open Rust, press F1, then enter client.connect 172.93.160.200:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.