Channel
low bass
@low_bassss
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,754subscribers
+351 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001591010609 |
|---|---|
| Type | Channel |
| Username | @low_bassss |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/low_bassss |
Topic
Other / unclassifiable — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 8 Nov 2026, 09:06 | 2,754 | +21 |
| 5 Nov 2026, 13:55 | 2,733 | +6 |
| 2 Nov 2026, 22:39 | 2,727 | +22 |
| 31 Oct 2026, 08:27 | 2,705 | +8 |
| 28 Oct 2026, 18:11 | 2,697 | +19 |
| 26 Oct 2026, 04:09 | 2,678 | +21 |
| 19 Oct 2026, 16:05 | 2,657 | +17 |
| 16 Oct 2026, 09:29 | 2,640 | +4 |
| 13 Oct 2026, 06:28 | 2,636 | +39 |
| 6 Oct 2026, 17:59 | 2,597 | +38 |
| 29 Sept 2026, 20:18 | 2,559 | +39 |
| 19 Sept 2026, 17:37 | 2,520 | +36 |
| 16 Sept 2026, 00:04 | 2,484 | no change |
| 15 Sept 2026, 02:14 | 2,484 | +30 |
| 11 Sept 2026, 07:41 | 2,454 | +13 |
| 6 Sept 2026, 19:58 | 2,441 | +16 |
| 2 Sept 2026, 12:45 | 2,425 | +15 |
| 30 Aug 2026, 02:05 | 2,410 | +7 |
| 26 Aug 2026, 23:45 | 2,403 | 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.
@BassRazuvaev · 25,216
Telegram ranks this channel #4 of 34 here — alongside 33 others — read 24 September 2026
@bass_matrix · 57,662
Telegram ranks this channel #14 of 52 here — alongside 51 others — read 26 August 2026
@vbassclub · 31,552
Telegram ranks this channel #16 of 46 here — alongside 45 others — read 6 September 2026
@Carrozzeria_music · 17,577
Telegram ranks this channel #34 of 34 here — alongside 33 others — read 6 September 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“low bass” (@low_bassss), 2,754 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/low_bassss.
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.