Channel
Türki müzikleri
@venusla
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,236subscribers
+0 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001312908866 |
|---|---|
| Type | Channel |
| Username | @venusla |
| Description | آموزش روزانه مکالمه زبان ترکی استانبولی ونوس لینک اینستاگرام https://www.instagram.com/p/CiYBc6EovBd/?igshid=YmMyMTA2M2Y= لینک یوتوب https://www.youtube.com/channel/UCRWlKnQx1QUwaCw7b5fmb-w لینک کانال آموزش روزانه https://t.me/+odLKwtzfscFlMWRk |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 October 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 8 |
| On Telegram | t.me/venusla |
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 3 October 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 3 Oct 2026, 04:45 | 1,236 | no change |
| 18 Sept 2026, 03:17 | 1,236 | -4 |
| 13 Sept 2026, 13:41 | 1,240 | +3 |
| 9 Sept 2026, 12:15 | 1,237 | -1 |
| 4 Sept 2026, 11:39 | 1,238 | +2 |
| 1 Sept 2026, 00:14 | 1,236 | -1 |
| 29 Aug 2026, 06:25 | 1,237 | +1 |
| 28 Aug 2026, 10:30 | 1,236 | 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.
@turkish7en · 21,568
Telegram ranks this channel #16 of 62 here — alongside 61 others — read 23 September 2026
@ashpazieirani · 43,955
Telegram ranks this channel #36 of 66 here — alongside 65 others — read 28 August 2026
@salamat91 · 19,830
Telegram ranks this channel #43 of 62 here — alongside 61 others — read 30 September 2026
@healthy_yoga · 31,305
Telegram ranks this channel #55 of 78 here — alongside 77 others — read 6 September 2026
@ashpaziiy · 20,712
Telegram ranks this channel #56 of 65 here — alongside 64 others — read 26 September 2026
@chehel_salegi · 31,077
Telegram ranks this channel #79 of 87 here — alongside 86 others — read 6 September 2026
This channel appears in 6 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 October 2026 — this entry's latest reading, not the date you are reading this.
“Türki müzikleri” (@venusla), 1,236 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/venusla.
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.