#gnss

Live, measured metrics for the hashtag #gnss from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #gnss

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.

$2,449.80/ year · 4-character #name
Claim #gnss$2,449.80/yr
Annual, renews each year
Buy on hashtag.space (web3)
one-timepay once, yours for life
card via hashtag.org · tokens via hashtag.space
1
Uses / 7 days
Mastodon
1
Accounts / 7 days
Mastodon
40
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 40
1.3
Avg reactions / post
Mastodon · last 40

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 05:18 UTC
0
07-21
0
07-22
0
07-23
0
07-24
0
07-25
1
07-26
0
07-27

1 uses by 1 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 05:18 UTC

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:18 UTC

Everything below is measured over the latest 40 public posts (spanning ~1221 hours).

Posting hours (UTC) — busiest: 13:00

00:0012:0023:00

Languages: English (24) · German (8) · Russian (3) · French (2) · Chinese (Taiwan) (2) · Italian (1)

Avg boosts / post: 2.1

Top of the latest posts

  • Great paper on wide-area transient interference,from a space-based source causing up to 10-dB GNSS degradation across Europe since 2019 in the important L1 band, from Russian early warning satellites in Molniya (“lightning”) orbits. Cosmos

    Frédéric Jacobs@[email protected]1492026-06-05 13:12 UTCView post →
  • 🛰️ It's here: native NTRIP support in QField 4.2. Sub-centimeter accuracy with no third-party app. Connect an RTK correction-capable GNSS device over Bluetooth, BLE or TCP, enter your NTRIP caster details in the positioning panel, and corr

    QField@qfield1292026-06-11 05:16 UTCView post →
  • A timing investigation for seven T-Beams: their external RTC preserves whole seconds, but cannot establish millisecond event order across units. I added GNSS PPS capture plus ESP32 monotonic interpolation, compared the resulting disciplined

    John Poole@[email protected]932026-06-21 23:55 UTCView post →

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/gnss