#reichstagsbrandverordnung
Live, measured metrics for the hashtag #reichstagsbrandverordnung from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #reichstagsbrandverordnung
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.social (Mastodon public tags API) · fetched 2026-08-20 03:52 UTCNo measured public usage for #reichstagsbrandverordnung in the last 7 days. That is a real result, and a good one to know: this hashtag is wide open right now. We show a dash before we ever show a made-up number. Browse the trending index for tags with live measurements.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-08-20 03:52 UTCNo related tags with measured usage found for #reichstagsbrandverordnung.
Live pulse
measured · Mastodon tag timeline · fetched 2026-08-20 03:52 UTCNo recent public posts found for #reichstagsbrandverordnung on Mastodon. Nothing measured, so nothing shown.
What “reichstagsbrandverordnung” means
WikipediaThe Reichstag Fire Decree, officially the Decree of the Reich President for the Protection of People and State, was an emergency decree issued by Paul von Hindenburg on 28 February 1933, the day after the Reichstag fire and five days before the final elections in the Weimar Republic. Issued under Article 48 of the Weimar Constitution, the decree suspended key civil liberties guaranteed by the Weimar Constitution, including personal liberty, freedom of expression, freedom of the press, freedom of
“Reichstag Fire Decree” on Wikipedia (CC BY-SA) →#reichstagsbrandverordnung across platforms
every network with a public tag surfaceFollow #reichstagsbrandverordnung 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/reichstagsbrandverordnung