Channel
Neutron Crash Course 2024 SB
@Neutron_Crash_Course_Lect
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,035subscribers
-52 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001990143100 |
|---|---|
| Type | Channel |
| Username | @Neutron_Crash_Course_Lect |
| Description | ➻[𝐎𝐖𝐍𝐄𝐑] :- 〘 @batman1321 〙 ➻For Query. Contact. @NJR_HELP_BOT |
| Created | Between 1 July 2023 and 29 February 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 September 2026 |
| Last confirmed live | 20 September 2026 |
| Measurements held | 13 |
| On Telegram | t.me/Neutron_Crash_Course_Lect |
Topic
Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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 |
|---|---|---|
| 20 Sept 2026, 15:37 | 2,035 | no change |
| 15 Sept 2026, 21:58 | 2,035 | +1 |
| 12 Sept 2026, 03:57 | 2,034 | -7 |
| 7 Sept 2026, 13:42 | 2,041 | -3 |
| 2 Sept 2026, 23:39 | 2,044 | -9 |
| 31 Aug 2026, 00:15 | 2,053 | -4 |
| 28 Aug 2026, 03:42 | 2,057 | -3 |
| 24 Aug 2026, 22:05 | 2,060 | -12 |
| 20 Aug 2026, 21:43 | 2,072 | -7 |
| 17 Aug 2026, 15:35 | 2,079 | -2 |
| 14 Aug 2026, 09:49 | 2,081 | -5 |
| 8 Aug 2026, 01:42 | 2,086 | -1 |
| 7 Aug 2026, 12:21 | 2,087 | 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.
@PW_YAKEEN_NEET_LEGEND_2_0_2027z · 23,564
Telegram ranks this channel #11 of 38 here — alongside 37 others — read 19 September 2026
@BIHAR_DAROGA_BSSC_BPSC_72_AEDO_G · 190,492
Telegram ranks this channel #67 of 82 here — alongside 81 others — read 11 August 2026
This channel appears in 2 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 20 September 2026 — this entry's latest reading, not the date you are reading this.
“Neutron Crash Course 2024 SB” (@Neutron_Crash_Course_Lect), 2,035 subscribers as measured 20 September 2026. Telegram Register, tgregister.com/channel/Neutron_Crash_Course_Lect.
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.