#cqrlog
Live, measured metrics for the hashtag #cqrlog from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cqrlog
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-29 13:51 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-29 13:51 UTCNo related tags with measured usage found for #cqrlog.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 13:51 UTCEverything below is measured over the latest 19 public posts (spanning ~27213 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (17) · French (1) · Spanish (1)
Avg boosts / post: 0.3
Top of the latest posts
@PE4KH last time I checked, and my current setup is built around, #cqrlog on linux was the option with the most integration features, and more complete overall. Curious about what your next steps will be, good luck!
Hmm, #cqrlog is falling over on something with the date format since today 2026-01-02. Maybe this is a sign I need to look further for Linux-based amateur radio logging, because a simple apt update will not get me a fixed version. Full back
It's a real shame, but I'm thinking of giving up on cqrlog, which I've been loyal to for many years. After a change of computer, I lost patience and fell back on qlog. It's true that cqrlog is on the verge of abandonment. It remains to be s
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/cqrlog