Helium IoT: public Sybil-risk read

As of 2026-08-20

Public source: https://entities.nft.helium.io/v2/hotspots?subnetwork=iot · no auth, no internal data

4,860 single-coordinate stacks of ≥10 hotspots on 1,008,187 located units — the largest stack holds 501 hotspots on one coordinate (§1 lists keys your registry team can grep today).

This is an independent read of Helium IoT's own public data by the GETKINETIK bureau. We publish what the public endpoint returns — covering duplicate GPS coordinates and stacked devices — so anyone can reproduce it. We hold no token in any network we read and take no equity in graded networks.

The numbers

Metric	Value
Units observed (with coordinates)	1,008,187
On-chain with no asserted location	27,407
Coordinates holding 10+ units	4,860
Largest single-coordinate stack	501
Flagged (any heuristic)	69,715
Share of fleet flagged	6.91%

What this means — and what it doesn't

Worth a look

Multiple devices reporting the exact same GPS coordinate. At small counts this is normal — dense buildings, shared rooftops, and H3-hex snapping all produce shared coordinates legitimately. Large single-coordinate stacks are the documented stacking pattern that warrants a registry cross-check.

Not an accusation

This is not proof of fraud. Honest dense deployments can share a coordinate, and the bureau makes no accusation. The list is a review queue, not a verdict.

How to confirm it

Sample hotspot keys from the largest same-coordinate stacks in §1 and run POST /api/verify-device to confirm whether stacked asserted locations resolve to distinct, physically separate radios.

For an authoritative per-device grade — hardware-rooted signature, chain age, tamper flags — a network or operator can POST a Proof of Origin to the verify-device API.

Go deeper

Full methodology & row-level table → Verify a device → Request the full table →