Engagement
45 posts held, back to 18 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 125 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 4.88%
- avg views ÷ 29,237 subscribers
- Avg views / post
- 1,430
- 11 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 11
- of 45 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
19 Oct 2026, 02:17 UTC887 viewsread 23 October 2026 https://cuttingthroughthematrix.substack.com/p/alan-watt-redux-285-psyop-war-uses?utm_source=podcast-email&publication_id=5069843&post_id=221005235&utm_campaign=email-play-on-substack&utm_content=watch_now_button&r=46hg0i&triedRedirect=true&utm_medium=email
Signed mikhail orlov
11 Oct 2026, 14:18 UTC≈1,720 viewsread 23 October 2026 https://youtu.be/Tb2jNe4L0vU
Signed mikhail orlov
10 Oct 2026, 06:52 UTC≈1,400 viewsread 23 October 2026 https://cuttingthroughthematrix.substack.com/p/alan-watt-redux-284-a-stitch-in-time?utm_source=podcast-email&publication_id=5069843&post_id=219627095&utm_campaign=email-play-on-substack&utm_content=watch_now_button&r=46hg0i&triedRedirect=true&utm_medium=email
Signed mikhail orlov
4 Oct 2026, 16:16 UTC≈1,950 viewsread 23 October 2026 https://youtu.be/5LcThgXTtgU
Signed mikhail orlov
4 Oct 2026, 16:15 UTC≈1,510 viewsread 23 October 2026 https://youtu.be/2v3-MyKRylE
Signed mikhail orlov
4 Oct 2026, 16:14 UTC≈1,280 viewsread 23 October 2026 https://youtu.be/mnRnAHNvS24
Signed mikhail orlov
4 Oct 2026, 16:13 UTC≈1,100 viewsread 23 October 2026 https://cuttingthroughthematrix.substack.com/p/alan-watt-redux-like-nosferatu-uncloaked?utm_source=podcast-email&publication_id=5069843&post_id=218796291&utm_campaign=email-play-on-substack&utm_content=watch_now_button&r=46hg0i&triedRedirect=true&utm_medium=email
Signed mikhail orlov
3 Oct 2026, 05:27 UTC≈1,350 viewsread 23 October 2026 https://youtu.be/htv0QcGDj9I
Signed mikhail orlov
2 Oct 2026, 13:52 UTC≈1,380 viewsread 23 October 2026 https://youtu.be/dSAQAuslgLY
Signed mikhail orlov
1 Oct 2026, 22:48 UTC≈1,390 viewsread 23 October 2026 https://cuttingthroughthematrix.substack.com/p/real-history-with-melissa-nick-heys?utm_source=podcast-email&publication_id=5069843&post_id=218356016&utm_campaign=email-play-on-substack&utm_content=watch_now_button&r=46hg0i&triedRedirect=true&utm_medium=email
Signed mikhail orlov
28 Sept 2026, 02:12 UTC≈1,720 viewsread 23 October 2026 https://cuttingthroughthematrix.substack.com/p/alan-watt-ngo-philanthropix-industrial?utm_source=podcast-email&publication_id=5069843&post_id=217676918&utm_campaign=email-play-on-substack&utm_content=watch_now_button&r=46hg0i&triedRedirect=true&utm_medium=email
Signed mikhail orlov
21 Sept 2026, 00:30 UTC≈2,250 viewsread 23 October 2026 https://cuttingthroughthematrix.substack.com/p/news-is-the-most-perfected-form-of?utm_source=podcast-email&publication_id=5069843&post_id=216623070&utm_campaign=email-play-on-substack&utm_content=watch_now_button&r=46hg0i&triedRedirect=true&utm_medium=email
Signed mikhail orlov
Showing the 12 most recent of 45 posts we hold for @mrn_death. 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.
Cite this entry
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 24 October 2026 — this
entry's latest reading, not the date you are reading this.
“mRNA DEATH TOLL” (@mrn_death), 29,237 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/mrn_death.
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.