In reply to tomrainbow:
There is a stored value we use as an ascent count. It would appear this value is out of sync with the actual logged ascents indicating it's probably not being updated when someone is either adding or removing a logged ascent.
I'm not sure exactly why it's being counted using this method, maybe there was a reason for this but I'll talk to Paul when he's back. For the time being I've changed the counting logic to actually count how many ascents there are in the database at that given moment. I've checked quite a few routes now and this seems to have fixed the issue.
If someone spots any strange values then please post here and let me know.
Martin