Channel
Cambridge 3 - 19
@reading_band_9
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,034subscribers
-146 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001635369574 |
|---|---|
| Type | Channel |
| Username | @reading_band_9 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/reading_band_9 |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 4 Nov 2026, 19:39 | 3,034 | -2 |
| 1 Nov 2026, 20:21 | 3,036 | -4 |
| 29 Oct 2026, 20:19 | 3,040 | -7 |
| 26 Oct 2026, 18:26 | 3,047 | -4 |
| 24 Oct 2026, 04:11 | 3,051 | -3 |
| 20 Oct 2026, 22:27 | 3,054 | +1 |
| 18 Oct 2026, 07:16 | 3,053 | -1 |
| 15 Oct 2026, 04:31 | 3,054 | +2 |
| 12 Oct 2026, 03:56 | 3,052 | -4 |
| 5 Oct 2026, 11:58 | 3,056 | -13 |
| 27 Sept 2026, 09:56 | 3,069 | -22 |
| 18 Sept 2026, 13:19 | 3,091 | -11 |
| 14 Sept 2026, 16:42 | 3,102 | -5 |
| 11 Sept 2026, 02:40 | 3,107 | -16 |
| 10 Sept 2026, 21:22 | 3,123 | no change |
| 6 Sept 2026, 11:38 | 3,123 | -8 |
| 2 Sept 2026, 10:25 | 3,131 | -9 |
| 30 Aug 2026, 12:26 | 3,140 | +6 |
| 27 Aug 2026, 10:17 | 3,134 | -11 |
| 24 Aug 2026, 07:38 | 3,145 | 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.
@cambridge_library · 128,940
Telegram ranks this channel #7 of 82 here — alongside 81 others — read 13 August 2026
@general_training_ielts · 22,814
Telegram ranks this channel #13 of 61 here — alongside 60 others — read 20 September 2026
@IELTS_CAMBRIDGE1 · 143,727
Telegram ranks this channel #27 of 83 here — alongside 82 others — read 13 August 2026
@ILETS_SPEAKING_PRACTICE · 20,578
Telegram ranks this channel #34 of 78 here — alongside 77 others — read 26 September 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Cambridge 3 - 19” (@reading_band_9), 3,034 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/reading_band_9.
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.