Found on a tb rescue mission exactly five years + one day after this coin was placed in GCHPEX, which was disabled the following day and never reactivated or found again until today.
We initially dismissed the rescue request because of the low likelihood of finding the coin after 1,827 days of being lost.

To make matters worse the State Park where this cache was placed was closed two years or more ago due to budgetary problems, so we weren’t sure whether we would be trespassing if we looked for it.

But, we love a challenge and this was a good one, so we left home 50 miles away under gray skies, wind and rain. One we arrived, access was not quite as close as we expected due to gating of the road leading to the cache, and it was raining, Nevertheless we bundled up and brought out the umbrellas and our special geocaching tool.

It was a quick hike, easy access to the old geozone but would anything be left of the old cache ? Rox was the first to notice a small, colorful decoration on the ground , below that a moldy wad of paper that might once have been a log. Nearby was a tiny toy car, so we had found the containerless cache but there was no geocoin on the ground.

So out came our special geotool the “Coinmaster 4900D“, our old metal detector. Progressively sweeping the surrounding area we found 1 to 3 inches underground
1)Several wads of aluminum foil.
2)A nail
3)A spike, probably left over from the railroad days.
4)The top of an old can.
and then…
5)China Town Geocoin. Buried in the sandy soil, its paperwork soggy and moldy, but the coin itself looked fine.

Major celebrating ensued.

And now we shall re-prepare the appropriate paperwork and try to get this nice but long-slumbering coin back on its way.

Doc&Rox

*unfortunately we did not keep the number of days that a TB was stuck in a cache before it was rescued so far. But we have never heard of any longer time than 5 years + 1 day so we will assume this IS THE CURRENT WORLD RECORD.

distance fair
In principal just as the normal distance race. But here, we only consider the first ‘placed’ log of every cacher. This prevents that cachers keeping trackables, dipping them in every cache and helping them to get high mileage. In case there is more than one log on the first day we will consider the one with the highes mileage on that day.

long jump
Also quite like the normal distance race. But if one cacher moves a TB several time we consider only the log with the highest mileage – the longest jump.
This prevents cachers keeping trackables, dipping them in every cache and helping them to get high mileage.

You can find a description of all race rules here.

A big “thank you” goes to team ‘WantedDeadOrAlive‘ for support and testing of the new rules.

In case of isses or questions please leave feedback in the blog comments or contact us at webmaster@tb-run.com.

it speaks about the fact that tb-rescue/tb-run will not continue to support cache-contest.com

But I was completely snowed under due to private and business projects.
Originally I planned to use thewinter season to implement many ideas for tb-run and tb-rescue and be able to proudly remove the “beta” label from both sites.

But what can I say… I did not and still both sites are running with almost no issues.

I have the impression that 90% of all “my TB is stuck” cases are covered by the current tb-rescue technology.
The service has become well established and seems to be stable.

We receive lots of new rescue requests every day and our server sends out thousands of mails every day to potential rescue teams in the relevant areas. Seems like the western caching civilization is mostly covered – see Map.

The banner ads from Groundspeak on gc.com do supply us with new interested geocachers every day and we have exceeded 8000 registered users.

What else is on the todo list?

Well, first of all we have the topics that are most aksed:

• Watch more than one area
• Have nice statistics about the races

• And my main issue that tb-rescue does not handle some processes too well.
  One example is: if a TB owner does not mark his trackable as missing, even though a rescue team has confirmed that its gone -  (sigh!).
  In this case, the rescuer does not get a rescue point and the request is kept open forever.

Ahh.. the „most Wanted“ functionality is still the creation of rescue request for TBs that are stuck at another CACHER.  .

For this, please also read “Rescue a TB that is stuck at another geocacher“.

Well.. Other than that… The situation at tb-run.com is even better: Everything is working fine.
By now we have more than 500 races with over 3800 Trackables in total.

We dont have a standstill, improvements are just postponed

Thats it for now, Yours sincerly, Sascha
(currently crossing the atlantic during a flight… having some time to let my mind wander….)

The site will be fully working during the move.

You will just recognize that the domain ends with “trackable.de” during a temporary time.
Also all links are supposed to remain working.
In case of any issues please leave a comment here or contact us at webmaster@tb-run.com

As soon as the move is completed in 1-2 weeks also trackable.de will disappear.

