#limfjordsbroen
Live, measured metrics for the hashtag #limfjordsbroen from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #limfjordsbroen
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.social (Mastodon public tags API) · fetched 2026-09-26 18:08 UTCNo measured public usage for #limfjordsbroen in the last 7 days. That is a real result, and a good one to know: this hashtag is wide open right now. We show a dash before we ever show a made-up number. Browse the trending index for tags with live measurements.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-09-26 18:08 UTCNo related tags with measured usage found for #limfjordsbroen.
Live pulse
measured · Mastodon tag timeline · fetched 2026-09-26 18:08 UTCNo recent public posts found for #limfjordsbroen on Mastodon. Nothing measured, so nothing shown.
What “limfjordsbroen” means
WikipediaLimfjordsbroen is a Danish bridge which connects Nørresundby and Aalborg over Limfjord, a shallow sound. It was inaugurated 30 March 1933 in the presence of approximately 30,000 spectators and attended by Thorvald Stauning. It was a toll bridge until 1935. The first fixed link between the two cities was established in 1865 in the form of a pontoon bridge, which was in use until the present bridge was established; the original bridge was slow to open and close when ship traffic passed. The bridge
“Limfjordsbroen” on Wikipedia (CC BY-SA) →#limfjordsbroen across platforms
every network with a public tag surfaceFollow #limfjordsbroen 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/limfjordsbroen