#lombardsbrucke
Live, measured metrics for the hashtag #lombardsbrucke from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lombardsbrucke
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-02 20:37 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-02 20:37 UTCNo related tags with measured usage found for #lombardsbrucke.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-02 20:37 UTCEverything below is measured over the latest 10 public posts (spanning ~17639 hours).
Posting hours (UTC)
Languages: German (9)
Avg boosts / post: 5
Top of the latest posts
In den 1960er-Jahren war eine dritte #Lombardsbrücke für eine Stadtautobahn in #Hamburg geplant, hier auf einer Montage von 1964. 🫣 Abbildung aus Heiko Grunert, Von der Festung bis Planten un Blomen (2020)
Im nördlichen Einfahrbereich des Hamburger Hbf müssen am 15.11.1990 Gleisbauarbeiten durchgeführt werden. Dabei wird auch der Turmtriebwagen 701 096 benötigt. Auf den S-Bahn-Gleisen kommt gerade eine 472/470-Doppeleinheit von der #Lombardsb
400 Meter Zukunft! Zusammen mit @P4F_Hamburg haben wir heute auf der #Lombardsbrücke in #Hamburg eine #ProtectedBikeLane eingerichtet. So viel Platz muss sein! Für sicheren #Radverkehr.
#lombardsbrucke across platforms
every network with a public tag surfaceFollow #lombardsbrucke 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/lombardsbrucke