https://clifhigh.substack.com/p/resurrection

Channel
Clif High Living Large
@clif_high_living_large
On this record: Topic · Growth · Engagement · Posts · Cite this entry
472subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001194115032 |
|---|---|
| Type | Channel |
| Username | @clif_high_living_large |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/clif_high_living_large |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 81% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 16:55 | 472 | -1 |
| 13 Sept 2026, 11:20 | 473 | -1 |
| 5 Sept 2026, 05:41 | 474 | -3 |
| 28 Aug 2026, 12:13 | 477 | -2 |
| 22 Aug 2026, 13:13 | 479 | -1 |
| 8 Aug 2026, 04:53 | 480 | no change |
| 7 Aug 2026, 05:03 | 480 | first reading |
Engagement
20 posts held, back to 8 April 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 1 page of 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 21 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
https://rumble.com/v7co01o-wacky-woo-special-report-with-clif-high-and-jean-claude-beyond-mystic-jul-1.html
https://youtu.be/6NUd7OtaE5g
https://clifhigh.substack.com/p/the-content-stream-in-my-head-has
https://clifhigh.substack.com/p/the-formerly-pending-recent-now-emergent
https://clifhigh.substack.com/p/deflation-and-the-obvious-way-out
https://clifhigh.substack.com/p/chatting-woo-with-you-know-whoheidis
https://clifhigh.substack.com/p/why-do-you-think-that
https://clifhigh.substack.com/p/with-an-option-to-renew
https://youtu.be/rNkp5vdMjmI
https://clifhigh.substack.com/p/the-articles-of-agreement-for-the
https://clifhigh.substack.com/p/it-came-as-a-shock
Showing the 12 most recent of 20 posts we hold for @clif_high_living_large. 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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“Clif High Living Large” (@clif_high_living_large), 472 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/clif_high_living_large.
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.