Channel
arefemlk
@arefemlk
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,004subscribers
-608 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001713034149 |
|---|---|
| Type | Channel |
| Username | @arefemlk |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/arefemlk |
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 13 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 |
|---|---|---|
| 3 Nov 2026, 23:21 | 4,004 | -10 |
| 31 Oct 2026, 21:15 | 4,014 | -23 |
| 29 Oct 2026, 06:48 | 4,037 | -19 |
| 25 Oct 2026, 21:46 | 4,056 | -23 |
| 23 Oct 2026, 01:08 | 4,079 | -19 |
| 20 Oct 2026, 05:46 | 4,098 | -11 |
| 17 Oct 2026, 06:18 | 4,109 | -16 |
| 14 Oct 2026, 16:06 | 4,125 | -22 |
| 11 Oct 2026, 03:22 | 4,147 | -44 |
| 4 Oct 2026, 23:17 | 4,191 | -47 |
| 25 Sept 2026, 23:38 | 4,238 | -69 |
| 15 Sept 2026, 11:39 | 4,307 | -31 |
| 11 Sept 2026, 11:57 | 4,338 | -21 |
| 7 Sept 2026, 03:57 | 4,359 | -46 |
| 3 Sept 2026, 22:25 | 4,405 | no change |
| 2 Sept 2026, 13:08 | 4,405 | -12 |
| 30 Aug 2026, 16:15 | 4,417 | -11 |
| 28 Aug 2026, 02:08 | 4,428 | -25 |
| 25 Aug 2026, 03:04 | 4,453 | -36 |
| 21 Aug 2026, 09:44 | 4,489 | 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.
@shcafca · 31,825
Telegram ranks this channel #2 of 65 here — alongside 64 others — read 4 September 2026
@panahe_nabat · 44,104
Telegram ranks this channel #4 of 71 here — alongside 70 others — read 27 August 2026
@pishraftgra · 25,280
Telegram ranks this channel #6 of 59 here — alongside 58 others — read 12 September 2026
@englishwithfarimahh · 31,749
Telegram ranks this channel #15 of 53 here — alongside 52 others — read 6 September 2026
@Avin_hastam · 228,408
Telegram ranks this channel #19 of 74 here — alongside 73 others — read 11 August 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“arefemlk” (@arefemlk), 4,004 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/arefemlk.
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.