Channel
@JohnMcAfeeDMS
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4,201subscribers
-22 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001411488689 |
|---|---|
| Type | Channel |
| Username | @JohnMcAfeeDMS |
| Created | 16 August 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/JohnMcAfeeDMS |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 11:46 | 4,201 | -11 |
| 10 Aug 2026, 08:00 | 4,212 | -10 |
| 6 Aug 2026, 23:41 | 4,222 | -1 |
| 6 Aug 2026, 10:36 | 4,223 | no change |
| 6 Aug 2026, 09:44 | 4,223 | first reading |
20 posts held, back to 17 December 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 pagesof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 26 May 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 7 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 30 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
BOOOOOOOOOOOOOOOOOOOOOOOOOOMMMMMMM !!!
🥳🥳🥳
🥳🥳🥳
🥳🥳🥳
🤣🤣🤣😂😂
🥳🥳🥳
🤣🤣🤣🤣😂😂😂
BOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOMMMMMMMMMMMMMMMMMMMMMM !!!
🥳🥳🥳
🚨🚨🚨
🥳🥳🥳
Showing the 12 most recent of 20 posts we hold for @JohnMcAfeeDMS. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 13 August 2026 — this entry's latest reading, not the date you are reading this.
“John McAfee Official🇺🇸” (@JohnMcAfeeDMS), 4,201 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/JohnMcAfeeDMS.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.