#regionalrail
Live, measured metrics for the hashtag #regionalrail from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #regionalrail
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-29 21:11 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-29 21:11 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 21:11 UTCEverything below is measured over the latest 40 public posts (spanning ~21980 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (35)
Avg boosts / post: 0.7
Top of the latest posts
In headline-ish form for the international audience: Pomeranian Voivodeship reveals offers in tender for 2027~2030 timetable years, SKMT unexpectedly bids and outbids Polregio for regional EMU lines by >150 mln PLN (~27% cheaper), Polregio
Back in 2015 with the opening of the PKM line (https://pl.wikipedia.org/wiki/Linia_kolejowa_nr_248), SKMT was given the task of operating it using brand-new Pesa DMUs ordered by the voivodeship to go with it (which is also where they introd
Before I go into the objections, let's see how things are laid out: The voivodeship divided the order into three lots, all mostly centered on Olsztyn, its capital: - Lot I - "Internal" - covering electric trains to Elbląg and Ełk via Korsze
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/regionalrail