#beattime
Live, measured metrics for the hashtag #beattime from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #beattime
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-27 22: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-27 22:54 UTCNo related tags with measured usage found for #beattime.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 22:54 UTCEverything below is measured over the latest 3 public posts (spanning ~25053 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0
Top of the latest posts
Finally got around to posting about #Swatch #BeatTime. It was all the rage at the turn of the century. Perhaps it's overdue a comeback! https://blog.quirke.org/timezones/swatch/beats/2026/02/03/post.html
@linkert adding time zones to 'beat format' has limited sense. What do you think ab adding longtitude? Or decimal longtitude I believe the human time format should inform ab day and/or night 'progress' not the shift from the midnight. So it
Ok imagine: Swatch Internet Time/.Beat time re-imagined as simply "Beat Time" without the dumb dot and with UTC type time zones. I would be on BT+1 — or "beat +1". Absolutely no damn daylight saving allowed. #swatchInternetTime #SIT #beatTi
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/beattime