Open stats
How many people read Built by NPCs, updated every few minutes. We count without cookies, keep no IP addresses, and publish every hit we turned away next to the totals.
13 Oct 2026 to 13 Oct 2026, UTC
- Page views
- 23
- 4 on stories
- Daily visitors
- 12
- a day, on average
- Read-through
- 50%
- of story views reach the end
- Directory clicks
- 0
- sent to listed tools
Most viewed stories
Views by section
- News4
Most saved to ChatGPT and Claude
Stories readers sent to an assistant with the Save button on each story, to get a summary now and ask questions later. 1 save in this range: 1 to ChatGPT, 0 to Claude.
- Fingerprinting survives cookie blocking, and one vendor selling it passed $50M in ARR1 to ChatGPT0 to Claude
Hits we turned away
Every hit that reached us and was left out of the totals, grouped by reason, so you can check the figures above against what was filtered.
- Counted
- 26
- Not loaded by a browser from our pages
- 11
- Same visitor, same page, same day
- 7
How we count
- A view is a browser loading a page and its counting pixel, a tiny image that is never cached. Pages are cached at the edge, so the pixel is the part that reaches us.
- A visitor is one network and browser on one day. We hash the IP address (the /64 block for IPv6) with the browser's user agent and a salt that is replaced every UTC day. The salt and the hashes are deleted when the day ends, and nothing that identifies a person is stored.
- Repeats don't count. One visitor counts once per page per day, and for at most 60 pages a day in total.
- A read is a second pixel placed after the story and loaded lazily, so the browser only fetches it as the reader gets near the end. Browsers start loading a little early, so read-through is a close estimate.
- A directory click is counted through the link's ping, which the browser sends when a reader follows the link. Browsers that turn pings off (Firefox, Brave) send nothing, so the click count is a minimum.
- A save is a reader pressing “Save to ChatGPT / Claude” on a story. The link passes through our server, which counts it and sends the reader on to the assistant. Only a click the browser reports as the reader's own is counted, once per story per assistant per day. We record which assistant was picked and never see what happens there.
- Not counted: crawlers, scripts and link previews; requests that did not come from one of our pages; search results, the 404 and other utility pages. Older browsers that don't send fetch metadata are left out too, which keeps every figure on the low side.
- Nothing is sampled or adjusted. Days run on UTC, and every total is a plain sum of daily counts.
As of 18:33 UTC, 13 Oct 2026. Counting since 13 Oct 2026. The same figures as JSON: /stats.json