Channel
Hanuman Chalisa 💮 Bhakti Sagar💮 T-Series
@hanumanchalisa2020
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,022subscribers
-58 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001362327179 |
|---|---|
| Type | Channel |
| Username | @hanumanchalisa2020 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/hanumanchalisa2020 |
Topic
Religion — 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 13 September 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 |
|---|---|---|
| 8 Nov 2026, 04:08 | 5,022 | +9 |
| 5 Nov 2026, 02:45 | 5,013 | -5 |
| 2 Nov 2026, 01:57 | 5,018 | -4 |
| 30 Oct 2026, 09:47 | 5,022 | -7 |
| 27 Oct 2026, 01:20 | 5,029 | -2 |
| 24 Oct 2026, 01:48 | 5,031 | -4 |
| 18 Oct 2026, 01:19 | 5,035 | +2 |
| 15 Oct 2026, 06:57 | 5,033 | -11 |
| 12 Oct 2026, 04:21 | 5,044 | -22 |
| 5 Oct 2026, 18:40 | 5,066 | -22 |
| 27 Sept 2026, 20:37 | 5,088 | -2 |
| 18 Sept 2026, 14:38 | 5,090 | -2 |
| 14 Sept 2026, 00:39 | 5,092 | +4 |
| 10 Sept 2026, 17:39 | 5,088 | +5 |
| 5 Sept 2026, 19:41 | 5,083 | +1 |
| 1 Sept 2026, 16:13 | 5,082 | -1 |
| 1 Sept 2026, 12:17 | 5,083 | no change |
| 29 Aug 2026, 23:44 | 5,083 | -2 |
| 26 Aug 2026, 21:25 | 5,085 | +4 |
| 24 Aug 2026, 01:13 | 5,081 | 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.
@Hindi_Suvichar_Motivation_Quotes · 70,502
Telegram ranks this channel #40 of 44 here — alongside 43 others — read 19 August 2026
@SumitPharmacy · 31,757
Telegram ranks this channel #47 of 47 here — alongside 46 others — read 4 September 2026
@mahatetexam · 42,085
Telegram ranks this channel #62 of 65 here — alongside 64 others — read 29 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“Hanuman Chalisa 💮 Bhakti Sagar💮 T-Series” (@hanumanchalisa2020), 5,022 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/hanumanchalisa2020.
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.