#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 · fosstodon.org (Mastodon public tags API) · fetched 2026-08-12 16:21 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-08-12 16:21 UTCNo related tags with measured usage found for #limfjordsbroen.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-12 16:21 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 1
Used together with
Top of the latest posts
Last few days we had wonderful fog in the mornings. I decided to grab my underused camera and roam around. I was lucky enough to catch the sun rise over the Limfjordsbroen. #Aalborg #Limfjordsbroen #fog #photography #fujifilm
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