Channel
Radio Sîtavk
@sitaavk
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,443subscribers
+61 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001858472482 |
|---|---|
| Type | Channel |
| Username | @sitaavk |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 2 times, most recently 4 November 2026 |
| On Telegram | t.me/sitaavk |
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 29 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 |
|---|---|---|
| 1 Nov 2026, 20:31 | 1,443 | +3 |
| 29 Oct 2026, 21:57 | 1,440 | +9 |
| 27 Oct 2026, 06:49 | 1,431 | -2 |
| 24 Oct 2026, 15:51 | 1,433 | -1 |
| 21 Oct 2026, 16:55 | 1,434 | -3 |
| 18 Oct 2026, 18:40 | 1,437 | +5 |
| 15 Oct 2026, 19:00 | 1,432 | +1 |
| 12 Oct 2026, 15:11 | 1,431 | +3 |
| 5 Oct 2026, 16:14 | 1,428 | +5 |
| 29 Sept 2026, 16:43 | 1,423 | no change |
| 28 Sept 2026, 11:20 | 1,423 | +2 |
| 15 Sept 2026, 13:21 | 1,421 | +5 |
| 12 Sept 2026, 06:40 | 1,416 | +5 |
| 8 Sept 2026, 11:42 | 1,411 | +2 |
| 3 Sept 2026, 06:09 | 1,409 | +2 |
| 31 Aug 2026, 00:28 | 1,407 | +11 |
| 28 Aug 2026, 06:37 | 1,396 | +8 |
| 25 Aug 2026, 13:43 | 1,388 | +6 |
| 21 Aug 2026, 14:15 | 1,382 | 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.
@LuxStreetCar · 30,480
Telegram ranks this channel #38 of 44 here — alongside 43 others — read 7 September 2026
@English_bi0 · 19,014
Telegram ranks this channel #48 of 65 here — alongside 64 others — read 2 October 2026
@Urmiyedang · 70,320
Telegram ranks this channel #59 of 73 here — alongside 72 others — read 22 August 2026
@majlese_tarhim · 65,940
Telegram ranks this channel #65 of 71 here — alongside 70 others — read 21 August 2026
@zana24urmiye · 31,057
Telegram ranks this channel #70 of 73 here — alongside 72 others — read 6 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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“Radio Sîtavk” (@sitaavk), 1,443 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/sitaavk.
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.