Telegram RegisterThe public register of Telegram
Telegram profile photo for Govt. Schemes By 10MEXPERT IAS

Channel

Govt. Schemes By 10MEXPERT IAS

@Schemesforupsc

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

329subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001274675390
TypeChannel
Username@Schemesforupsc
CreatedBetween 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 15 October 2026
On Telegramt.me/Schemesforupsc

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 22 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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

3293333317 August 2026 — 333 subscribers7 August 2026 — 333 subscribers13 August 2026 — 332 subscribers20 August 2026 — 331 subscribers13 September 2026 — 329 subscribers25 September 2026 — 330 subscribers15 October 2026 — 329 subscribers7 August 202615 October 2026
7 measurements spanning 69 days, net -4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 328–334 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Oct 2026, 03:17329-1
25 Sept 2026, 20:21330+1
13 Sept 2026, 13:16329-2
20 Aug 2026, 11:24331-1
13 Aug 2026, 13:04332-1
7 Aug 2026, 04:31333no change
7 Aug 2026, 04:29333first reading

Engagement

16 posts held, back to 14 July 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 23 August 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

21 Aug 2022, 05:28 UTC913 viewsread 7 August 2026
Forwarded from @tipsforiasPhoto

Topic: Interaction with UPSC Topper IAS Divyansh Singh AIR 49 CSE 21 Time: Aug 21, 2022 12:00 PM India Join Zoom Meeting https://us05web.zoom.us/j/89467719072?pwd=VVM4SnJ2OHVuQm11bXFLeXJhUUJTQT09 Meeting ID: 894 6771 9072 Passcode: 10MEXPERT

20 Aug 2022, 05:24 UTC743 viewsread 7 August 2026
Forwarded from @tipsforiasPhoto

Topic: Interaction with UPSC Topper Rajesh Mourya AIR 367, CSE21 Time: Aug 20, 2022 11:00 AM India Join Zoom Meeting https://us05web.zoom.us/j/83259734488?pwd=eEk0SEpyUzk3TDlqNW5OQVd4eDhMZz09 Meeting ID: 832 5973 4488 Passcode: 10MEXPERT

16 Aug 2022, 05:23 UTC632 viewsread 7 August 2026
Forwarded from @tipsforiasPhoto

Topic: Interaction with UPSC Topper Shivam Chandra AIR 453, CSE21 Time: Aug 19, 2022 11:00 AM India Join Zoom Meeting https://us05web.zoom.us/j/87173365894?pwd=ZVIyeENIaWdLRmtFbE5LS3hMazNFQT09 Meeting ID: 871 7336 5894 Passcode: 10MEXPERT

9 Aug 2022, 10:54 UTC565 viewsread 7 August 2026
Forwarded from @tipsforiasPhoto

Topic: Interaction with UPSC Topper ROJA S RAJAN AIR 108, CSE21 Time: Aug 9, 2022 05:00 PM India Join Zoom Meeting https://us05web.zoom.us/j/89436530837?pwd=MG9LeGNpU0M1YXdXanRwd1A4bUQwQT09 Meeting ID: 894 3653 0837 Passcode: 10MEXPERT

5 Aug 2022, 11:06 UTC472 viewsread 7 August 2026

Topic: Interaction with UPSC Topper Anjali Shrotriya AIR 44, CSE21 Time: Aug 5, 2022 05:00 PM India Join Zoom Meeting https://us05web.zoom.us/j/85707360887?pwd=WkFGZm9mMjM5cjNOLzA5Y2dHVHF3QT09 Meeting ID: 857 0736 0887 Passcode: 10MEXPERT

30 Jul 2022, 10:09 UTC418 viewsread 7 August 2026
Forwarded from @tipsforiasPhoto

AGL- 300 [ Strategy planning of Next 300 Days with Daily Targets and Schedules ] . Visit - www.10mexpertias.com For Further Information and Broucher Pdf .

28 Jul 2022, 06:55 UTC372 viewsread 7 August 2026
Forwarded from @tipsforiasPhoto

Concluded with the above session !! Please wait for the recorded video. Thanks Shristi for this insightful session. @tipsforias

28 Jul 2022, 05:22 UTC327 viewsread 7 August 2026
Forwarded from @tipsforiasPhoto

Topic: Interaction with UPSC Topper Shristi Singh AIR 180 CSE21 Time: Jul 28, 2022 11:00 AM India Join Zoom Meeting https://us05web.zoom.us/j/83240252054?pwd=WUFacGtibG8rT1gwbFVXMk51VWFHQT09 Meeting ID: 832 4025 2054 Passcode: 10MEXPERT

26 Jul 2022, 07:03 UTC287 viewsread 7 August 2026
Forwarded from @tipsforiasPhoto

Concluded with the above session !! Please wait for the recorded video. Thanks Surbhi for this insightful session. Next session is on 28th July with Shristi singh , AIR 180 CSE21 @tipsforias

Showing the 12 most recent of 16 posts we hold for @Schemesforupsc. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 15 October 2026 — this entry's latest reading, not the date you are reading this.

“Govt. Schemes By 10MEXPERT IAS” (@Schemesforupsc), 329 subscribers as measured 15 October 2026. Telegram Register, tgregister.com/channel/Schemesforupsc.

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.