Channel
RAJEEV REASONING
@rajeevreasoning
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,552subscribers
-200 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001368828247 |
|---|---|
| Type | Channel |
| Username | @rajeevreasoning |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/rajeevreasoning |
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 65% 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 |
|---|---|---|
| 5 Nov 2026, 15:39 | 5,552 | -7 |
| 2 Nov 2026, 10:46 | 5,559 | -7 |
| 30 Oct 2026, 16:46 | 5,566 | -8 |
| 28 Oct 2026, 01:39 | 5,574 | -15 |
| 21 Oct 2026, 20:29 | 5,589 | -15 |
| 18 Oct 2026, 05:46 | 5,604 | -8 |
| 15 Oct 2026, 12:21 | 5,612 | -4 |
| 12 Oct 2026, 03:38 | 5,616 | -8 |
| 5 Oct 2026, 16:20 | 5,624 | -26 |
| 27 Sept 2026, 19:16 | 5,650 | -17 |
| 15 Sept 2026, 14:37 | 5,667 | -10 |
| 11 Sept 2026, 15:18 | 5,677 | -15 |
| 6 Sept 2026, 22:36 | 5,692 | -17 |
| 2 Sept 2026, 14:23 | 5,709 | -11 |
| 30 Aug 2026, 18:27 | 5,720 | -11 |
| 30 Aug 2026, 11:56 | 5,731 | no change |
| 28 Aug 2026, 03:12 | 5,731 | -6 |
| 24 Aug 2026, 18:57 | 5,737 | -8 |
| 20 Aug 2026, 22:35 | 5,745 | -3 |
| 17 Aug 2026, 13:44 | 5,748 | 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.
@SuryawanshiRajender · 20,663
Telegram ranks this channel #23 of 34 here — alongside 33 others — read 1 October 2026
@Magadh_University_News · 34,573
Telegram ranks this channel #55 of 65 here — alongside 64 others — read 2 September 2026
@GayaCollegeInfo · 34,582
Telegram ranks this channel #58 of 65 here — alongside 64 others — read 2 September 2026
@Magadh_University_Bodhgaya · 126,766
Telegram ranks this channel #76 of 83 here — alongside 82 others — read 13 August 2026
This channel appears in 4 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“RAJEEV REASONING” (@rajeevreasoning), 5,552 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/rajeevreasoning.
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.