On the class lists: D (48), with population over 48 hours and no performance mark.
Players now1/ 402% full
7-day average0peak 3
Rank#8,158top 37%
Last wipe7h agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 40 on average. Plenty of space to grow.
Standingrank on player hours
63/ 100
C
Working its way up from the back of the class: #8,158 on player hours.
Uptimehours on the list, last 48
77/ 100
B
Missed a few lessons: on the list 37 of the last 48 hours.
Performanceserver fps, last 48 hours
22/ 100
F
Needs to work on its frame rate: 13 server fps on average.
Wipeskeeping the crowd after a wipe
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
48/ 100
D
Slipped a little: down 347 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (B); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 37% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
9 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WW··
······W
·W··W··
······W
W·W····
·······
··W
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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.4 daysbetween real wipes
on rhythm38%of its recent wipes
wipe-day peak2players, last three wipes
crowd held50%else halves by day 1
The first 48 hours of its last wipes
Wed 14 OctMon 12 OctSun 11 Oct
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 28 Oct, 13:01 UTC7h ago
–
–
running
0
Wed 14 Oct, 18:04 UTC14d ago
4
halved by day 1
13.8 days
0
Mon 12 Oct, 13:02 UTC16d ago
1
✓ held half
2.2 days
1
Sun 11 Oct, 18:44 UTC17d ago
1
–
0.8 days
0
Fri 2 Oct, 15:23 UTC26d 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 UTC40d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by Hex Dev. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 172.93.160.200:28015.
Is Hex Dev up, and how steady is its uptime?
The server is up: Hex Dev is online now. The uptime it reports puts the last restart at about 3 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
How well does Hex Dev run?
It averaged 13 server fps over the last 48 hours, with a low of 6. Buildings, deployables and everything else in the world added up to as many as 150,445 entities. At its highest, it used 4,559 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does Hex Dev sit?
The server Hex Dev is on Rust network protocol 2635 and build 168909 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Hex Dev reset?
There is no next wipe to predict on Hex Dev, as it wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 7 hours.
What should you expect from wipe day on Hex Dev?
Across its recent wipes, the busiest moments averaged 2 players. Peak numbers came 15 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 50% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Player count
Where does Hex Dev sit among Rust servers?
In the top 37% of all ranked servers, Hex Dev sits at #8,158 for player hours over the last seven days.
Is Hex Dev a busy server?
Hex Dev is showing 1 players right now, with 40 slots in total. Averaging 0 players over seven days, it peaked at 3. The highest average in the last 48 hours came at 15:00 UTC, with 2 players.
Tags and filters
How should you read the tags on Hex Dev?
You'll see Hex Dev tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Hex Dev?
Rust Server Score lists that include Hex Dev: Modded Rust servers, graded. 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 24 hours.
Map and rules
What settings and rules apply on Hex Dev?
Nothing in the name of Hex Dev states a gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Hex Dev uses?
A procedural map of size 5,800 and seed 1337, generated by the game, is what Hex Dev runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. The name of the map reads: Fallout Vault 117 Map.
How to join
How should you connect to Hex Dev?
Enter client.connect 172.93.160.200:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp40
Max playersThe server holds 40 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under 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.
A term to build on. Strongest in uptime (B); population is the one to work on (F).