Channel
leberya music 🎧
@leberya
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,891subscribers
-183 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002136546455 |
|---|---|
| Type | Channel |
| Username | @leberya |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/leberya |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 3 Nov 2026, 06:40 | 2,891 | -3 |
| 31 Oct 2026, 05:30 | 2,894 | -2 |
| 28 Oct 2026, 07:28 | 2,896 | -5 |
| 25 Oct 2026, 07:37 | 2,901 | -8 |
| 22 Oct 2026, 02:55 | 2,909 | -8 |
| 18 Oct 2026, 16:26 | 2,917 | -7 |
| 15 Oct 2026, 15:22 | 2,924 | -6 |
| 13 Oct 2026, 00:00 | 2,930 | -19 |
| 6 Oct 2026, 19:38 | 2,949 | -10 |
| 29 Sept 2026, 15:20 | 2,959 | -24 |
| 19 Sept 2026, 07:40 | 2,983 | -11 |
| 15 Sept 2026, 06:16 | 2,994 | -3 |
| 11 Sept 2026, 22:42 | 2,997 | -12 |
| 11 Sept 2026, 14:01 | 3,009 | no change |
| 7 Sept 2026, 08:54 | 3,009 | -16 |
| 2 Sept 2026, 21:24 | 3,025 | -8 |
| 31 Aug 2026, 03:54 | 3,033 | -5 |
| 28 Aug 2026, 14:34 | 3,038 | -5 |
| 25 Aug 2026, 05:37 | 3,043 | -10 |
| 22 Aug 2026, 12:05 | 3,053 | 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.
@nabz_text_music · 55,129
Telegram ranks this channel #11 of 59 here — alongside 58 others — read 23 August 2026
@batis_graphichanel · 25,821
Telegram ranks this channel #15 of 57 here — alongside 56 others — read 11 September 2026
@AHANGE_DEEP · 64,789
Telegram ranks this channel #38 of 65 here — alongside 64 others — read 23 August 2026
@Koucheyedel · 26,922
Telegram ranks this channel #39 of 69 here — alongside 68 others — read 14 September 2026
@zakiwmusic · 5
Telegram ranks this channel #74 of 82 here — alongside 81 others — read 15 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“leberya music 🎧” (@leberya), 2,891 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/leberya.
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.