Return to Project-GC

Welcome to Project-GC Q&A. Ask questions and get answers from other Project-GC users.

If you get a good answer, click the checkbox on the left to select it as the best answer.

Upvote answers or questions that have helped you.

If you don't get clear answers, edit your question to make it clearer.

0 votes


I was wondering if someone could help with a problem I have involving my Most consecutive days with finds statistic.

Project-GC currently states that my streak is 288, from 2015-07-25 to 2016-05-07

but this is incorrect as I found a cache on the 7th of May ( and also on the 8th of May ( infact my streak should currently end on the 28th of May (I haven't logged my finds for the 29th May yet)

The date on my statistics says they were generated today, and I logged the cache from the 7th of may around Monday or Tuesday and the cache on the 8th of May I logged months ago! I'm not too sure how to fix this issue so my statistics are correct!

Thanks to anyone who can help me out!

in Support and help by Sir-Lancelot (220 points)

1 Answer

+1 vote
Best answer

When finds appear on the wrong date or streaks are mysteriously broken it can often be due to finds being logged from phones using apps that are known to have problems with timezones that are not the same as Groundspeak's servers are in (Seattle). We know that at least the official iPhone app and the Android app Neongeo (which isn't supported any longer) have this problem. (Apps known to handle this scenario correctly are c:geo, GCDroid and the web interface on

If you have this problem, use the web interface on to edit your finds and make sure that they have the right date. Since Project-GC doesn't get automatic notifications about edited logs, this edit may take some time to be detected (up to a month, unless the cache is logged by someone else before that).

by pinkunicorn (Moderator) (191k points)
selected by Sir-Lancelot
Sir-Lancelot in a separate topic (removed): "So If I was to delete my log for the cache on the 8th of May, and then log it again (on the 8th of May) do you think this would fix the issue? (when my stats next update of course)"

Yes, assuming you use a non-buggy client as specified above.
As an alternative to waiting for it to be detected, you can use the Support > Self Support and refresh the cache by its GC code.
Date not read/checked in
I'm trying this now. I deleted my original log and logged it again yesterday, making sure the date was correct. But that didn't seem to work. Hopefully your suggestion will help!
Thanks sumbloke that did the job!