Telegram RegisterThe public register of Telegram
Telegram profile photo for Crypto Schizo

Channel

Crypto Schizo

@crypto_schizo

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Cite this entry

1,100subscribers

-22 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001318806818
TypeChannel
Username@crypto_schizo
Created29 April 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 October 2026
Last confirmed live22 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 22 October 2026
On Telegramt.me/crypto_schizo

Topic

Crypto & trading — 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 6 October 2026 and assigned it the closest of 31 fixed categories, at 68% 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

1,1001,1221,1117 August 2026 — 1,122 subscribers9 August 2026 — 1,120 subscribers16 August 2026 — 1,119 subscribers19 August 2026 — 1,118 subscribers22 August 2026 — 1,116 subscribers25 August 2026 — 1,115 subscribers28 August 2026 — 1,116 subscribers2 September 2026 — 1,113 subscribers8 September 2026 — 1,111 subscribers12 September 2026 — 1,109 subscribers28 September 2026 — 1,108 subscribers5 October 2026 — 1,107 subscribers6 October 2026 — 1,107 subscribers12 October 2026 — 1,102 subscribers19 October 2026 — 1,101 subscribers22 October 2026 — 1,100 subscribers7 August 202622 October 2026
16 measurements spanning 77 days, net -22. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,097–1,125 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Oct 2026, 14:571,100-1
19 Oct 2026, 04:371,101-1
12 Oct 2026, 15:211,102-5
6 Oct 2026, 18:241,107no change
5 Oct 2026, 15:381,107-1
28 Sept 2026, 04:591,108-1
12 Sept 2026, 06:211,109-2
8 Sept 2026, 08:561,111-2
2 Sept 2026, 22:241,113-3
28 Aug 2026, 15:031,116+1
25 Aug 2026, 05:331,115-1
22 Aug 2026, 07:071,116-2
19 Aug 2026, 06:111,118-1
16 Aug 2026, 06:491,119-1
9 Aug 2026, 23:321,120-2
7 Aug 2026, 00:001,122first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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 22 October 2026 — this entry's latest reading, not the date you are reading this.

“Crypto Schizo” (@crypto_schizo), 1,100 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/crypto_schizo.

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.