Search the Community

I got FTF once on one 200+ miles off. The "CO" was a bit off on his North coords... The name is what got me to notice (why I really missed the "newest in..." on our profiles), one of my favorite fly-fishing areas, and the description was on-the-money too. Turned out to be where I thought, on Park Service property, and after I notified the Reviewer of the error and it's location, it got archived. I was first and last to find.

I am having trouble creating lists, where I never had difficulty before. Even though I add as many as 800-950 caches to a particular list, the list I then create only contains 50, 100, or 200 caches, the number coinciding to the "Show 50", "Show 100", or "Show 200", options given on the drop-down menu that may be open when I am creating the list. Have I unknowingly set up some sort of limit on the lists I am trying to create, all of which exceed 200? Thank you for any assistance you can provide.

The only touch screen gpsr in production is the Garmin Montana series, quite large and quite pricey. The Oregons, Dakotas, and Etrex 25, 35 all have been discontinued. Garmin I guess decided there is no market for touchscreeen anymore now that most geocachers use a cellphone. All units made in the past 12 years plus have paperless geocaching. That said, if you can find a good used Oregon 7xx series, that will work perfectly for geocaching if you must have touchscreen. Now if you don't need touchscreen and want a new GPSr unit, probably the Garmin GPSMap series 64s is all you need. There are 65, 66, 67 that are more pricey . The Garmin etrex 22x is still being sold if you need a budget GPSr that is under $200.

> I find myself geocaching by phone these days I think you've hit the market summary spot on. They're in a tough spot. Look at their product line and you can see a hole and some rollup opportunities. Etrex: small and large. $100 and $200 are good price points. GPSMap: separate product entries at $300, $350, and $400 - each with submodels of different sensors, mapping options is too crowded. Clean house. A BME280 and a HMC5883L combined are under a buck in quantity. Does a camera make sense in these at all, especially at $100 when the sensors are < $3. Volumes for the multi-SV chipsets and antennas have driven the price to nearly the same as the GPS-only solutions. Printing and stocking different SKUs with training sales and support people (bwaaahahaha ) costs more than that. Fold all the 64, 65, and 66 devices together into one model. Remove Topo as a SKU and make it a download. Rhino and Montana are niche products at best. I just can't imagine that people are buying $800 Montana 750is. Make Spot a separate unit that connects to the phone for a keyboard and location. Just don't even put it in the GPS. Just like the camera, that's on a different upgrade cadence than the core GPS tech. New volume lineup: eTtex small $100 and large $200. GPSMap touch or dpad at $350. (Ask if we really need three different UX's with click-stick, dpad, and touch at all...) Hire a team to fix the problems that have been in these things for >10 years. The self-destructing buttons, switches, and rubber band problems are just not funny any more. Hire a usability engineer to count the number of button presses to street/foot navigate for a day of power geocaching, then go fix the UI. Read AC's list of long-standing bugs in the firmware and actually fix them. Crashing on certain PQs has been with us since Colorado. Make a legit sustaining engineering group to fix and support these things Last time I picked up a eTrex, the performance was just torture. When we had 8Mhz Dragonballs, I understood why keypresses lagged by a second. Modern multi-core RISC-V and ARM parts with a good peripheral set and good power management are, again, about a buck in quantity. Quit using parts that just make the hardware so laggy to save pennies. But you've exactly called out the elephant in the room. All, but particularly the entry level devices, have to be feeling the pressure from phones. As long as your touch screen device is $600, it's really hard to justify one instead of the touch screen you already own. That really leaves their island between those two points: hyper rugged (compared to a phone) hardware. They'll never be able to compete with the volume economies of Samsung or Apple - heck, probably not even Oppo or OnePlus. I think there's space for them to survive with geocaching-capable devices inside the larger "outdoor" class of devices, but I suspect the $500 touch screen Oregons are so indistinguishable in the minds of consumers from a phone (that the already have) in an otterbox that we just won't be seeing more of those. Instead of trying to shove everything into every device, consider your handheld "power geocacher" unit using BT to pair with your Drive so the cache you just marked found disappears from the map and your next (auto-routed) GOTO is the navigation target. Quit trying to solve driving directions on a 2.4" screen and an AA battery budget for some users. They used to have 20 Nuvis and then mobile phones happened. Now just have models at 5", 6", 7", and 8", I think it's time for some tough love in their outdoor line to clean the models up and lock them down into a sustainable maintenance mode product line. In that product line, like their fitness devices, external competition forced them to clean up. In handheld GPS, their hand isn't forced, but they can't coast with this product line forever. If I were King, things would be a lot different here... I'm just not sure we need an Oregon 800 at $500.

