The geokid asked to go find a cache this morning while his big sister went off to a playdate. We opted to tackle this one, which I’d failed to find a long while ago when it was missing. This time we had no such difficulty, and the geokid put his hands right on it! Nice, TFTC.
Out for a walk with the 5-y/o geokid we decided to check up on this cache to ensure it was still accessible in spite of the ongoing work to rearrange the footpaths around here. Yup, it’s still accessible (and as devious as ever!).
0/2 for the geokids and I this morning. Hunted a long while on and around the obvious place, later reassured by the hint, but eventually expanded our search based on recent logs (which suggest the hint is wrong). Interrupted by a suspicious local we decided to make an excuse to leave. Hint, possibly coordinates, maybe more needs looking at by CO.
A hard walk to an easy find, but this cache has definitely caught the worst of the stormy conditions. Its hiding place has flooded and the container is drenched. Dried as best I could, but it needs CO attention. TFTC.
Getting down the muddy bank (picture attached) to this one was a bit spicy! Like those before me, I found the cache wedged tight into its hiding space. But unlike them, I was able to construct a crude lever with which to set it free! SL, TFTC.
Hard to believe any cache could survive the gale force winds ripping over those hilltop. Hunted for some time, including getting a view as per the hint, without luck.
Found after an extended hunt, not where the hint would suggest. Looks like it blew quite a way away! Returned to pave specified by coordinates and hint. Log extremely wet, hard to sign.
You were right about the views from up here, though!
Don’t want to be a grass, but I don’t think that’s legal tinder. End of this road for me, need to loop a different direction now to stay on schedule for my planned arrival at the 2022-02-20 52 -1 geohashpoint!
Found, but only thanks to the hint! My GPSr had me on the wrong side of the road. In case anybody else is similarly affected, I found the cache about 11m away from where I expected to, at N 52 23.698, W 002 10.330. TFTC!