#geocache
Live, measured metrics for the hashtag #geocache from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #geocache
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 09:23 UTC1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 09:23 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 09:23 UTCEverything below is measured over the latest 40 public posts (spanning ~6428 hours).
Posting hours (UTC) — busiest: 21:00
Languages: English (27) · German (7) · Dutch (4) · Portuguese (1)
Avg boosts / post: 2.6
Top of the latest posts
On my work trip to SoCal I was able to acquire four more 4-character QTH grid squares for #geocache finds, bringing my total to 130 and connecting the cluster including Los Angeles to the cluster including Seattle. I have 3058 total finds,
🗺️ Last weekend I reached 3000 total #geocache finds and today I made my 500th find in British Columbia! #geocaching
New instance, new #introduction. Hello everyone! I’m a meteorologist working at a company that launches #weather balloons. On Mastodon, I toot about #weather, mostly #BCstorm, #WAwx, and #ORwx. Despite being in the United States, most of my
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/geocache