#re13
Live, measured metrics for the hashtag #re13 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #re13
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-11-12 07:19 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-11-12 07:19 UTCNo related tags with measured usage found for #re13.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-11-12 07:19 UTCEverything below is measured over the latest 40 public posts (spanning ~6201 hours).
Posting hours (UTC) — busiest: 04:00
Languages: German (40)
Avg boosts / post: 0.2
Top of the latest posts
Aufgrund von Brückenarbeiten kommt es bei den Zügen der Linien #RE7, #RE13, #RE57 und #RB53 vom 30.10. (21:00 Uhr) - 06.11.26 (21:00 Uhr) zu Teilausfällen auf verschiedenen Streckenabschnitten. Bei den Zügen der Linie RE 7 kommt es zu Teila
#RE13: Die Regionalexpresse aus Richtung Venlo enden und beginnen in #Düsseldorf Hbf. Aus Richtung Hagen Hbf enden und beginnen die Züge in Schwelm. Die Folge sind Teilausfälle zwischen Schwelm und Düsseldorf Hbf. Zur Zeit liegen für die #R
Bonn-Mehlem (09:43) - #Leverkusen-Manfort (10:39), die Fahrt beginnt in #Bonn Hbf um 09:54 Uhr. Alternative Reisemöglichkeiten: Sie können für die Teilausfälle zwischen Wuppertal-Oberbarmen und Wuppertal-Vohwinkel auf die Züge der RE 4, #RE
What “re13” means
Wiktionaryre/ɹeɪ/
- prepositionAbout, regarding, with reference to; especially in letters, documents and emails.
#re13 across platforms
every network with a public tag surfaceFollow #re13 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/re13