Channel
Shastra Manthan 🕉
@Shastra_Manthan
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,833subscribers
+104 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001581635314 |
|---|---|
| Type | Channel |
| Username | @Shastra_Manthan |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/Shastra_Manthan |
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 14 September 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 02:39 | 3,833 | +18 |
| 13 Sept 2026, 23:38 | 3,815 | +10 |
| 10 Sept 2026, 11:36 | 3,805 | +19 |
| 6 Sept 2026, 20:51 | 3,786 | no change |
| 5 Sept 2026, 10:57 | 3,786 | +5 |
| 1 Sept 2026, 16:13 | 3,781 | +9 |
| 29 Aug 2026, 09:56 | 3,772 | +8 |
| 26 Aug 2026, 08:26 | 3,764 | +5 |
| 23 Aug 2026, 12:09 | 3,759 | +9 |
| 20 Aug 2026, 07:35 | 3,750 | -1 |
| 17 Aug 2026, 11:38 | 3,751 | +7 |
| 14 Aug 2026, 10:19 | 3,744 | +12 |
| 11 Aug 2026, 02:02 | 3,732 | +3 |
| 7 Aug 2026, 12:23 | 3,729 | 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.
@theilluminatishow · 23,741
Telegram ranks this channel #34 of 58 here — alongside 57 others — read 17 September 2026
@Ayurveda_Yoga_Meditation · 43,410
Telegram ranks this channel #46 of 72 here — alongside 71 others — read 28 August 2026
@Brahmacharya · 34,888
Telegram ranks this channel #53 of 69 here — alongside 68 others — read 2 September 2026
@CSEUPSCPrelims · 56,604
Telegram ranks this channel #74 of 76 here — alongside 75 others — read 23 August 2026
@dhyeya_ias_study_material · 79,079
Telegram ranks this channel #77 of 80 here — alongside 79 others — read 18 August 2026
This channel appears in 5 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Shastra Manthan 🕉” (@Shastra_Manthan), 3,833 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Shastra_Manthan.
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.