#jtdx
Live, measured metrics for the hashtag #jtdx from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jtdx
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:26 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:26 UTCNo related tags with measured usage found for #jtdx.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 21:26 UTCEverything below is measured over the latest 31 public posts (spanning ~33349 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (28) · Spanish (2) · German (1)
Avg boosts / post: 0.2
Top of the latest posts
🎯 📻 DARC FT4 Contest – Dein Ticket ins Contest-Abenteuer! 📻 🎯 Dienstag, 10. Februar 2026 | 20:00–21:29 Uhr (MEZ) Du fragst dich noch, ob Conteste was für dich sind? Wir auch – bis wir den DARC FT4 Contest entdeckt haben! 💪 Hier ist, wa
@BoscoLab yeah, I love #JTDX I feel like #JTDX is better at pulling even weaker signals out of the noise than #WSJTX but I haven't objectively measured that, lol
I just realized something funky is going on in #WSJTX for me I'm only seeing decodes up to about 1300 Hz in WSJTX, but in #JTDX I can see up to 2700 Hz 🤔 I'm using the same sound interface and channels (left vs. right, etc.) and I don't kn
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/jtdx