#recordsmanagement
Live, measured metrics for the hashtag #recordsmanagement from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #recordsmanagement
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-07-28 21:54 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-07-28 21:54 UTCNo related tags with measured usage found for #recordsmanagement.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 21:54 UTCEverything below is measured over the latest 40 public posts (spanning ~19327 hours).
Posting hours (UTC) — busiest: 14:00
Languages: Dutch (15) · English (14) · German (8) · French (3)
Avg boosts / post: 1.7
Top of the latest posts
#Anbietungspflicht #Archivgesetze #Schriftgutverwaltung (oder neudeutsch) #RecordsManagement https://www.welt.de/geschichte/article6a2a6be41089b0ba0bc0a9f5/neues-archivgesetz-ein-rechtsstaat-darf-seine-eigenen-spuren-nicht-beseitigen.html
Mijn nieuwe blog op ericburger .nl: "Microsoft 365 Priority Cleanup: archivering en hold herroepen of teniet doen" 👉🏼 De nieuwe functie Privacy Cleanup wordt binnenkort aangeboden voor toepassing op Exchange Online postvakken. 👉🏼 Het he
Belated news (because I haven't been on Mastodon recently), but good news nonetheless: Two weeks ago, May 14, I graduated with my Master of Information degree from #rutgers. I'm now hunting for a job involving #recordsmanagement or #digital
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/recordsmanagement