[Az-Geocaching] Two travel bugs at event cache not yet accounted for

Rob Brinkerhoff listserv@azgeocaching.com
Tue, 16 Dec 2003 21:13:38 -0700


This is a multi-part message in MIME format.

------=_NextPart_000_000C_01C3C419.7924FEC0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Ken,
Looks to me like Herbert, Your Schroom Buddy was grabbed by
a certain cacher and taken home and is still in that cachers
possession. The problem is another cacher decided to log the
TB (for what ever reason?) and then replaced it back in the
cache, thus making it look like the TB is stranded High and
dry in the cache...just a theory of course. As for Mi-Co-To
Campfire Club your guess is a good as mine.

One thing that I noted with allot of the TBs that exchanged
hands at this event is several teams logged finds for TBs
(i.e. write down tracking numbers and logging that the TB
was "seen" thus jacking up ones TB count) but did not move
the TB to a different location. Odd behavior if you ask me.

The only metric that counts is D+T...;-)

Rob (Wily Javelina)

  ----- Original Message -----
  From: Ken Akerman
  To: Geocaching.com Automated Bot
  Sent: Tuesday, December 16, 2003 1:23 PM
  Subject: [Az-Geocaching] Two travel bugs at event cache
not yet accounted for


  Hello Geocachers,

  2003 Tucson Geocaching Extravaganza has now been archived.
There are two travel bugs that were brought to this event
but haven't been logged by the geocachers who took them.
These include a travel bug that I own, Mi-Co-To Campfire
Club, and a travel bug that I found in Phoenix a week
earlier, Herbert, Your Schroom Buddy.

  If you have either of these travel bugs, please go to the
respective travel bug page and enter the six-digit number on
the tag to put it in you inventory before putting it in
another cache.  If you find either of those travel bugs in
another cache without it being logged into it, please log
the travel bug into the cache you found it in before
claiming possession of it.  Thank you.

  Ken Akerman (a.k.a. Highpointer)
    Greetings from Geocaching.com.

    This is an automated message letting you know that a
cache on your watch list has been archived. You can read the
message by visiting the following link


http://www.geocaching.com/seek/cache_details.asp?ID=96757

    This will take you to the cache page. If you would like
to modify your cache list, please visit www.geocaching.com.

    Cheers,
    Geocaching.com Team

------=_NextPart_000_000C_01C3C419.7924FEC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DVerdana size=3D2>Ken,</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2>Looks to me like <A=20
href=3D"http://www.geocaching.com/track/track_detail.asp?ID=3D28961"><FON=
T=20
face=3D"Times New Roman" size=3D3>Herbert, Your Schroom =
Buddy</FONT></A>&nbsp;was=20
grabbed by a certain cacher and taken home and is still in that cachers=20
possession. The problem is another cacher decided to log the TB (for =
what ever=20
reason?) and then replaced it back in the cache, thus making it look =
like the TB=20
is stranded High and dry in the cache...just a theory of course. As for =
<A=20
href=3D"http://www.geocaching.com/track/track_detail.asp?ID=3D53838"><FON=
T=20
face=3D"Times New Roman" size=3D3>Mi-Co-To Campfire =
Club</FONT></A>&nbsp;your guess=20
is a good as mine.</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DVerdana size=3D2>One thing that I noted with allot of =
the TBs that=20
exchanged hands at this event is several teams logged finds for TBs =
(i.e. write=20
down tracking numbers and logging that the TB was "seen" thus jacking up =
ones TB=20
count) but did not move the TB to a different location. Odd behavior if =
you ask=20
me. </FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DVerdana size=3D2>The only metric that counts is=20
D+T...;-)</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DVerdana size=3D2>Rob (Wily Javelina)</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dken@highpointer.com href=3D"mailto:ken@highpointer.com">Ken =
Akerman</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dlistserv@azgeocaching.com=20
  href=3D"mailto:listserv@azgeocaching.com">Geocaching.com Automated =
Bot</A>=20
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, December 16, =
2003 1:23=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Az-Geocaching] Two =
travel bugs=20
  at event cache not yet accounted for</DIV>
  <DIV><BR></DIV>
  <DIV>Hello Geocachers,</DIV>
  <DIV>&nbsp;</DIV>
  <DIV><A =
href=3D"http://www.geocaching.com/seek/cache_details.aspx?ID=3D96757">200=
3=20
  Tucson Geocaching Extravaganza</A> has now been archived.&nbsp; There =
are two=20
  travel bugs that were brought to this event but haven't been logged by =
the=20
  geocachers who took them.&nbsp; These include a travel bug that I own, =
<A=20
  =
href=3D"http://www.geocaching.com/track/track_detail.asp?ID=3D53838">Mi-C=
o-To=20
  Campfire Club</A>, and a travel bug that I found in Phoenix a week =
earlier, <A=20
  =
href=3D"http://www.geocaching.com/track/track_detail.asp?ID=3D28961">Herb=
ert, Your=20
  Schroom Buddy</A>.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>If you have either of these travel bugs, please go to the =
respective=20
  travel bug page and enter the six-digit number on the tag to put it in =
you=20
  inventory before putting it in another cache.&nbsp; If you find either =
of=20
  those travel bugs in another cache without it being logged into it, =
please log=20
  the travel bug into the cache you found it in before claiming =
possession of=20
  it.&nbsp; Thank you.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV><STRONG>Ken Akerman</STRONG> (a.k.a.=20
  <STRONG><EM>Highpointer</EM></STRONG>)</DIV>
  <BLOCKQUOTE class=3Dreplbq=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px =
solid">Greetings=20
    from Geocaching.com.<BR><BR>This is an automated message letting you =
know=20
    that a cache on your watch list has been archived. You can read the =
message=20
    by visiting the following link<BR><BR><A=20
    =
href=3D"http://www.geocaching.com/seek/cache_details.aspx?ID=3D96757">htt=
p://www.geocaching.com/seek/cache_details.asp?ID=3D96757<BR></A><BR>This =

    will take you to the cache page. If you would like to modify your =
cache=20
    list, please visit =
www.geocaching.com.<BR><BR>Cheers,<BR>Geocaching.com=20
  Team</BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000C_01C3C419.7924FEC0--