Channel
DJ MEHMET TEKIN
@DjMehmetTekin
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,664subscribers
+102 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001587503590 |
|---|---|
| Type | Channel |
| Username | @DjMehmetTekin |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 September 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/DjMehmetTekin |
Topic
Music — 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 26 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Oct 2026, 15:40 | 1,664 | +6 |
| 20 Oct 2026, 05:46 | 1,658 | -2 |
| 17 Oct 2026, 03:36 | 1,660 | +2 |
| 14 Oct 2026, 10:55 | 1,658 | +2 |
| 11 Oct 2026, 04:19 | 1,656 | +17 |
| 4 Oct 2026, 20:16 | 1,639 | +15 |
| 26 Sept 2026, 01:46 | 1,624 | no change |
| 25 Sept 2026, 00:39 | 1,624 | +13 |
| 16 Sept 2026, 11:40 | 1,611 | +3 |
| 12 Sept 2026, 20:02 | 1,608 | +5 |
| 8 Sept 2026, 16:19 | 1,603 | +6 |
| 3 Sept 2026, 12:35 | 1,597 | +6 |
| 30 Aug 2026, 22:36 | 1,591 | +6 |
| 28 Aug 2026, 03:54 | 1,585 | +4 |
| 25 Aug 2026, 07:32 | 1,581 | +7 |
| 22 Aug 2026, 13:53 | 1,574 | +7 |
| 19 Aug 2026, 01:44 | 1,567 | +2 |
| 15 Aug 2026, 20:37 | 1,565 | +3 |
| 11 Aug 2026, 21:21 | 1,562 | 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.
@moeinrabanian · 114,818
Telegram ranks this channel #55 of 59 here — alongside 58 others — read 23 September 2026
@nexdjcom · 21,352
Telegram ranks this channel #65 of 68 here — alongside 67 others — read 22 September 2026
@deej_danial · 85,014
Telegram ranks this channel #78 of 81 here — alongside 80 others — read 18 August 2026
@deejvans · 96,727
Telegram ranks this channel #79 of 84 here — alongside 83 others — read 17 August 2026
@dj_say · 186,566
Telegram ranks this channel #87 of 89 here — alongside 88 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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“DJ MEHMET TEKIN” (@DjMehmetTekin), 1,664 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/DjMehmetTekin.
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.