#department56
Live, measured metrics for the hashtag #department56 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #department56
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-05 11:07 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-05 11:07 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-05 11:07 UTCEverything below is measured over the latest 2 public posts (spanning ~275 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0.5
Top of the latest posts
I spent much of the day setting up my holiday village display, which mixes older and newer #Department56 and #Lemax pieces (and some generic village buildings). This is just a detail. Tomorrow I might do more photography. #ChristmasVillage
Wife got the Christmas village put up just in time for the in-laws to ohh over yesterday. This year it's the #Department56 North Pole series that came out of storage. #D56 #Villaging
What “department56” means
Wiktionary#department56 across platforms
every network with a public tag surfaceFollow #department56 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/department56