LIST OF TRAVEL BUGS
There are two tables below that list shellbadger TBs that visited a new statoid at least once. The first one lists the bugs in order of their catalog numbers, lowest to highest. The catalog numbers are assigned first by the date of release then in order of the unique ID number. The numbers are very close to the sequence in which they were released.
The second table has the same information as the first, but is listed in alphabetical order of the name of the TB. These tables are the only ones in this report that display the Names of the travel bugs, the Release Date, the Release Location, the Miles traveled on the closing date, the number of Drops achieved by the closing date and the Status of the bug.
The values for the miles traveled are those observed within a few days of 31 December 2016. The mileage for catalog number 66 was estimated. Because mileage can incease with each new visit to a cache, the values reported should not be taken as absolute. However, in no instance will a current value be less than the reported value. The status of a bug is noted as either in a Cache, in the Hands of a cacher, Missing or Retired. The retired bug was taken out of circulation when it met its goal.
In the status column, the number appended to either cache, hands, missing or retired is the last two digits of year of the last retrieval or drop. For example Hands 14 means at the last log the bug has been in a cacher's hands since 2014. The practice of discovering trackables from lists passed around at events is so prevalent that I do not acknowledge discovery dates for this purpose. A bug is declared missing if determined, by some means, the bug is not in the cache into which it was logged.
The total new statoids for each of the release years is as follows: 2010, 61; 2011, 51; 2012, 22; 2013, 42; 2014, 14; 2105, 4; 2016,1. It should be no surprise that the earliest release-years captured the most new statoids, particularly in view of the proximity to the statoids of the US and Canada. The increase in 2013 is a result of bugs being sent for release at a Mega in Belgium
Of the 195 TBs under study, 138 (70.7%) were released in the owner's core caching area in the Panhandle-South Plains of Texas (see the image below). To provide perspective, the map was purposely expanded to include Amarillo, Oklahoma City, Dallas/Fort Worth, Midland/Odessa and the New Mexico/Texas state boundary. The black dots are currently active caches, the red dots are archived caches, but sites where TBs were once released. The writer lives in Lubbock, on the west side of the core area.
There are two tables below that list shellbadger TBs that visited a new statoid at least once. The first one lists the bugs in order of their catalog numbers, lowest to highest. The catalog numbers are assigned first by the date of release then in order of the unique ID number. The numbers are very close to the sequence in which they were released.
The second table has the same information as the first, but is listed in alphabetical order of the name of the TB. These tables are the only ones in this report that display the Names of the travel bugs, the Release Date, the Release Location, the Miles traveled on the closing date, the number of Drops achieved by the closing date and the Status of the bug.
The values for the miles traveled are those observed within a few days of 31 December 2016. The mileage for catalog number 66 was estimated. Because mileage can incease with each new visit to a cache, the values reported should not be taken as absolute. However, in no instance will a current value be less than the reported value. The status of a bug is noted as either in a Cache, in the Hands of a cacher, Missing or Retired. The retired bug was taken out of circulation when it met its goal.
In the status column, the number appended to either cache, hands, missing or retired is the last two digits of year of the last retrieval or drop. For example Hands 14 means at the last log the bug has been in a cacher's hands since 2014. The practice of discovering trackables from lists passed around at events is so prevalent that I do not acknowledge discovery dates for this purpose. A bug is declared missing if determined, by some means, the bug is not in the cache into which it was logged.
The total new statoids for each of the release years is as follows: 2010, 61; 2011, 51; 2012, 22; 2013, 42; 2014, 14; 2105, 4; 2016,1. It should be no surprise that the earliest release-years captured the most new statoids, particularly in view of the proximity to the statoids of the US and Canada. The increase in 2013 is a result of bugs being sent for release at a Mega in Belgium
Of the 195 TBs under study, 138 (70.7%) were released in the owner's core caching area in the Panhandle-South Plains of Texas (see the image below). To provide perspective, the map was purposely expanded to include Amarillo, Oklahoma City, Dallas/Fort Worth, Midland/Odessa and the New Mexico/Texas state boundary. The black dots are currently active caches, the red dots are archived caches, but sites where TBs were once released. The writer lives in Lubbock, on the west side of the core area.
The owner released another 23 travel bugs in his travels around the US. Of the 34 (17.4%) travel bugs released abroad, 25 were among the collection sent to a cacher in Bruges, Belgium. Another cacher at that event is responsible for the release in Australia. A handful of bugs were sent to a cacher in England in 2015, which resulted in the record there and the Isle of Man. The other seven TBs were released by the owner, during his own travels in Europe.
The average miles travel by this collection of travelers was 17,827 (range 940-84,353). The average number of drops made by the bugs was 18 (range 0-56). The number of drops equates to the number of cachers who have moved a particular bug. Interestingly, there are three travel bugs listed (007, 1065, 1119) that have had their original appended item replaced, and all have garnered more than 25 drops. There are obviously more than a few conscientious cachers out there.
A summary of the status of these TBs follows. A total of 28 (14.4%) were placed in a cache 2016 and were not logged out by the end of the year. There are 86 TBs (44%) in the hands of cachers, 42 of which have been held from before the end of 2015, some even back to 2010. A total of 80 (41%) bugs have been marked missing. One travel bugs has been retired.
TABLE 1. List of TBs by Catalog Numbers.
The average miles travel by this collection of travelers was 17,827 (range 940-84,353). The average number of drops made by the bugs was 18 (range 0-56). The number of drops equates to the number of cachers who have moved a particular bug. Interestingly, there are three travel bugs listed (007, 1065, 1119) that have had their original appended item replaced, and all have garnered more than 25 drops. There are obviously more than a few conscientious cachers out there.
A summary of the status of these TBs follows. A total of 28 (14.4%) were placed in a cache 2016 and were not logged out by the end of the year. There are 86 TBs (44%) in the hands of cachers, 42 of which have been held from before the end of 2015, some even back to 2010. A total of 80 (41%) bugs have been marked missing. One travel bugs has been retired.
TABLE 1. List of TBs by Catalog Numbers.
TABLE 2. List of TBs by Name.