← All clusters

Cluster axTKM_H9

2 maps · 2 servers

These servers share no common name, so there is nothing to call this cluster but its id. The id is first-party and exact; a heading taken from whichever server happens to be busiest today would not be. The busiest one is called Sluggington.

172.240.118.62:5180

In ARK: Join ARK → unofficial → paste into the filter, or use the console. We will ask you in a week whether it was any good — that answer is the only thing on this site that comes from a player rather than a name.

busiest right now — SLUGNAROK
2average players
0on right now
6highest of each server, added up
7 days agobusiest point on this chart: 4now

Watched 72.2 of the last 168 hours — 43%. The gaps below are times nobody was polling, not times the server was empty.

Across the day

Busiest around 09:00 UTC — 1.0 on average

UTC. A server’s own timezone is inferable from where this peaks — that is why observations are stored with an offset — but inferring it is not done yet, and labelling these as local would be a guess.

Rates, as the names state them

Harvest
not stated
Taming
not stated
Breeding
not stated
XP
not stated
Tribe cap
not stated

Rules

Wipes
not stated
Wipe date
not stated
Launch or event date
not stated
Offline raid protection
not stated
Playstyle tags
not stated

First-party facts

Mode
PVEfrom the first-party SessionIsPve field, not the name
Platforms
PC (Steam)
Language
not stated
Region
not stated
Discord
not stated
Mods
5 across the cluster
Accuracy
not statednothing in these names was checkable against first-party data
First seen
2026-08-24we were already watching, and it was not here - so this is an arrival

The 2 servers

MapNameOn nowAveragePeakStatus
RagnarokSLUGNAROK0/201.54live
The IslandSluggington0/200.12live

Mods 5

Mod ids as the source reports them. Names would need a CurseForge lookup this index does not do yet, and inventing one would be worse than an id.

928548929420930494935408952123
Already claimed it? Customise it here

This browser is not holding a claim yet. Claim a server in this cluster first, from that server’s own page — then come back here.