Bill & All, 2009 was with a Nikon D40, manual 55-200 zoom. Upgraded in 2013 to a Canon Power Shot A-1200 (for birds ). 2015 & 16 was with a Canon SX50 HS. On a tripod, with a remote shutter release, for the long shot. And a handheld Canon SX70 HS in 2020. Raised on a ranch in Montana, I tend to 'chat' with locals (drives one of my birding companions crazy). Got the 2016 location info from a rancher working cattle after the 2015 observation, and checked it out on the way to camp at the BLM Moorhead. Can't resist putting a history link up for that location - there are PID's associated MEL. https://www.powderriverexaminer.com/story/2022/06/30/news/moorhead-a-struggle-by-a-dam-site/3796.html

Talking about bugs: I think I just found another one, which is not very important/annoying, but I thought I should mention it. I search for the "Nearest Waymarks" of any WM. If I click on any profile name in the results list, it leads to f.e. https://Waymarking.com/users/profile.aspx?f=1&guid=d4c8eca0-ea01-4d21-bfdb-3c4f18d35dac&lat=45.1612&lon=10.798267&t=6 which includes the coordinates of my prior search. So far, no problem, but: If I then open the category grid, and click on some of the categories that are already covered, there seem to be no WMs to find, if the coordinates that are still in the URL are too far from where the posted/visited WM of that category is. In my example just click on the very first category icon for "Bloggers" on https://Waymarking.com/users/profile.aspx?f=1&guid=d4c8eca0-ea01-4d21-bfdb-3c4f18d35dac&lat=45.1612&lon=10.798267&t=6&full=False&mypage=3. Also, if I open the "waymark lists" tab in the profile page, the coordinates are still in the URL and clicking on any of the numbers will either give all the waymarks, part of them or nothing at all. Example: The 200+ WMs of the category "Austrian and Swiss National Heritage Sites" on https://Waymarking.com/users/profile.aspx?f=1&guid=d4c8eca0-ea01-4d21-bfdb-3c4f18d35dac&lat=45.1612&lon=10.798267&t=6&full=False&mypage=2 Like I said: Not a big problem, but maybe easy to get rid of.

Right: https://www.geocaching.com/play/results/?ct=6%2C1304%2C3653%2C3774%2C4738&st=GCA7JTN+-+Oratorio+di+Sant'Erasmo&ot=geocache&r=200&asc=true&sort=distance

