#h3f8
Live, measured metrics for the hashtag #h3f8 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #h3f8
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:16 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:16 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 08:16 UTCEverything below is measured over the latest 39 public posts (spanning ~4510 hours).
Posting hours (UTC) — busiest: 02:00
Languages: German (3)
Avg boosts / post: 0.1
Top of the latest posts
#ScienceJapan: " Failure cause of H3 rocket No. 8 identified as "delamination of satellite mounting section": Measures to be implemented for resumption " "Flight data showed that 3 min. and 45 sec. after launch, immediately after the "fairi
#NHK: " Japan's aerospace agency reports likely cause of H3 rocket launch failure " ".. highly likely a problem occurred with the payload support structure at the top of the rocket." ".. adhesive sites in components of the payload support s
" Launch Failure of the 8th H3 Launch Vehicle and Setting up a Special Task Force " ".. launched .. QZS-5 .. aboard the .. H3 F8 at 10:51:30 on Dec. 22, 2025 (JST) from Tanegashima Space Center. .. second stage engine’s second ignition fail
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/h3f8