#Biggesee
Live, measured metrics for the hashtag #Biggesee from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #biggesee
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.online (Mastodon public tags API) · fetched 2026-10-14 01:27 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-10-14 01:27 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-14 01:27 UTCEverything below is measured over the latest 40 public posts (spanning ~23248 hours).
Posting hours (UTC) — busiest: 09:00
Languages: German (38) · English (1)
Avg boosts / post: 0.5
Top of the latest posts
@FotoVorschlag #FotoVorschlag (Tag der) 'Currywurst' Currywurst, Pommes, Mayo ist quasi Pflichtprogramm, wenn ich mit dem #Motorrad unterwegs bin. Aber normalerweise fotografiere ich nicht unbedingt mein Essen. Hier mal eine Ausnahme, weil
Die Lokalzeitung berichtet von #Meshcore. https://www.sauerlandkurier.de/kreis-olpe/olpe/funkamateure-bauen-meshcore-netz-ohne-internet-und-mobilfunk-auf-94432847.html #Sauerland #Biggesee #Lorawan #Mesh
#Feiertagsausflug zum #Biggesee im #Sauerland -von unserer #Ferienwohnung aus sogar per #ÖPNV erreichbar. Und die Schiffe auf der #Biggetalsperre (wie sie eigentlich heißt) fahren #elektrisch. #FotoMontag
What “biggesee” means
WikipediaThe Biggesee or Bigge Reservoir is a reservoir in Germany. It lies in the southern part of the Sauerland between Olpe and Attendorn.
“Biggesee” on Wikipedia (CC BY-SA) →#biggesee across platforms
every network with a public tag surfaceFollow #biggesee 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/biggesee