Hi"JS" from Twitter goGeocaching Account, here our trace data. Hope you can do something with it and the problem will be solved soon. Because sometimes it´s so slow, one can´t do anything with the website or the API. Location is: Dresden, Germany ISP: T-Online traceroute to geocaching.com (63.251.163.200), 64 hops max, 72 byte packets 1 XXXXXXXXX(192.XXXXXXXXX) 3.376 ms 3.894 ms 2.037 ms 2 87.186.224.218 (87.186.224.218) 9.161 ms 8.740 ms 9.796 ms 3 87.190.191.134 (87.190.191.134) 8.571 ms 9.676 ms 8.832 ms 4 f-ed4-i.f.de.net.dtag.de (62.154.14.130) 18.317 ms 18.280 ms 17.100 ms 5 80.157.128.230 (80.157.128.230) 18.090 ms 18.631 ms 18.403 ms 6 ae-6.r20.frnkge04.de.bb.gin.ntt.net (129.250.6.248) 18.610 ms ae-1.r21.frnkge03.de.bb.gin.ntt.net (129.250.6.216) 24.456 ms ae-6.r20.frnkge04.de.bb.gin.ntt.net (129.250.6.248) 18.608 ms 7 ae-3.r23.nycmny01.us.bb.gin.ntt.net (129.250.3.180) 147.174 ms 147.387 ms ae-7.r22.asbnva02.us.bb.gin.ntt.net (129.250.3.20) 133.801 ms 8 ae-0.r22.nycmny01.us.bb.gin.ntt.net (129.250.3.72) 127.891 ms 130.579 ms 123.428 ms 9 ae-5.r21.sttlwa01.us.bb.gin.ntt.net (129.250.4.182) 508.142 ms 247.352 ms ae-1.r21.sttlwa01.us.bb.gin.ntt.net (129.250.4.13) 235.995 ms 10 ae-2.r04.sttlwa01.us.bb.gin.ntt.net (129.250.5.45) 255.022 ms 259.749 ms 252.401 ms 11 * ae-0.internap.sttlwa01.us.bb.gin.ntt.net (129.250.201.18) 376.347 ms 223.212 ms 12 border8.po1-40g-bbnet1.sef.pnap.net (63.251.160.18) 354.876 ms 648.917 ms 506.138 ms 13 63.251.163.200 (63.251.163.200) 511.959 ms 509.374 ms 512.301 ms PING geocaching.com (63.251.163.200): 56 data bytes 64 bytes from 63.251.163.200: icmp_seq=0 ttl=245 time=231.315 ms 64 bytes from 63.251.163.200: icmp_seq=1 ttl=245 time=218.284 ms 64 bytes from 63.251.163.200: icmp_seq=2 ttl=245 time=223.224 ms 64 bytes from 63.251.163.200: icmp_seq=3 ttl=245 time=226.252 ms 64 bytes from 63.251.163.200: icmp_seq=4 ttl=245 time=225.311 ms 64 bytes from 63.251.163.200: icmp_seq=5 ttl=245 time=221.818 ms 64 bytes from 63.251.163.200: icmp_seq=6 ttl=245 time=217.292 ms 64 bytes from 63.251.163.200: icmp_seq=7 ttl=245 time=200.838 ms 64 bytes from 63.251.163.200: icmp_seq=8 ttl=245 time=221.414 ms 64 bytes from 63.251.163.200: icmp_seq=9 ttl=245 time=191.583 ms --- geocaching.com ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 191.583/217.733/231.315/11.596 ms PING geocaching.com (63.251.163.200): 56 data bytes 64 bytes from 63.251.163.200: icmp_seq=0 ttl=245 time=378.121 ms 64 bytes from 63.251.163.200: icmp_seq=1 ttl=245 time=452.927 ms 64 bytes from 63.251.163.200: icmp_seq=2 ttl=245 time=398.323 ms 64 bytes from 63.251.163.200: icmp_seq=3 ttl=245 time=353.585 ms 64 bytes from 63.251.163.200: icmp_seq=4 ttl=245 time=327.212 ms 64 bytes from 63.251.163.200: icmp_seq=5 ttl=245 time=379.283 ms 64 bytes from 63.251.163.200: icmp_seq=6 ttl=245 time=437.034 ms 64 bytes from 63.251.163.200: icmp_seq=7 ttl=245 time=371.503 ms 64 bytes from 63.251.163.200: icmp_seq=8 ttl=245 time=371.667 ms 64 bytes from 63.251.163.200: icmp_seq=9 ttl=245 time=386.024 ms --- geocaching.com ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 327.212/385.568/452.927/35.019 ms

