Telegram RegisterThe public register of Telegram
Telegram profile photo for UPSC CSE with PURU DUBEY(AIR 86)

Channel

UPSC CSE with PURU DUBEY(AIR 86)

@purudubey86

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

7,957subscribers

+731 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003806457244
TypeChannel
Username@purudubey86
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 August 2026
Last confirmed live17 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/purudubey86

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 100% 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

7,2267,9577,591.512 August 2026 — 7,226 subscribers13 August 2026 — 7,242 subscribers16 August 2026 — 7,349 subscribers19 August 2026 — 7,382 subscribers23 August 2026 — 7,444 subscribers26 August 2026 — 7,480 subscribers26 August 2026 — 7,480 subscribers29 August 2026 — 7,502 subscribers31 August 2026 — 7,523 subscribers4 September 2026 — 7,550 subscribers9 September 2026 — 7,717 subscribers13 September 2026 — 7,867 subscribers17 September 2026 — 7,957 subscribers12 August 202617 September 2026
13 measurements spanning 36 days, net +731. 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 7,116–8,067 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 17:377,957+90
13 Sept 2026, 22:417,867+150
9 Sept 2026, 23:177,717+167
4 Sept 2026, 21:367,550+27
31 Aug 2026, 21:127,523+21
29 Aug 2026, 03:147,502+22
26 Aug 2026, 17:587,480no change
26 Aug 2026, 01:087,480+36
23 Aug 2026, 02:377,444+62
19 Aug 2026, 04:227,382+33
16 Aug 2026, 14:377,349+107
13 Aug 2026, 02:347,242+16
12 Aug 2026, 16:457,226first reading

Engagement

No public post preview. We read this entry on 28 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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.

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

“UPSC CSE with PURU DUBEY(AIR 86)” (@purudubey86), 7,957 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/purudubey86.

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.