#techresults
Live, measured metrics for the hashtag #techresults from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #techresults
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-11-12 09:00 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-11-12 09:00 UTCNo related tags with measured usage found for #techresults.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-11-12 09:00 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: German (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
RT @bnjmn_marie: Mein erster vollständiger Durchlauf von Qwen3.8 27B auf DeepSWE 1.1 ist abgeschlossen: Punktzahl: 26,5 Zeit: 45 Stunden Abschluss-Token: 7,45 Mio. Gesamtinput- und Output-Token: 820 Mio. Modellaufrufe: 9.591 Die Punktzahl l
#techresults across platforms
every network with a public tag surfaceFollow #techresults 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/techresults