#generalservicesbuilding
Live, measured metrics for the hashtag #generalservicesbuilding from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #generalservicesbuilding
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-01 22:58 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-01 22:58 UTCNo related tags with measured usage found for #generalservicesbuilding.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-01 22:58 UTCEverything below is measured over the latest 8 public posts (spanning ~27000 hours).
Posting hours (UTC)
Languages: English (8)
Avg boosts / post: 0.1
Top of the latest posts
Today's photo: Binnenhaven | Oostelijke Handelskade - head (1895). [EN] In the middle is the General Services Building, at the head of the Oostelijke Handelskade. The ship to the left is the Fulmar, from […] [NL] In het midden het gebouw va
Today's photo: Javakade (1901). [EN] Work on the future Javakade. On the left is Oostelijke Handelskade. The boy in the foreground is probably one of Olie's sons. [NL] Werkzaamheden aan de latere Javakade. Links de Oostelijke Handelskade. O
Today's photo: Dijksgracht (1899). [EN] The railway enbankment along Dijksgracht (left). On the right the waters of the Binnenhaven, bordered by Oostelijke Handelskade. The building with towers is the General […] [NL] De spoordijk langs de
#generalservicesbuilding across platforms
every network with a public tag surfaceFollow #generalservicesbuilding 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/generalservicesbuilding