Channel
Arefe English Channel
@Arefe_English
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,711subscribers
-46 since we began measuring on 24 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002167437289 |
|---|---|
| Type | Channel |
| Username | @Arefe_English |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/Arefe_English |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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, 21:15 | 1,711 | -1 |
| 4 Nov 2026, 17:31 | 1,712 | -2 |
| 1 Nov 2026, 13:46 | 1,714 | -7 |
| 29 Oct 2026, 06:21 | 1,721 | -1 |
| 26 Oct 2026, 06:47 | 1,722 | +1 |
| 22 Oct 2026, 22:39 | 1,721 | -1 |
| 19 Oct 2026, 12:19 | 1,722 | -4 |
| 16 Oct 2026, 19:10 | 1,726 | -4 |
| 13 Oct 2026, 12:30 | 1,730 | -1 |
| 7 Oct 2026, 20:59 | 1,731 | -4 |
| 1 Oct 2026, 13:01 | 1,735 | -4 |
| 24 Sept 2026, 02:30 | 1,739 | no change |
| 16 Sept 2026, 07:00 | 1,739 | -6 |
| 8 Sept 2026, 20:56 | 1,745 | -1 |
| 3 Sept 2026, 16:40 | 1,746 | -3 |
| 31 Aug 2026, 04:08 | 1,749 | -5 |
| 28 Aug 2026, 09:42 | 1,754 | -3 |
| 24 Aug 2026, 22:30 | 1,757 | 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.
@podcasts_english · 19,250
Telegram ranks this channel #21 of 77 here — alongside 76 others — read 1 October 2026
@fereshte_irannezhadd · 24,864
Telegram ranks this channel #43 of 55 here — alongside 54 others — read 14 September 2026
@SaharCast · 34,036
Telegram ranks this channel #44 of 90 here — alongside 89 others — read 3 September 2026
@RMS_English · 53,745
Telegram ranks this channel #50 of 84 here — alongside 83 others — read 24 August 2026
@GermanyPargar · 34,713
Telegram ranks this channel #55 of 76 here — alongside 75 others — read 3 September 2026
This channel appears in 5 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.
“Arefe English Channel” (@Arefe_English), 1,711 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/Arefe_English.
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.