Channel
концертный хаски
@husky_concert
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,143subscribers
+17 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001979067619 |
|---|---|
| Type | Channel |
| Username | @husky_concert |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 October 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/husky_concert |
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 6 October 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 |
|---|---|---|
| 7 Nov 2026, 18:07 | 1,143 | +3 |
| 4 Nov 2026, 09:16 | 1,140 | -1 |
| 1 Nov 2026, 01:18 | 1,141 | +1 |
| 29 Oct 2026, 11:55 | 1,140 | -2 |
| 24 Oct 2026, 01:59 | 1,142 | +4 |
| 21 Oct 2026, 10:11 | 1,138 | +1 |
| 18 Oct 2026, 13:01 | 1,137 | -2 |
| 15 Oct 2026, 13:48 | 1,139 | -4 |
| 12 Oct 2026, 21:28 | 1,143 | +3 |
| 6 Oct 2026, 01:56 | 1,140 | +1 |
| 6 Oct 2026, 01:36 | 1,139 | no change |
| 28 Sept 2026, 13:17 | 1,139 | -2 |
| 18 Sept 2026, 18:19 | 1,141 | +1 |
| 10 Sept 2026, 07:36 | 1,140 | +1 |
| 1 Sept 2026, 02:05 | 1,139 | +3 |
| 29 Aug 2026, 01:28 | 1,136 | -3 |
| 26 Aug 2026, 00:12 | 1,139 | +1 |
| 23 Aug 2026, 09:27 | 1,138 | -2 |
| 17 Aug 2026, 12:08 | 1,140 | +7 |
| 14 Aug 2026, 12:04 | 1,133 | 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.
@husky_spgs · 116,058
Telegram ranks this channel #7 of 75 here — alongside 74 others — read 8 September 2026
@papinomoloko · 19,442
Telegram ranks this channel #17 of 66 here — alongside 65 others — read 3 October 2026
@concerts_moscow · 48,941
Telegram ranks this channel #27 of 58 here — alongside 57 others — read 27 August 2026
This channel appears in 3 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“концертный хаски” (@husky_concert), 1,143 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/husky_concert.
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.