Channel
Trilhas Sonoras
@TrilhasSonoras
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,572subscribers
+7 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001022400884 |
|---|---|
| Type | Channel |
| Username | @TrilhasSonoras |
| Created | 5 January 2016 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 7 September 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/TrilhasSonoras |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 16 Sept 2026, 10:19 | 3,572 | +4 |
| 12 Sept 2026, 19:38 | 3,568 | +4 |
| 8 Sept 2026, 16:56 | 3,564 | +4 |
| 7 Sept 2026, 23:16 | 3,560 | no change |
| 2 Sept 2026, 23:47 | 3,560 | -1 |
| 28 Aug 2026, 02:45 | 3,561 | +4 |
| 24 Aug 2026, 23:26 | 3,557 | +1 |
| 21 Aug 2026, 15:35 | 3,556 | -2 |
| 18 Aug 2026, 09:33 | 3,558 | +2 |
| 15 Aug 2026, 15:12 | 3,556 | -7 |
| 12 Aug 2026, 02:08 | 3,563 | -1 |
| 9 Aug 2026, 02:01 | 3,564 | -1 |
| 5 Aug 2026, 21:18 | 3,565 | 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.
@clubedamente · 31,938
Telegram ranks this channel #12 of 12 here — alongside 11 others — read 5 September 2026
@adoramosromancesebook · 37,248
Telegram ranks this channel #17 of 24 here — alongside 23 others — read 1 September 2026
@AprendendoIngles · 33,653
Telegram ranks this channel #19 of 44 here — alongside 43 others — read 4 September 2026
@popcornportal · 101,900
Telegram ranks this channel #24 of 47 here — alongside 46 others — read 16 August 2026
@redacaoplay · 22,807
Telegram ranks this channel #29 of 37 here — alongside 36 others — read 19 September 2026
@TrailersBR · 114,329
Telegram ranks this channel #37 of 44 here — alongside 43 others — read 16 August 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Trilhas Sonoras” (@TrilhasSonoras), 3,572 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/TrilhasSonoras.
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.