Channel
Samhita ( charak + Ashtang hridaya )
@samhitaorashtang
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,123subscribers
+224 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001932665299 |
|---|---|
| Type | Channel |
| Username | @samhitaorashtang |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/samhitaorashtang |
Topic
Education — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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 |
|---|---|---|
| 6 Nov 2026, 07:19 | 2,123 | +6 |
| 3 Nov 2026, 13:18 | 2,117 | +8 |
| 31 Oct 2026, 08:49 | 2,109 | +4 |
| 28 Oct 2026, 17:57 | 2,105 | +7 |
| 25 Oct 2026, 21:50 | 2,098 | +6 |
| 23 Oct 2026, 00:00 | 2,092 | +15 |
| 20 Oct 2026, 00:16 | 2,077 | +5 |
| 17 Oct 2026, 08:28 | 2,072 | +9 |
| 14 Oct 2026, 17:00 | 2,063 | +12 |
| 11 Oct 2026, 03:01 | 2,051 | +30 |
| 5 Oct 2026, 07:16 | 2,021 | +28 |
| 26 Sept 2026, 20:58 | 1,993 | +23 |
| 21 Sept 2026, 02:26 | 1,970 | no change |
| 18 Sept 2026, 01:59 | 1,970 | +14 |
| 14 Sept 2026, 05:39 | 1,956 | +8 |
| 10 Sept 2026, 11:16 | 1,948 | +23 |
| 5 Sept 2026, 13:39 | 1,925 | +17 |
| 1 Sept 2026, 15:24 | 1,908 | +7 |
| 29 Aug 2026, 09:14 | 1,901 | +2 |
| 28 Aug 2026, 15:30 | 1,899 | 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.
@bams_notes_library · 21,341
Telegram ranks this channel #14 of 68 here — alongside 67 others — read 26 September 2026
@ayurveda_Sidhi · 55,775
Telegram ranks this channel #20 of 81 here — alongside 80 others — read 28 August 2026
@Ayurveda_bams_books · 24,723
Telegram ranks this channel #40 of 72 here — alongside 71 others — read 16 September 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Samhita ( charak + Ashtang hridaya )” (@samhitaorashtang), 2,123 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/samhitaorashtang.
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.