› Forums › Geocaching in Wisconsin › General › 6000 miles of geocaching

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • 12/26/2006 at 11:34 pm #1724027
    djwini

      i have a tb that i have used this year to log all the caches i’ve done. it has 6119 miles on it. that sure is a lot of travel on my part. and to think i used to be a couch potato

      12/27/2006 at 3:34 am #1767730
      marc_54140

        I do not use a tb to track my miles, but my trip to Arizona in October logged almost 6000 miles. Did a lot of driving around Phoenix, which means up to 250 miles some days!

        12/27/2006 at 3:47 am #1767731
        Team Hemisphere Dancer

          Not Having a caching companion I can get that many miles in 1 caching trip. LOL

          12/31/2006 at 3:31 pm #1767732
          Team Bear Bear

            We were going to start doing the travel bug tracking with Bear Bear, but it seems to be a lot of work. If I’m doing it correctly, first you log your cache as usual, then you must log your bug in, then out of the cache. We thought this was a neat idea and a great way to log the miles you spent caching. However we just decided to do this and going back to log 300+ caches it turns out to be very time consuming.

            Then we discovered It’s not about the numbers stats (Thanks Jim).

            In the “It’s not about the numbers stats” it has an “Approximate cache-to-cache distance:”
            Ours is shown as: 14,357.4 miles (23106 kilometres) this Excludes locationless and known traveling caches.

            I’m not sure exactly how it calculates this number but for comparisons sake it could be used to accurately(?) measure your distance versus another cacher because it would calculate everyones miles the same way.

            Food for thought anyway.

            Team Bear Bear (Chris)

            12/31/2006 at 3:51 pm #1767733
            Lostby7

              I put on hundreds of miles this month and thus far in my 2 years of caching I have logged

              “Approximate cache-to-cache distance: 16,164.45 miles (26,014.16 kilometres) (Excludes locationless and known traveling caches)”

              12/31/2006 at 4:00 pm #1767734
              djwini

                where is this–its not about the numbers stats–thing?

                i logged that bug all year, but this year decided to retire it and save myself the time. the idea was that i would be able to read thru where i had been that year in order of caches done. but having never gone back to read it, i decided not to continue. ithink i started because i didn’t want to release the coin once i bought it.

                12/31/2006 at 4:02 pm #1767735
                Lostby7

                  @djwini wrote:

                  where is this–its not about the numbers stats–thing?

                  i logged that bug all year, but this year decided to retire it and save myself the time. the idea was that i would be able to read thru where i had been that year in order of caches done. but having never gone back to read it, i decided not to continue. ithink i started because i didn’t want to release the coin once i bought it.

                  It can be found on the main page here on this site …look in the lower left hand corner….in fact it’s on this page as well look left in the “Quick Links” box.

                  12/31/2006 at 8:02 pm #1767736
                  Jeremy

                    @Team Bear Bear wrote:

                    In the “It’s not about the numbers stats” it has an “Approximate cache-to-cache distance:”
                    Ours is shown as: 14,357.4 miles (23106 kilometres) this Excludes locationless and known traveling caches.

                    It looks like other people are at least getting reasonable numbers for this stats calculation. Here is what the It’s Not About the Numbers Stats came up with for my cache finds:

                    Approximate cache-to-cache distance: 528,634.69 miles (850755.06 kilometres) (Excludes locationless and known traveling caches)

                    I know I tend to visit some remote caches, but this is amazing considering that I have only flown to one caching destination (exciting and exotic Cleveland, Ohio).

                    Oops, nevermind, I forgot about grabbing that cache on the Moon. 🙂 This added 478,000 miles to my total.

                    12/31/2006 at 9:15 pm #1767737
                    greyhounder

                      Mine:

                      Approximate cache-to-cache distance: 13,444.74 miles (21637.22 kilometres) (Excludes locationless and known traveling caches)

                      All driven miles (no flying, although I have been out to Delaware, and over to Kansas — all in the car with my greyhound!)

                      I’ve also been using my geocoins to track mileage (all sort of different ways), but as the gc.com server is too busy, I can’t write any numbers.

                      Bec

                    • Author
                      Posts
                    Viewing 9 posts - 1 through 9 (of 9 total)
                    • You must be logged in to reply to this topic.