#hack4rail
Live, measured metrics for the hashtag #hack4rail from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #hack4rail
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 · mas.to (Mastodon public tags API) · fetched 2026-09-29 17: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 · mas.to (Mastodon public search API) · fetched 2026-09-29 17:26 UTCNo related tags with measured usage found for #hack4rail.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-09-29 17:26 UTCEverything below is measured over the latest 15 public posts (spanning ~9233 hours).
Posting hours (UTC) — busiest: 11:00
Languages: German (11) · English (4)
Avg boosts / post: 1.9
Top of the latest posts
Our first official Open Rail community meetup series starts NOW! 🚂 The OpenRail Association is launching its regular online gatherings 📅 July 9, 2026 ⏰️ 2:00 PM CEST 📆 Recurring: Second Thursday of each month 🔗 Join here: https://conf.f
Huh, our team actually won 2nd place at #Hack4Rail. How unexpected, but what a nice surprise!
EC 1213 zwar nicht mit #FensterAuf, aber dafür mit #HintenRausSchauen. #Hack4Rail
#hack4rail across platforms
every network with a public tag surfaceFollow #hack4rail 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/hack4rail