Channel
RKh_Music
@rkh_music
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,886subscribers
-32 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001919578624 |
|---|---|
| Type | Channel |
| Username | @rkh_music |
| Description | Instagram: rkh.music YouTube: ReZaKh_Music |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 September 2026 |
| Last confirmed live | 22 September 2026 |
| Measurements held | 14 |
| On Telegram | t.me/rkh_music |
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 22 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 |
|---|---|---|
| 22 Sept 2026, 02:36 | 1,886 | no change |
| 19 Sept 2026, 17:37 | 1,886 | -1 |
| 15 Sept 2026, 14:38 | 1,887 | -2 |
| 12 Sept 2026, 01:19 | 1,889 | +1 |
| 7 Sept 2026, 17:01 | 1,888 | -3 |
| 2 Sept 2026, 10:56 | 1,891 | -1 |
| 30 Aug 2026, 19:02 | 1,892 | -4 |
| 27 Aug 2026, 08:43 | 1,896 | -4 |
| 20 Aug 2026, 14:58 | 1,900 | -2 |
| 17 Aug 2026, 20:18 | 1,902 | -8 |
| 14 Aug 2026, 09:54 | 1,910 | -2 |
| 11 Aug 2026, 05:05 | 1,912 | -3 |
| 7 Aug 2026, 23:06 | 1,915 | -3 |
| 7 Aug 2026, 15:24 | 1,918 | 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.
@musicttrend · 76,933
Telegram ranks this channel #8 of 59 here — alongside 58 others — read 19 August 2026
@OfficialShadmehr · 36,342
Telegram ranks this channel #22 of 83 here — alongside 82 others — read 1 September 2026
@pmc_org · 24,987
Telegram ranks this channel #23 of 65 here — alongside 64 others — read 15 September 2026
@CookBTCcom · 48,920
Telegram ranks this channel #25 of 76 here — alongside 75 others — read 25 August 2026
@tiamo_music · 98,953
Telegram ranks this channel #48 of 81 here — alongside 80 others — read 15 August 2026
@shimamuzic · 31,316
Telegram ranks this channel #70 of 85 here — alongside 84 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 22 September 2026 — this entry's latest reading, not the date you are reading this.
“RKh_Music” (@rkh_music), 1,886 subscribers as measured 22 September 2026. Telegram Register, tgregister.com/channel/rkh_music.
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.