As I get older I notice three major changes in my caching activities: fewer long high mile hiking (and driving) days, much more cache selectivity, and more time spent placing and maintaining caches than in the past. The first change is partly do to aging and partly due to "clearing out the radius" of nearby caches. I'd much rather hike than drive and as the distance to the nearest "unfound good caches" increases, I'm less willing to drive an hour there and back. About five years into the game, I pretty much lost interest in micros within 200 feet of parking and since they are about half of all placements, my field of interest shrank. Most folks place single stage caches, but since I like to hike around the woods, once I started placing caches, I placed mostly multis that have five or six stages and involve a walk of a mile ot two (on average). Multis are exponentially harder to find, place and maintain than single stage caches but way more fun to my mind, and since they are closer to home the ratio of drive time to woods time shifts the right way for me. Plus, I know I'm going to enjoy the area and the cache since I only place stuff I'd like to find. edexter

Hey there, new to the forum but not to geocaching or using GPS's...please forgive for what seems to be a general forum faux-pas in discussing,asking or otherwise talking about the horrible attributes oh the Magellan Triton 200,but I have simple needs and just want it to work when it should.I'm almost resigned to the fact that the availability of anything that will work on the unit is slim to none but possibly a member on here can put this to rest for good or offer a solution where I might obtain a working Topo map for the Triton. Thanks so much in advance!

With lots of experience traveling and hiking in the deserts I have learned to not go anywhere you haven’t recently been in the daylight so one evening I stopped caching and just drove along the ET highway and checked out the area some miles ahead and marked that spot on my GPS. My last find was already on my GPS so no need to enter that. The next morning I left Rachel, NV before daylight and headed out caching between those marks. When I got to the last mark I stopped and drank coffee until the sun came up and started again. No faking the finds, I have witnessed a lot of that, I stamped and/or replaced each cache. In the late evening I drove ahead once again and marked that spot so I could find those caches in the dark until I got to that mark. *When caching alone, driving a hybrid car sure helps because you never need to turn it off nor worry about running out of gas.* That is how I did it, now to what I did; [Total for that day] “961 caches in one day on 03/11/2012” Why I did it; Because even though I was an active hiker and outdoorsman I was feeling old (at age 65) and wanted to push myself. Plus it was just pure fun on the run under the sun. Highlight of the day; Was the sun rolling across the desert like someone rolling up a dark curtain *plus* the stallion standing there watching me within maybe 200 feet when the sun came up.

In fact, they posted their first Needs Maintenance log when they had less than 200 finds! 😱😱😱 How naughty. I'd better flag it for Needs Delete. I'm not saying Groundspeak asked me to be a forum moderator because of my psychic powers, but...

In fact, they posted their first Needs Maintenance log when they had less than 200 finds! 😱😱😱 How naughty. I'd better flag it for Needs Delete.

I have a Magellan Explorist 200 and would like to enter individual caches into it by entering each caches coordinates as found on Geocaching.com. How do I enter the coordinates as a POI? Or is there some other way to enter geocaches onto the Explorist 200? Thanks!

It's nice to see new countries being introduced. I am still missing New Caledonia & PNG, but they might be coming. They can't all be done at once. However, it seems I now only have 32 souvenirs, but it's the important ones, so not a big problem for me. Fortunately though I got enough for a challenge that needed 200 souvenirs to log it before this.

