Geodnet: public Sybil-risk read

As of 2026-08-20

Public source: https://rtk.geodnet.com/api/v2/coverage_stations · no auth, no internal data

6 exact (lat,lng) duplicate groups on 19,490 public stations — each row in §1 is one coordinate pair your registry team can grep today.

This is an independent read of Geodnet'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)	19,490
Exact duplicate-coordinate groups	6
Near-duplicate clusters	903
Tight clusters	5
Low-precision coordinates	5
Flagged (any heuristic)	1,797
Share of fleet flagged	9.22%

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 station IDs that share an exact coordinate pair in §1 and run POST /api/verify-device on each operator's Proof of Origin to confirm whether they resolve to distinct, real device identities.

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 →