Channel
TARUN sir Nuetron Lectures
@Tarun_sir_botany_Neutron_lecture
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
6,121subscribers
+430 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 | -1002062335637 |
|---|---|
| Type | Channel |
| Username | @Tarun_sir_botany_Neutron_lecture |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/Tarun_sir_botany_Neutron_lecture |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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, 08:39 | 6,121 | -17 |
| 14 Sept 2026, 06:57 | 6,138 | -19 |
| 11 Sept 2026, 01:00 | 6,157 | -47 |
| 5 Sept 2026, 22:58 | 6,204 | -33 |
| 2 Sept 2026, 03:56 | 6,237 | -51 |
| 29 Aug 2026, 22:55 | 6,288 | +241 |
| 29 Aug 2026, 19:21 | 6,047 | no change |
| 26 Aug 2026, 23:57 | 6,047 | -51 |
| 24 Aug 2026, 08:08 | 6,098 | +229 |
| 20 Aug 2026, 09:12 | 5,869 | +178 |
| 19 Aug 2026, 09:15 | 5,691 | 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.
@Dr_Manish_Dubey_MD_Sir_BMS · 38,968
Telegram ranks this channel #22 of 47 here — alongside 46 others — read 30 August 2026
@MohitsirpwIOC · 65,001
Telegram ranks this channel #23 of 41 here — alongside 40 others — read 30 August 2026
@sankalpneetvedantu · 75,541
Telegram ranks this channel #26 of 44 here — alongside 43 others — read 19 August 2026
@faisalsirpwgoatarmy · 24,605
Telegram ranks this channel #39 of 42 here — alongside 41 others — read 15 September 2026
@Biologybyvipinsir8 · 74,530
Telegram ranks this channel #40 of 44 here — alongside 43 others — read 19 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.
“TARUN sir Nuetron Lectures” (@Tarun_sir_botany_Neutron_lecture), 6,121 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Tarun_sir_botany_Neutron_lecture.
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.