#SenseCAP
Live, measured metrics for the hashtag #SenseCAP from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sensecap
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 · mas.to (Mastodon public tags API) · fetched 2026-07-27 05:41 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-27 05:41 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 05:41 UTCEverything below is measured over the latest 39 public posts (spanning ~35103 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (30) · German (7) · Danish (1) · Portuguese (1)
Avg boosts / post: 0.8
Top of the latest posts
I was writing my own Meshtastic firmware for Seeed T1000-E and I accidentally wrote over the flash based bootloader and SoftDevice. This meant some lovely dremel time as the only way to fix is by accessing the JTAG pads inside the device. I
I was curious where the sensors were located on the #SenseCAP T1000-e. It took me a few minutes to find this picture and so I thought it might be of interest to some who also have these nodes. Technically this appears to be from an earlier
I had been waiting eagerly for these nodes to get back in stock at #Muziworks The #SenseCAP Tracker T1000-E seems to do it all. A very impressive built-in antenna, GPS, temperature sensors, beeper speaker etc. Unfortunately, it looks like i
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/sensecap