Channel
BY LUONG MUSIC
@byluong
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,785subscribers
+177 since we began measuring on 24 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001992023272 |
|---|---|
| Type | Channel |
| Username | @byluong |
| Created | Between 1 October 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/byluong |
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 73% 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 |
|---|---|---|
| 4 Nov 2026, 18:30 | 2,785 | +4 |
| 1 Nov 2026, 21:46 | 2,781 | +6 |
| 29 Oct 2026, 20:38 | 2,775 | +12 |
| 26 Oct 2026, 21:29 | 2,763 | +12 |
| 23 Oct 2026, 15:19 | 2,751 | +15 |
| 20 Oct 2026, 08:36 | 2,736 | +4 |
| 17 Oct 2026, 10:29 | 2,732 | +4 |
| 14 Oct 2026, 11:14 | 2,728 | +3 |
| 11 Oct 2026, 02:58 | 2,725 | +22 |
| 5 Oct 2026, 01:02 | 2,703 | +28 |
| 26 Sept 2026, 03:22 | 2,675 | +12 |
| 17 Sept 2026, 01:00 | 2,663 | +15 |
| 14 Sept 2026, 01:43 | 2,648 | no change |
| 12 Sept 2026, 18:21 | 2,648 | +2 |
| 8 Sept 2026, 17:58 | 2,646 | +10 |
| 3 Sept 2026, 10:09 | 2,636 | +12 |
| 31 Aug 2026, 12:05 | 2,624 | +9 |
| 28 Aug 2026, 15:23 | 2,615 | +6 |
| 25 Aug 2026, 05:38 | 2,609 | +1 |
| 24 Aug 2026, 19:30 | 2,608 | 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.
@Giaphanhacbayphong · 64,792
Telegram ranks this channel #10 of 24 here — alongside 23 others — read 2 September 2026
@tracknhac · 36,037
Telegram ranks this channel #10 of 26 here — alongside 25 others — read 2 September 2026
@NHACCUATUI23T · 23,556
Telegram ranks this channel #18 of 23 here — alongside 22 others — read 18 September 2026
@KenhNhacLotMusic · 105,785
Telegram ranks this channel #26 of 39 here — alongside 38 others — read 24 August 2026
This channel appears in 4 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“BY LUONG MUSIC” (@byluong), 2,785 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/byluong.
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.