Telegram RegisterThe public register of Telegram
Telegram profile photo for Lord Shiva Songs Bhajan

Channel

Lord Shiva Songs Bhajan

@shiv_bhajan

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

1,115subscribers

-19 since we began measuring on 4 October 2026

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

Register entry

Telegram ID-1001406183396
TypeChannel
Username@shiv_bhajan
CreatedBetween 1 January 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 October 2026
Last confirmed live3 November 2026
Measurements held9
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/shiv_bhajan

Topic

Religion — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 19 October 2026 and assigned it the closest of 31 fixed categories, at 94% 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,1151,1341,124.54 October 2026 — 1,134 subscribers6 October 2026 — 1,134 subscribers8 October 2026 — 1,133 subscribers13 October 2026 — 1,127 subscribers19 October 2026 — 1,123 subscribers22 October 2026 — 1,122 subscribers25 October 2026 — 1,119 subscribers28 October 2026 — 1,116 subscribers3 November 2026 — 1,115 subscribers4 October 20263 November 2026
9 measurements spanning 30 days, net -19. 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,112–1,137 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 16:111,115-1
28 Oct 2026, 23:051,116-3
25 Oct 2026, 23:161,119-3
22 Oct 2026, 20:411,122-1
19 Oct 2026, 17:471,123-4
13 Oct 2026, 23:191,127-6
8 Oct 2026, 14:381,133-1
6 Oct 2026, 03:411,134no change
4 Oct 2026, 09:471,134first 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.

HOMEOPATHY MEDICO NOTES 📚📚
@mediconot · 19,044
Telegram ranks this channel #65 of 78 here — alongside 77 others — read 4 October 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“Lord Shiva Songs Bhajan” (@shiv_bhajan), 1,115 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/shiv_bhajan.

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.