#nascom1
Live, measured metrics for the hashtag #nascom1 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #nascom1
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 · mastodon.online (Mastodon public tags API) · fetched 2026-11-10 19:50 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-11-10 19:50 UTCNo related tags with measured usage found for #nascom1.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-11-10 19:50 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 1
Used together with
Top of the latest posts
A single board computer with an 8035 CPU. I made it in 1979. As a slave to a NASCOM 1 {https://en.wikipedia.org/wiki/Nascom_(computer_kit) with a Z80 CPU} it was a little development system for 8048 microcontrollers. I implemented the ports
What “nascom1” means
WikipediaThe Nascom 1 and 2 were single-board computer kits issued in the United Kingdom in 1977 and 1979, respectively, based on the Zilog Z80 and including a keyboard and video interface, a serial port that could be used to store data on a tape cassette using a proprietary standard, and two 8-bit parallel ports. At that time, including a full keyboard and video display interface was uncommon, as most microcomputer kits were then delivered with only a hexadecimal keypad and seven-segment display. To min
“Nascom” on Wikipedia (CC BY-SA) →#nascom1 across platforms
every network with a public tag surfaceFollow #nascom1 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/nascom1