Routenverfolgung zu www.geocaching.com [63.251.163.200] über maximal 30 Hops: 1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1] 2 * * * Zeitüberschreitung der Anforderung. 3 8 ms 8 ms 8 ms 92.79.251.56 4 9 ms 8 ms 8 ms 88.79.22.104 5 11 ms 10 ms 10 ms 92.79.214.236 6 11 ms 11 ms 11 ms 145.254.2.199 7 11 ms 11 ms 11 ms ae38-100-xcr1.dus.cw.net [195.2.18.189] 8 14 ms 14 ms 14 ms ae23.pcr1.fis.cw.net [195.2.20.178] 9 15 ms 15 ms 15 ms be3001.agr41.fra03.atlas.cogentco.com [130.117.14.73] 10 15 ms 15 ms 16 ms be3187.ccr42.fra03.atlas.cogentco.com [130.117.1.118] 11 18 ms 19 ms 18 ms be2814.ccr42.ams03.atlas.cogentco.com [130.117.0.141] 12 110 ms 109 ms 109 ms be12488.ccr42.lon13.atlas.cogentco.com [130.117.51.41] 13 111 ms 110 ms 111 ms be2490.ccr42.jfk02.atlas.cogentco.com [154.54.42.85] 14 110 ms 109 ms 109 ms be2890.ccr22.cle04.atlas.cogentco.com [154.54.82.245] 15 110 ms 109 ms 110 ms be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.129] 16 122 ms 121 ms 121 ms be2832.ccr22.mci01.atlas.cogentco.com [154.54.44.169] 17 159 ms 159 ms 159 ms be3036.ccr22.den01.atlas.cogentco.com [154.54.31.89] 18 159 ms 159 ms 159 ms be3038.ccr32.slc01.atlas.cogentco.com [154.54.42.97] 19 171 ms 170 ms 170 ms be2029.ccr22.sea02.atlas.cogentco.com [154.54.86.110] 20 171 ms 171 ms 171 ms be3321.rcr21.sea03.atlas.cogentco.com [154.54.42.206] 21 172 ms 172 ms 171 ms Internap-Network-Services.demarc.cogentco.com [38.104.124.82] 22 172 ms 171 ms 171 ms border1.ae1-bbnet1.sef.pnap.net [63.251.160.4] 23 173 ms 173 ms 173 ms edge1.ae1-edgenet.sef.pnap.net [64.94.137.18] 24 171 ms 170 ms 171 ms www.geocaching.com [63.251.163.200] Ablaufverfolgung beendet.

Nicht super schnell, aber auch keine wirklichen Probleme: Routenverfolgung zu www.geocaching.com [63.251.163.200] über maximal 30 Hops: 1 1 ms 1 ms <1 ms fritz.box [192.168.x.x] 2 13 ms 12 ms 12 ms 192.0.0.1 3 13 ms 13 ms 41 ms 62.72.71.113 4 22 ms 19 ms 23 ms xnl1002aihb001.versatel.de [80.249.209.109] 5 22 ms 21 ms 19 ms ams-ix-ae6-inap.com [80.249.209.187] 6 24 ms 20 ms 32 ms 216.52.199.46 7 99 ms 99 ms 99 ms bbr1.ae101.bsn003.pnap.net [64.95.159.33] 8 130 ms 116 ms 116 ms bbr1.ae101.chg.pnap.net [64.95.159.182] 9 157 ms 157 ms 157 ms bbr2.ae102.sef.pnap.net [64.95.158.85] 10 156 ms 156 ms 157 ms bbr1.ae7.sef.pnap.net [64.95.158.77] 11 157 ms 159 ms 156 ms core1.po2.inap-31.sea.pnap.net [64.95.158.154] 12 157 ms 156 ms 175 ms border1.ae1-bbnet1.sef.pnap.net [63.251.160.4] 13 158 ms 156 ms 157 ms edge1.ae1-edgenet.sef.pnap.net [64.94.137.18] 14 157 ms 156 ms 156 ms www.geocaching.com [63.251.163.200]

