Why is the mileage of my race TB incorrect?

Hi,

sometimes it happens that a race participant complains about the ranking list not being correct. In this case please, take a look at the following points.
If there are still things unclear after review, we are happy to answer your message at webmaster@tb-run.com.

The following points are valid for all races that are about “who makes the most mileage” –  “distance“, “distance fair” as well as “long jump“:

  1. Only the mileage after start of the race is considered.
  2. In case a TB was added to the race after the race started, only the mileage is valued from the date, the TB was added.
    In case you want to adjust this please, contact the race-organizer of your race. A simple email from the race-organizer is enough and we will adjust this manually on request.
  3. At the bottom of the race list, you will find the date of the “last complete update” from geocaching.com.
    In case this is old, you will usually see the next update happening within 24 hours.
  4. As we are not just considering the total mileage but only the mileage since race start (see 1. and 2.) the value “total mileage” from geocaching.com is not relevant (see Screenshot).
    total-log_en
  5. Instead of considering the total mileage tb-run reads the single logs mileages from the log history (see screenshot).
    single-logs_deen

    In case geocaching.com does not show the correct mileage here, it sometimes helps to run a “recalculate distance” from the detail page of your trackable on geocaching.com (see screenshot).
    If this does not help there is unfortunately nothing we can do about it from our side.
    recalc-distance_en

The following point is valid in addition for “distance fair” and “long jump“:

  • Here, multiple logs from the same “Mover” will be excluded on purpose. You can find the details in the rule section.
    This works pretty well and reliable.
    In case you are under the impression that something is not valued correctly, please contact us.

With race type “race to cache” we calculate the distance from the current to the target cache. In the following cases it can happen that the distance is temporary not calculated correctly:

  • The TB was just added to the race – tb-run.com will update the data from geocaching.com once per day.
  • There is no ‘placed’ log for this TB yet. So we cannot find out where the TB is located..
  • The last ‘placed’ log was in a archived cache.
  • The last ‘placed’ log was in a ‘Premium Member Only’ Cache.

In all these cases, the situation remains only temporary and the correct position is calculated once the trackable moves to the next cache,

In case you still have questions please contact us with providing the race name as well as the (public) TB case at webmaster@tb-run.com.

Pathtags shjpped accidentially to germany

This article is only relevant for germany.

We have produced a first amount of tb-rescue pathtags which were supposed to b offered via pathtags.com.

Now accidentially they were shipped to my home in germany – so we are doing a “garage sale” of them in germany.

New production is in progress and they will soon be offered also in the US.

tb-rescue World Record: Coin rescued after 5 years and 1 day

From time to time we receive stories from either the owner a trackable that got rescued or somebody who had a special experience while being on a rescue mission.
This one is the new world record*: The Coin was stuck in a cache for 5 years before “B4alltime” got the notification from tb-rescue.com  and went to save the Coin. But read the whole story (taken from the original with authors permission):

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.

two new race rulesets on tb-run.com

We just activated two new race types on tb-run.com:

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.

 

Geocaching Travel Bug® Races