#Erpel
Live, measured metrics for the hashtag #Erpel from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #erpel
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-10-18 04:28 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-10-18 04:28 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-18 04:28 UTCEverything below is measured over the latest 37 public posts (spanning ~55492 hours).
Posting hours (UTC) — busiest: 19:00
Languages: German (14) · English (3)
Avg boosts / post: 0.8
Top of the latest posts
The Neutor (new gate) in the village of Erpel (Unkel municipality, Neuwied district, Rhineland-Palatinate), built around 1420, was part of the village fortifications. (January 2024) (Foto: © Rüdiger Benninghaus) #Stadttore, #towngates, #Arc
Stockentenerpel (Anas platyrhynchos) https://de.wikipedia.org/wiki/Stockente #AnasPlatyrhynchos #Stockente #Erpel #Vogelfotografie #BirdPhotography #Wildtierfotografie #WildlifePhotography #Naturfotografie #NaturePhotography #SilentSunday #
Diese #Erpel enteten bei #Erkner herum. Aber was war das für ein #Gewässer? Es war die Wanderung von erkner nach Hangelsberg auf dem 66-Seen-Wanderweg. #Wanderempfehlungen in diesem Bundesland mit GPX-Track findet Ihr unter https://www.oeko
What “erpel” means
WikipediaErpel is a municipality in the district of Neuwied, in Rhineland-Palatinate, Germany.
“Erpel” on Wikipedia (CC BY-SA) →#erpel across platforms
every network with a public tag surfaceFollow #erpel 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/erpel