Channel
𝙃𝙖𝙢𝙘𝙡𝙪𝙗𝙮
@hamclluby
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,169subscribers
-60 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001757028529 |
|---|---|
| Type | Channel |
| Username | @hamclluby |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 October 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/hamclluby |
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 4 October 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 23:39 | 1,169 | -2 |
| 4 Nov 2026, 09:49 | 1,171 | -2 |
| 1 Nov 2026, 12:46 | 1,173 | -1 |
| 26 Oct 2026, 18:45 | 1,174 | -1 |
| 23 Oct 2026, 12:00 | 1,175 | -3 |
| 20 Oct 2026, 15:36 | 1,178 | -4 |
| 17 Oct 2026, 13:50 | 1,182 | -4 |
| 15 Oct 2026, 00:26 | 1,186 | -4 |
| 11 Oct 2026, 23:57 | 1,190 | -5 |
| 5 Oct 2026, 11:20 | 1,195 | -7 |
| 4 Oct 2026, 04:13 | 1,202 | no change |
| 27 Sept 2026, 17:57 | 1,202 | -5 |
| 17 Sept 2026, 23:55 | 1,207 | -4 |
| 13 Sept 2026, 15:39 | 1,211 | -3 |
| 10 Sept 2026, 05:57 | 1,214 | -5 |
| 5 Sept 2026, 07:39 | 1,219 | -3 |
| 1 Sept 2026, 15:38 | 1,222 | -1 |
| 29 Aug 2026, 14:05 | 1,223 | -4 |
| 26 Aug 2026, 10:24 | 1,227 | -2 |
| 22 Aug 2026, 19:45 | 1,229 | 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.
@babizhoon · 18,123
Telegram ranks this channel #17 of 66 here — alongside 65 others — read 4 October 2026
@exchangerafiei · 54,742
Telegram ranks this channel #63 of 76 here — alongside 75 others — read 22 August 2026
This channel appears in 2 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“𝙃𝙖𝙢𝙘𝙡𝙪𝙗𝙮” (@hamclluby), 1,169 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/hamclluby.
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.