Gestern und heute keinerlei Probleme. Die generelle Erreichbarkeit kann man mit Diensten à la "down for everyone or just me" gut testen: https://downforeveryoneorjustme.com/geocaching.com Da zu einer Web-Verbindung von Browser zu Server verschiedene Wege durchs Internet möglich sind, kann es sein, dass zwar Dein Internetzugang prinzipiell gut funktioniert und der Server bei Groundspeak auch - aber irgendwo dazwischen eine Verbindung "lahmt". Meine läuft z.B. über diese Zwischenstationen (Telekom als ISP): tracert www.geocaching.com Routenverfolgung zu www.geocaching.com [63.251.163.200] über maximal 30 Hops: 1 1 ms 1 ms 1 ms fritz.box [192.168.x.y] 2 7 ms 6 ms 7 ms blabla-irgendwas.dip0.t-ipconnect.de [a.b.c.d] 3 20 ms 19 ms 20 ms a-b-c-d-e-f-i.F.DE.NET.DTAG.DE [217.x.y.z] 4 28 ms 29 ms 27 ms 80.157.201.198 5 26 ms 25 ms 25 ms be3186.ccr41.fra03.atlas.cogentco.com [130.117.0.1] 6 32 ms 32 ms 32 ms be2813.ccr41.ams03.atlas.cogentco.com [130.117.0.121] 7 117 ms 117 ms 117 ms be12194.ccr41.lon13.atlas.cogentco.com [154.54.56.93] 8 116 ms 116 ms 116 ms be2317.ccr41.jfk02.atlas.cogentco.com [154.54.30.185] 9 116 ms 116 ms 116 ms be2889.ccr21.cle04.atlas.cogentco.com [154.54.47.49] 10 116 ms 116 ms 117 ms be2717.ccr41.ord01.atlas.cogentco.com [154.54.6.221] 11 130 ms 128 ms 128 ms be2831.ccr21.mci01.atlas.cogentco.com [154.54.42.165] 12 169 ms 174 ms 169 ms be3035.ccr21.den01.atlas.cogentco.com [154.54.5.89] 13 171 ms 171 ms 170 ms be3037.ccr21.slc01.atlas.cogentco.com [154.54.41.145] 14 185 ms 190 ms 186 ms be3284.ccr22.sea02.atlas.cogentco.com [154.54.44.73] 15 184 ms 187 ms 185 ms be3321.rcr21.sea03.atlas.cogentco.com [154.54.42.206] 16 185 ms 184 ms 184 ms Internap-Network-Services.demarc.cogentco.com [38.104.124.82] 17 166 ms 166 ms 166 ms border1.ae2-bbnet2.sef.pnap.net [63.251.160.68] 18 169 ms 167 ms 167 ms edge1.ae1-edgenet.sef.pnap.net [64.94.137.18] 19 170 ms 171 ms 171 ms www.geocaching.com [63.251.163.200] Ablaufverfolgung beendet. Also erst meine Fritzbox, dann der Telekom-Einwahlserver, dann Router der DTAG (telekom), dann ein Internet-Anbieter namens Cogent, dann über einen namens PNAP und dann zum Web-Frontend-Server www.geocaching.com. Bei Dir läuft das vielleicht ganz anders, und irgendein Techniker bei irgendeinem der Provider hat irgendwas falsch konfiguriert, und nun hakt es. Wo genau? Keine Ahnung. Wer das beheben kann? Erst recht keine Ahnung. Die Webseite an sich scheint es nicht zu sein.

I do individual logs for most of my geocaches. Every now and then we do power trails where we snag 90-200 geocaches in a day. I don't do individual logs as there really isn't anything interesting to say. If there is something noteworthy, I go back and edit my log accordingly. The reason I am asking the questions is a group of us are doing the ET Highway in May. We will get 2,400 geocaches in five days. How many caches will we get each day? I have no way of knowing. However, if I can press "Found It" on my Garmin Montana then when I get home I will have a file that reflects what caches I got each day. I can then process a mass logging using the correct date. The cache owners of this power trail actually prefer a nice log on the first or last cache and then copy/paste logs for all others. My other alternative is to purchase a cheap laptop and use GSAK.

