October 15 – USA Geocoin

Hello, Mrs Hg137 here.

On our circuit of the Chilterns, we picked up a trackable, a solid geocoin. Quite an old and well travelled geocoin, too. It’s been out and about for eleven years (ELEVEN YEARS! That is really, really, really old for these kind of items), and has travelled 48,000 miles since leaving New York in October 2005 – that’s almost twice around the earth!

It has been fortunate to survive so long. Having spent two years travelling around the USA, it was lost under a car seat for some months in 2007, then discovered when the car was cleaned. It made its way to Australia, and then spent four and five months at a time waiting in caches; I guess that both geocaches and geocachers were sparser in those days. Off it went to New Zealand, and that was very nearly the end of the tale. It went missing in mid-2010 and was marked as lost. Five years (yes really!) it reappeared – a man had found the coin in a field and taken it home. In 2015, one of his children took up geocaching, recognised the coin as a trackable, and set it off on its travels again. In January 2016, it was picked up by a French geocacher, on holiday in New Zealand, who took it back to Europe via Singapore, and finally, in early October 2016 it arrived in England, to be found by us a fortnight later.

A chequered history, and some lucky escapes …

(Editor’s note: to protect the identity of this fine, well-travelled geocoin, I’ve altered its number so it can’t be discovered online – I thought that for this particular coin, all its log entries should faithfully reflect its travels.)


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: