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
434 views
When looking at my stats, I notice they are off by one from what GC.com shows.  I have 80 lab caches which I have subtracted, but I'm still off by one.  My project-gc stats show 3599, and it should be 3600 after removing the 80 lab caches.  I've tried to figure out where the problem is, but have been unsuccessful.  Anyone have any ideas?
in Support and help by chihuahuajill (220 points)

1 Answer

0 votes
 
Best answer
Hmm... looks like geocaching.com shows you as having 3052 Traditional finds in the Stats section, but only 3051 when you look at the list. Since only 3051 show in the list, that would be what PGC is using. Looks like a bug on the geocaching.com end.
by sumbloke (Expert) (35.1k points)
selected by chihuahuajill
Thank you for the quick response!!  I know how to look at my traditional finds in the Stats section, but can you tell me how you saw the number of traditional finds when you look at the list?  I plan on asking geocaching.com, and would like to know how you saw that part.
Go to your profile page https://www.geocaching.com/profile/?u=chihuahuajill and then click on "Traditional Geocaches". You will get a list of all Traditionals you have found and above the list it says "Total Records: 3051".
Thank you all so much for the help!!  I really appreciate it.
I don't think it's a bug. You have probably logged a cache that has later been redacted (not just archived, but removed entirely). When that happens it is still included in your find count but isn't included in your list of finds, and the cache page can't be viewed.
@pinkunicorn: What could be a reason that a cache is removed entirely? I didd't know, that this is possible...
One reason could be that it was published by mistake (like if a reviewer misses that it should be published for an event).

It could also be due to landowner requests or that the cache was in a dangerous place (very near an active railroad, etc).
...