real humans have used our sites since we started counting.
Not visits. Not bots. People, each counted once. Pulled from Google Analytics today, Oct 12, 2026, with the discounts shown below, in the open.
How 329 is counted
Counted means every user analytics recorded, by city. A person who visited from two cities counts in both city rows, which is why the counted total runs higher than a simple user count. We keep the method anyway: it is the only way to subtract us and the bots honestly. A few counted humans (27) have no city recorded at all; they stay in, they are probably people on VPNs.
The last 7 days
Humans by property, all time
| Property | Counted | Us | Datacenter | Humans |
|---|---|---|---|---|
| The Studio | 356 | 34 | 116 | 206 |
| E2 | 82 | 13 | 4 | 65 |
| Llama Chat | 70 | 9 | 3 | 58 |
| Total | 508 | 56 | 123 | 329 |
Clear Recipe, Llamagram, and Clear only started measuring on Oct 12, so their humans are not in this table yet. This number is a floor, not a ceiling.
Where the humans are
Real places, from the same data. No datacenter cities on this list.
City counts are per property, so a person who visited two of our sites from the same city appears once per site.
What counts as a bot here
- Datacenter cities. Ashburn, Virginia and Singapore host huge server farms and few of our readers. Traffic that "lives" there is usually a bot, a scraper, or a VPN endpoint, so we subtract all of it. Some real people on VPNs get subtracted too. We would rather undercount humans than overcount them.
- Us. Our own team tests these sites constantly, and every test visit lands in the raw numbers. We know which city is ours, so all of it comes out. The city itself stays off this site, on purpose.
- What we do not do: no fingerprinting, no following individuals, no selling anything. Analytics reports totals and cities to us through a read-only service account. That is all it can do; its permission is Viewer.
Method and numbers published Oct 12, 2026. When the numbers move, this page moves, and the dev log says why.