#memtest86
Live, measured metrics for the hashtag #memtest86 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #memtest86
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-10-01 23:24 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-10-01 23:24 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-01 23:24 UTCEverything below is measured over the latest 40 public posts (spanning ~37609 hours).
Posting hours (UTC) — busiest: 17:00
Languages: English (28) · German (9) · Norwegian (2) · Esperanto (1)
Avg boosts / post: 1
Top of the latest posts
"Neuer" DIMM im Slot und geht. Spannend. Der ist 6 Jahre neuer als die anderen. Hat aber die gleichen Specs. Dual-Channel geht also. #memtest86 findet keine Fehler mehr :)
Yo wtf #pentium2 #pentiumii #retropc #retrocomputer #retrocomputing #oldpc #oldcomputer #vintagecomputer #memtest86 #crt #tinkering
This is soo chill to look at. :) It's #memtest86 accompanied by computer metal via Master Boot Record. Spoiler: the ram check is successful without errors. https://youtube.com/watch?v=OJQ2UT-7h_o
What “memtest86” means
WikipediaMemTest86 and Memtest86+ are memory test software programs designed to test and stress test an x86 architecture computer's random-access memory (RAM) for errors, by writing test patterns to most memory addresses, reading back the data, and comparing for errors. Each tries to verify that the RAM will accept and correctly retain arbitrary patterns of data written to it, that there are no errors where different bits of memory interact, and that there are no conflicts between memory addresses.
“MemTest86” on Wikipedia (CC BY-SA) →#memtest86 across platforms
every network with a public tag surfaceFollow #memtest86 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/memtest86