#RT3s
Live, measured metrics for the hashtag #RT3s from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rt3s
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 11:16 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 11:16 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:16 UTCEverything below is measured over the latest 5 public posts (spanning ~12402 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0.6
Top of the latest posts
I'm looking for someone who is willing to do the hardware M17 mod to a Retevis RT3S radio (same as the Tytera MD-UV380). If you are willing to help out please get back to me. I'm putting this out into the fediverse and curious to see what c
@VK5ZSH Hi! I just recently did. I did not mod mine yet. Having some issues with #RT3s changing MCUs recently...
I've started tinkering with a Retevis #RT3s radio. I've installed #OpenRTX and found that there were some issues. This is due to Retevis changing the original STM32F405 for what we suspect is a GD32 MCU. If someone knows what MCU may have a
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/rt3s