Hallo 3Johns, kontaktiere am besten direkt die Owner des Events - das hat ja schon im Oktober 2022 stattgefunden, ist inzwischen also schon ein Weilchen her. Und laut Listing (https://www.geocaching.com/geocache/GC9NVQD_entenparty-das-vorevent) sind hier noch 28 (!!!) Trackables eingeloggt, mehr als 5 Monate nach dem Event sollte das so nicht sein. Die Owner sind ein Team und einer davon hat sogar seine Handynummer im Profil angegeben. Ich würde da einfach einmal anrufen, das ist das schnellste. Der übliche Weg wäre natürlich über das Message-Center, aber wenn du schon mal die Telefonnummer hast, ...!? Die sollen sich bitte mal um alle 28 Trackables kümmern, das kann's ja nicht sein, dass ein Event zu so einem TB-Grab wird. Wenn natürlich ein Eventbesucher die Trackables mitgenommen hat, ist es möglicherweise schwer, das nachzuverfolgen - auch für die Owner, denn es waren fast 200 Teams anwesend. Aber wenn, dann haben sie wohl die beste Chance. Herzliche Grüße Jochen

I've been out of action for a while. Long enough that I can't remember how to use my GPS. Not so much the function...but getting caches onto the unit. Any help is greatly appreciated.

I pre search when I travel and make lists. My caching is less random, especially these days. I am travelling now. I searched and listed unfound SideTracked caches, 200 caches, caches in county (council) areas I still haven't found any in, Mary Mackillop caches, a web cache, Earth caches, Virtual caches (I need to increase the finds of the last two for challenges. I used to ignore Earth caches.), and caches that I need to fulfil challenges. Then, if on some days I want more caches, I look for small sized caches and above. It has to be a very low available cache day to list micros, unless they fulfill one of the previous listed things. I don't need to do power trails; I would rather focus on fewer 'speciality' caches.

Near me is a "Bikeway Challenge Trail", 30 or so challenge caches along a a bikeway where our local group holds a CITO each year. When I first started geocaching, I attended the CITO and was encouraged by others to sign all the challenges along the route (we walked it). At that point I didn't think I'd ever qualify for any, with my handful of finds and some of them needing thousands of caches to qualify, like the 4444 or 7777 type (4000 trads, 400 mystery, 40 event, 4 webcam, for example). But those more experienced told me to sign anyway, and see what happens over the years - I might be surprised. I have actually completed 11 of those challenges, and I am very close to 2 or 3 others; still far away from 4444, 7777, the 200+ in a day, 10 icons in a day, 6 states in a day, etc; and I may eventually get those too if my health and motivation keeps up. I don't see these challenges as meant to "isolate or exclude", but as they are intended to be, a challenge to up my geocaching game and have some goals to reach! There's a lot about the geocaching experience that those new to it need to learn - and it does take time. Not everyone does travel bugs, or challenges, or mysteries, or Wherigo's - not that they are being excluded but there is a great variety to this hobby, and a you spend more time "doing it", you learn more and expand your horizons. Or not. It's your choice. Find those you can find, or want to, and ignore the rest, until the time comes when you DO want to go for more. Thanks to this thread, I just found one more along the trail that I can now log as a find! And a couple that have been added that were either missing or not a part of the trail when I first signed them all in 2018. I look at it as I've got more caching to do!!

HHL: You are having more success with your Swedish lists, than I do with my Alberta and Saskatchewan lists. I note that your last four are all over the maximum of 750 caches to which I now appear to be limited. That is, my button "Add 750 to list" never goes higher than 750. I have tried several times with lists of 850 or more, and 750 is the maximum that I can add. Also, I have now worked out the process of creating lists from the search map which is a little trickier than I remember it being before. For example, before I figured out the process, when I had my map set to show only 50 caches at a time, (or 100 or 200), then, until I worked out the correct procedure, when I tried to add the geocaches I wanted to a list, my list would only contain 50, or 100, or 200, depending on what setting I was using for the number of caches to be shown on my map at the time I made the list. I have now worked out the crucial need to select the "Sort by" box on the upper left side of the screen beside the map. When I do that, I get the "Add 750 to list" box. Now that I have figured that part out, then (as you say), the procedure works "flawlessly" for me as well :-) Das Leben ist in der Tat eine Reise, aber für einige von uns hat es ein paar Wendungen mehr als für andere. :-) Vielen Dank für Ihre Antwort auf meinen Hinweis. MartyWalker1

Sure, that's what I usually do in the end. Or, if the cache allows it, resort to "alternate" solutions ... e.g. for one of the unsolved puzzles, I'm quite sure about the general area where the cache is (a roughly 200 m long and 20 m zone) and there are spoiler photos. Geocaching with very fuzzy coordinates ! Well ... I don't have to, but it would still be nice .