#HAMChallenge
Live, measured metrics for the hashtag #HAMChallenge from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #hamchallenge
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-27 14:52 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-27 14:52 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 14:52 UTCEverything below is measured over the latest 40 public posts (spanning ~4357 hours).
Posting hours (UTC) — busiest: 08:00
Languages: German (25) · English (15)
Avg boosts / post: 1.4
Top of the latest posts
One of the very first CW activities I took part in on my cw journey, was the AGCW VHF/UHF contest (144/432 MHz, see https://www.agcw.de/contest/vhf-uhf/ ) and what I'd call 'summer edition' took place again last saturday. Throughout the las
I modified my ZS6BKW to work on 160m. I replaced my balun with an alligator cable that connected the center pin of the coax to both terminals of the ladder line. It worked. Running 50W on FT8 I managed one qso with DL7GP (135km). I got -17
#hamchallenge week 16 - Operate in an uncommon digital mode Which mode did you choose? What hardware or software did you use? Were you able to make a QSO? https://www.hamchallenge.org/challenges/34/toots #hamradio
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/hamchallenge