I climbed a peak but it didn’t count

Peaks are bagged from your recorded track, so when one doesn’t appear it’s almost always something about the recording rather than the walk.

Was it recorded? This is by far the most common answer. Following a planned route without hitting record doesn’t bag anything.
Did you save the recording? Matching runs when the recording is saved.
Has it synced? A walk recorded on a watch or another app has to reach your HiiKER account first.
Did the recording cover the summit? If it was paused, or stopped for battery before the top, the track never got there.

You may have passed just below it. Paths often contour under a top rather than over it. Beyond 150 m from the summit point, it won’t count.
Poor GPS. Thick cloud, crag and dense forest all push your track off line. If the recorded track shows you further from the top than you were, that’s what HiiKER matched against.
There’s a gap in the track near the top. If the signal dropped or the recording was paused around the summit and the track jumps more than 300 m, HiiKER can’t tell that you went over the top.
It’s a minor top. A top that rises less than 30 m above the dip joining it to a bigger hill needs you within about 50 m.
You were moving quickly. Tracks moving faster than about 12 km/h past the summit are treated as vehicle travel.

You’d already bagged it. A repeat records another ascent rather than adding to your total, so the number doesn’t move.
No celebration on the summit? Celebrations only appear when you’re recording while following a hike, for peaks on that hike’s route you haven’t bagged before. Other summits are still checked when you save the recording.
The peak isn’t on the list you’re watching. Check the peak’s own screen — it’ll tell you which lists it belongs to.
It isn’t a named summit in our data. Not every high point is a listed peak.

Get in touch from Get support on the home screen, and tell us the peak and the date of the walk so we can look at the recording.