Channel
YCT DIGI BOOK 2026
@yct_digi_book
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,577subscribers
-232 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001203220775 |
|---|---|
| Type | Channel |
| Username | @yct_digi_book |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/yct_digi_book |
Topic
Education — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 04:37 | 4,577 | -6 |
| 4 Nov 2026, 02:49 | 4,583 | -11 |
| 1 Nov 2026, 02:41 | 4,594 | -8 |
| 29 Oct 2026, 04:09 | 4,602 | -11 |
| 25 Oct 2026, 19:39 | 4,613 | -6 |
| 22 Oct 2026, 19:16 | 4,619 | -6 |
| 19 Oct 2026, 12:40 | 4,625 | -7 |
| 16 Oct 2026, 04:48 | 4,632 | -6 |
| 13 Oct 2026, 15:16 | 4,638 | -19 |
| 7 Oct 2026, 10:16 | 4,657 | -25 |
| 30 Sept 2026, 07:59 | 4,682 | -26 |
| 19 Sept 2026, 16:15 | 4,708 | -10 |
| 14 Sept 2026, 18:20 | 4,718 | -8 |
| 11 Sept 2026, 14:57 | 4,726 | -13 |
| 7 Sept 2026, 01:36 | 4,739 | -6 |
| 2 Sept 2026, 13:00 | 4,745 | no change |
| 2 Sept 2026, 09:12 | 4,745 | -6 |
| 30 Aug 2026, 16:58 | 4,751 | -10 |
| 27 Aug 2026, 09:14 | 4,761 | -4 |
| 24 Aug 2026, 11:08 | 4,765 | first 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@saba_bio · 18,542
Telegram ranks this channel #8 of 53 here — alongside 52 others — read 5 October 2026
@UPSC_Prelim_Mains_Gk_Gs_Current · 208,789
Telegram ranks this channel #37 of 54 here — alongside 53 others — read 11 August 2026
@ipl_psl_toss_match · 44,422
Telegram ranks this channel #39 of 39 here — alongside 38 others — read 27 August 2026
@UPSC_Quiz_PRELIMS · 191,766
Telegram ranks this channel #47 of 57 here — alongside 56 others — read 11 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“YCT DIGI BOOK 2026” (@yct_digi_book), 4,577 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/yct_digi_book.
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.