Channel
حباً للقراءة
@readbookscultural
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,704subscribers
+40 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001890732010 |
|---|---|
| Type | Channel |
| Username | @readbookscultural |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/readbookscultural |
Topic
Literature — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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 |
|---|---|---|
| 18 Sept 2026, 12:16 | 5,704 | -3 |
| 14 Sept 2026, 05:16 | 5,707 | +15 |
| 10 Sept 2026, 14:42 | 5,692 | +5 |
| 5 Sept 2026, 18:17 | 5,687 | +2 |
| 2 Sept 2026, 01:57 | 5,685 | +13 |
| 30 Aug 2026, 18:39 | 5,672 | no change |
| 29 Aug 2026, 19:26 | 5,672 | +2 |
| 26 Aug 2026, 16:24 | 5,670 | +4 |
| 23 Aug 2026, 06:47 | 5,666 | +12 |
| 19 Aug 2026, 19:58 | 5,654 | -7 |
| 16 Aug 2026, 14:47 | 5,661 | -3 |
| 15 Aug 2026, 08:21 | 5,664 | 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.
@TheBo0kN0ok · 28,441
Telegram ranks this channel #17 of 51 here — alongside 50 others — read 9 September 2026
@art_of_book · 36,534
Telegram ranks this channel #27 of 58 here — alongside 57 others — read 2 September 2026
@books_nour · 104,090
Telegram ranks this channel #39 of 73 here — alongside 72 others — read 15 August 2026
@DrHananMohamed · 24,566
Telegram ranks this channel #42 of 49 here — alongside 48 others — read 16 September 2026
@iqra2bk · 39,040
Telegram ranks this channel #44 of 56 here — alongside 55 others — read 31 August 2026
@katabatakatabata · 28,419
Telegram ranks this channel #49 of 64 here — alongside 63 others — read 9 September 2026
@quiz_moaser · 59,674
Telegram ranks this channel #81 of 82 here — alongside 81 others — read 23 August 2026
This channel appears in 7 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“حباً للقراءة” (@readbookscultural), 5,704 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/readbookscultural.
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.