#delayrepay
Live, measured metrics for the hashtag #delayrepay from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #delayrepay
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-07-27 23:20 UTC2 uses by 2 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-07-27 23:20 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-27 23:20 UTCEverything below is measured over the latest 15 public posts (spanning ~31394 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (15)
Avg boosts / post: 0.3
Top of the latest posts
The statutory #DelayRepay mechanism for UK train company #GreatWesternRailway in effect via their website is almost certainly designed to be deliberately obfuscatory to put people off making legitimate claims when suffering delayed trains.
Blimey, South Western have coughed up the #DelayRepay already. It's only £1.77 but still.
2 off #DelayRepay claims submitted. Let's see who wriggles hardest, CrossCountry or South Western. #trains
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/delayrepay