Telegram RegisterThe public register of Telegram
Telegram profile photo for Hard Rock & Heavy Metal

Channel

Hard Rock & Heavy Metal

@metalfeed

On this record: Topic · Growth · Engagement · Cite this entry

1,088subscribers

+28 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001045467643
TypeChannel
Username@metalfeed
Created23 May 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 October 2026
Last confirmed live20 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 20 November 2026
On Telegramt.me/metalfeed

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 7 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

1,0551,0891,0725 August 2026 — 1,060 subscribers9 August 2026 — 1,059 subscribers13 August 2026 — 1,056 subscribers16 August 2026 — 1,055 subscribers19 August 2026 — 1,058 subscribers23 August 2026 — 1,061 subscribers27 August 2026 — 1,063 subscribers29 August 2026 — 1,064 subscribers1 September 2026 — 1,068 subscribers6 September 2026 — 1,065 subscribers11 September 2026 — 1,067 subscribers14 September 2026 — 1,073 subscribers19 September 2026 — 1,074 subscribers29 September 2026 — 1,082 subscribers6 October 2026 — 1,084 subscribers7 October 2026 — 1,084 subscribers13 October 2026 — 1,088 subscribers25 October 2026 — 1,089 subscribers31 October 2026 — 1,087 subscribers3 November 2026 — 1,089 subscribers6 November 2026 — 1,088 subscribers9 November 2026 — 1,085 subscribers15 November 2026 — 1,084 subscribers20 November 2026 — 1,088 subscribers1,0885 August 202620 November 2026
24 measurements spanning 106 days, net +28. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,050–1,094 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
20 Nov 2026, 00:511,088+4
15 Nov 2026, 01:301,084-1
9 Nov 2026, 17:361,085-3
6 Nov 2026, 00:211,088-1
3 Nov 2026, 06:281,089+2
31 Oct 2026, 12:281,087-2
25 Oct 2026, 09:271,089+1
13 Oct 2026, 00:391,088+4
7 Oct 2026, 04:291,084no change
6 Oct 2026, 21:201,084+2
29 Sept 2026, 18:181,082+8
19 Sept 2026, 14:011,074+1
14 Sept 2026, 19:201,073+6
11 Sept 2026, 00:381,067+2
6 Sept 2026, 00:181,065-3
1 Sept 2026, 22:361,068+4
29 Aug 2026, 23:251,064+1
27 Aug 2026, 02:481,063+2
23 Aug 2026, 21:251,061+3
19 Aug 2026, 19:151,058first 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.

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 20 November 2026 — this entry's latest reading, not the date you are reading this.

“Hard Rock & Heavy Metal” (@metalfeed), 1,088 subscribers as measured 20 November 2026. Telegram Register, tgregister.com/channel/metalfeed.

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.