#dxpeditions
Live, measured metrics for the hashtag #dxpeditions from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dxpeditions
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 21:25 UTC0 uses by 0 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 21:25 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 21:25 UTCEverything below is measured over the latest 3 public posts (spanning ~6789 hours).
Posting hours (UTC)
Languages: English (2) · French (1)
Avg boosts / post: 0.7
Top of the latest posts
“Wednesday October 16th at 7:30pm (1830z) zoom 366 093 9746 One man DX pedition to Pacific with Bob GM4DGL A one man #DXpedition to ZL, ZL7, VK7, VK9L, VK9N lasting 8 weeks. Main aim was to explore the capabilities of 20m/40m/80m two-elemen
I think its pretty terrible when major #DXpeditions operate near the bottom of the band where many ops aren't licensed. Example: US General Class can't transmit below .025 #CW or 14.225 MHz #SSB. Even if they want to be down there for some
#HamDXMap Release #5 1️⃣ #SDR Receiver located on the map 2️⃣ #DXpeditions current and planned 3️⃣ Main info panel retractable Install #HamDXMap as an #application (smartphone, Chrome Edge on windows) #DX#hamradio #HNY2024 ▶️https://dxmap.f
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/dxpeditions