Channel
SAMYAK IAS
@samyakiasjpr
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,950subscribers
+101 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 | -1002040703233 |
|---|---|
| Type | Channel |
| Username | @samyakiasjpr |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/samyakiasjpr |
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 14 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 20:14 | 3,950 | +7 |
| 3 Nov 2026, 12:16 | 3,943 | +6 |
| 31 Oct 2026, 13:28 | 3,937 | -9 |
| 28 Oct 2026, 13:45 | 3,946 | +6 |
| 25 Oct 2026, 05:25 | 3,940 | +1 |
| 21 Oct 2026, 23:29 | 3,939 | +2 |
| 18 Oct 2026, 17:31 | 3,937 | +12 |
| 15 Oct 2026, 12:30 | 3,925 | +2 |
| 12 Oct 2026, 11:06 | 3,923 | +17 |
| 5 Oct 2026, 21:57 | 3,906 | +18 |
| 28 Sept 2026, 21:22 | 3,888 | +29 |
| 19 Sept 2026, 05:19 | 3,859 | -7 |
| 11 Sept 2026, 02:17 | 3,866 | -1 |
| 6 Sept 2026, 01:57 | 3,867 | -13 |
| 6 Sept 2026, 00:08 | 3,880 | no change |
| 2 Sept 2026, 01:37 | 3,880 | +3 |
| 30 Aug 2026, 04:08 | 3,877 | -6 |
| 27 Aug 2026, 12:55 | 3,883 | -7 |
| 24 Aug 2026, 18:58 | 3,890 | +1 |
| 21 Aug 2026, 05:23 | 3,889 | 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.
@samyakiasjaipur · 45,066
Telegram ranks this channel #1 of 77 here — alongside 76 others — read 27 August 2026
@Studzify · 56,944
Telegram ranks this channel #15 of 53 here — alongside 52 others — read 27 August 2026
@Quality_Education_Exam · 39,598
Telegram ranks this channel #41 of 60 here — alongside 59 others — read 30 August 2026
@StraightRAS · 27,715
Telegram ranks this channel #51 of 64 here — alongside 63 others — read 11 September 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“SAMYAK IAS” (@samyakiasjpr), 3,950 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/samyakiasjpr.
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.