you can request to update your TB Image on tb-run.com.
Once clicked, during the next daily replication run we will retrieve the latest image of your TB from geoaching.com.

Northing really special but one more step towards leaving the Beta version.

The development team has found out that the mileage calculation of trackables had several errors. Thus, the mileage calculation was sometimes wrong.
With the upcoming update the mileage calc will be much more accurate.

As a result for many trackables the mileage will change.

Cheers,
Sascha

You can find all details of this spectacular misson on their websitehttp://sonntagsrudel.amshove.net/indexE.html.

We think this a pretty cool accomplishment that (even though it was not a activity that was initiated by tb-rescue.com) deserves honor.
In order to thank the team, we have set up all successful rescues as records on tb-rescue.com

A big THANK YOU to the Caching team “Sonntagsrudel”.

Here you find all rescues trackables of this cool mission:

Acimes 1st Coin
Letterboxing in Deutschland
Saarland Geocoin 2007
Frozboz’ Happy Caching – Black Cat Geocoin
Euro 5th Anniversary Geocoin
Birthday Geocoin 2009
Die Schwedenflagge – The Swedish Flag
Dragon Spinner Geocoin
Happy Caching – Ladybird Geocoin
Come Together – Rad
GN_worldwide!_S16_002_Germany2007
Reindeer Geocoin
Geocacher?s Star 2009 Geocoin
Screw 2007 Geocoin
Denmark Geocoin
The Lord of the Caches – Earth Geocoin
Pepper’s Love
Belted Kingfisher Geocoin
SNSpencer?s Cache Movers Geocoin #1
mahos geotaler 3
Robby Schlappohr
Das fliegende Auge
Army Geocoin
NoobNaders RoG – Harz- Geocoin
Proving Trail Geocoin
Excalibur Geocoin
Red Handed Micro
2102 on Tour
“Amaigbo, Nigeria” Unite for Diabetes Travel Bug
“Thun, Switzerland” Unite for Diabetes Travel Bug
Phoebe the Globetrotter
Helicopter Herrold
The Flying Dutchman
Goofy
Alaska Bear Paw TB
Schwitzwasserleitung
happy
The flower bug
Silferme’s WorldRoller #2
Team Die Goldbären – Tebby
Liam’s Lego Plane
Janis the Bat
Where’s My Car?!?
Go GOLEO, go !!!
Travel Bug Vista
Dalarna horse
Vans World Tour
RANGE
Travel Bug Cool Chicken
Lupus54 No.: 06
Bob
Bailey Bee
Balancing Act
Svenne Svensson
Halve a twin (Yoni)
ROBOTICA 2
UV-Men Baron von Zwick
Freizeitpark TB
Signature Item Collector

After groundspeaks last update to gc.com the mileage bug should be fixed.
In case you still experience issues please try a “Recalculate Distance” first.
If there are still logs on gc.com where the milease is missing please let us know the public TB code.

We will now start the update process that updates all races. Should be done by friday morning (2.July) latest.

———-

Hi all,

since groundspeak did the last update to geocaching.com at the biginning of june 2010 we receive quite some complaints from you, asking why tb-run.com shows the wrong mileage for a TB.

Here comes the short answer

Due to a bug on geocaching.com we are missing the mileage of the last log.
As soon as a new “placed” log is added to this TB, the previous one is considered as well.

In detail:

tb-run.com does not simply use the total mileage that gc.com shows for a trackable. This is sometimes not correct but even more important:  This number has all mileage – but we must only read the mileage that occured during the race of the TB (from start to end date of the particular race).

Thus, we collect the individual mileage that is shown behin every “placed” log – see screenshot:

And exactly here the bug on geocaching.com hits us.

For some reasons, in some cases the last log on gc.com does not show any mileage.
gc.com does consider it in the total mileage figure and it is also shown in the Google Maps Vie (“View Map”).

However, on the TB overview page that tb-run.com alway the mileage of the last “placed” log is missing- see Screenshot:

Our experience is, that also a “Recalculate Distance” does not solve this issue.

But:

As soon as a new “placed” log is added, the milease of this (now last but one) log show up. Again,  the mileage of the new log is missing (and so on).

We have informed Groundspeak about the issue and they have promised to work on fixing this.
Until then, we have to live with the problem.