
Channel
Khalife
@mehdikhalifee
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,964subscribers
-154 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001269421770 |
|---|---|
| Type | Channel |
| Username | @mehdikhalifee |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/mehdikhalifee |
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 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 |
|---|---|---|
| 17 Nov 2026, 06:58 | 2,964 | -6 |
| 11 Nov 2026, 12:04 | 2,970 | -6 |
| 8 Nov 2026, 03:07 | 2,976 | -7 |
| 4 Nov 2026, 22:48 | 2,983 | -4 |
| 1 Nov 2026, 14:12 | 2,987 | -5 |
| 29 Oct 2026, 22:35 | 2,992 | -8 |
| 26 Oct 2026, 11:44 | 3,000 | -2 |
| 23 Oct 2026, 11:27 | 3,002 | -2 |
| 20 Oct 2026, 20:56 | 3,004 | -6 |
| 17 Oct 2026, 09:30 | 3,010 | -8 |
| 14 Oct 2026, 06:39 | 3,018 | -2 |
| 10 Oct 2026, 18:57 | 3,020 | -5 |
| 4 Oct 2026, 18:39 | 3,025 | -22 |
| 24 Sept 2026, 20:37 | 3,047 | -17 |
| 16 Sept 2026, 07:17 | 3,064 | -8 |
| 12 Sept 2026, 19:17 | 3,072 | -6 |
| 10 Sept 2026, 23:46 | 3,078 | no change |
| 9 Sept 2026, 05:58 | 3,078 | -6 |
| 4 Sept 2026, 05:37 | 3,084 | -8 |
| 31 Aug 2026, 14:54 | 3,092 | 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.
@KABIMUSIC · 86,387
Telegram ranks this channel #16 of 75 here — alongside 74 others — read 18 August 2026
@zangekhass · 51,517
Telegram ranks this channel #20 of 46 here — alongside 45 others — read 24 August 2026
@turkmusic25 · 36,711
Telegram ranks this channel #31 of 75 here — alongside 74 others — read 2 September 2026
@arefdep · 59,400
Telegram ranks this channel #47 of 70 here — alongside 69 others — read 22 August 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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“Khalife” (@mehdikhalifee), 2,964 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/mehdikhalifee.
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.