#hc44s
Live, measured metrics for the hashtag #hc44s from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #hc44s
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 08:12 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 08:12 UTCNo related tags with measured usage found for #hc44s.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 08:12 UTCEverything below is measured over the latest 2 public posts (spanning ~4057 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 1.5
Used together with
Top of the latest posts
#hamchallenge Week 44: Receive a QRSS signal. Easy one for me, because I have a 30m QRSS grabber running 24/7 for a bit over a year now. The details are described on my website. https://fkurz.net/ham/qrss/qrss-wsprd-setup.html #HC44S The sc
I made some software rendering pixel fonts into audio and I TXed a #qrss signal. RXed my own signal from the grabbers, plus some common British beacons on 30m. Does this count as a threefer for the #hamchallenge? (44, 46 and 48). @hamchalle
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/hc44s