#threadx
Live, measured metrics for the hashtag #threadx from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #threadx
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.social (Mastodon public tags API) · fetched 2026-09-26 12:59 UTCNo measured public usage for #threadx in the last 7 days. That is a real result, and a good one to know: this hashtag is wide open right now. We show a dash before we ever show a made-up number. Browse the trending index for tags with live measurements.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-09-26 12:59 UTCNo related tags with measured usage found for #threadx.
Live pulse
measured · Mastodon tag timeline · fetched 2026-09-26 12:59 UTCNo recent public posts found for #threadx on Mastodon. Nothing measured, so nothing shown.
What “threadx” means
WikipediaThreadX is an embedded real-time operating system (RTOS) programmed mostly in the C language. It was originally released in 1997 as ThreadX when Express Logic first developed it, later it was renamed to Azure RTOS (2019) after Express Logic was purchased by Microsoft, then most recently it was renamed again to Eclipse ThreadX (2023), or "ThreadX" in its short form, after it transitioned to free open source model under the stewardship of the Eclipse Foundation.
“ThreadX” on Wikipedia (CC BY-SA) →#threadx across platforms
every network with a public tag surfaceFollow #threadx 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/threadx