#dxcentralmwfrequencychallenge
Live, measured metrics for the hashtag #dxcentralmwfrequencychallenge from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dxcentralmwfrequencychallenge
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 · mastodon.online (Mastodon public tags API) · fetched 2026-10-07 10:53 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-10-07 10:53 UTCNo related tags with measured usage found for #dxcentralmwfrequencychallenge.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-07 10:53 UTCEverything below is measured over the latest 3 public posts (spanning ~3799 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.3
Top of the latest posts
@croyle One thing to keep in mind is that, depending on your setup, you might be able to receive some very distant & unexpected AM programs. I've enjoyed participating in some of the DX challenges put out by #DXcentral such as #DXCentralMWf
0855UTC Still working on goal-oriented AM listening for DX Central’s MW Frequency Challenge (Week 6: 690-720kHz) ~ (DX Challenges .com). I hear two stations fading in & out on 710AM depending on how I position the #TecsunS2000 “internal” ro
WLAC AM - Nashville, TN - Program: Armstrong & Getty. Not DX at all really (distance: 185mi) - but the first station copied within the freq range for the DX Central MW Frequency Challenge. First time I’ve paid attention to the programming /
#dxcentralmwfrequencychallenge across platforms
every network with a public tag surfaceFollow #dxcentralmwfrequencychallenge straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/dxcentralmwfrequencychallenge