
Channel
Anglteacher
@anglteacher
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,328subscribers
-177 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001799883040 |
|---|---|
| Type | Channel |
| Username | @anglteacher |
| Created | Between 1 May 2022 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/anglteacher |
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 |
|---|---|---|
| 12 Nov 2026, 00:46 | 5,328 | -9 |
| 7 Nov 2026, 23:06 | 5,337 | -9 |
| 4 Nov 2026, 16:40 | 5,346 | -2 |
| 2 Nov 2026, 00:09 | 5,348 | -8 |
| 30 Oct 2026, 07:19 | 5,356 | -4 |
| 26 Oct 2026, 23:40 | 5,360 | -7 |
| 24 Oct 2026, 10:17 | 5,367 | -8 |
| 21 Oct 2026, 14:10 | 5,375 | -5 |
| 18 Oct 2026, 18:56 | 5,380 | -7 |
| 16 Oct 2026, 04:16 | 5,387 | -5 |
| 12 Oct 2026, 23:46 | 5,392 | -16 |
| 6 Oct 2026, 05:20 | 5,408 | -21 |
| 29 Sept 2026, 11:18 | 5,429 | -19 |
| 19 Sept 2026, 01:58 | 5,448 | -8 |
| 14 Sept 2026, 10:21 | 5,456 | -6 |
| 10 Sept 2026, 22:35 | 5,462 | -6 |
| 6 Sept 2026, 06:55 | 5,468 | -6 |
| 2 Sept 2026, 01:57 | 5,474 | -10 |
| 30 Aug 2026, 22:46 | 5,484 | no change |
| 29 Aug 2026, 21:53 | 5,484 | 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.
@learn_repeat_check · 29,566
Telegram ranks this channel #20 of 68 here — alongside 67 others — read 7 September 2026
@eng_every_day · 74,743
Telegram ranks this channel #29 of 82 here — alongside 81 others — read 19 August 2026
@eng_for_all · 43,354
Telegram ranks this channel #34 of 74 here — alongside 73 others — read 28 August 2026
@englishkuzmina · 28,663
Telegram ranks this channel #84 of 93 here — alongside 92 others — read 9 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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“Anglteacher” (@anglteacher), 5,328 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/anglteacher.
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.