Telegram RegisterThe public register of Telegram
Telegram profile photo for UPPSC Mains 5&6

Supergroup

UPPSC Mains 5&6

@UPPSCMAINSS

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

2,747members

+9 since we began measuring on 21 August 2026

265 online right now

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

Register entry

Telegram ID-1002082886458
TypeSupergroup
Username@UPPSCMAINSS
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 September 2026
Last confirmed live23 October 2026
Measurements held15
Confirmed unchanged2 times, most recently 23 October 2026
On Telegramt.me/UPPSCMAINSS

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 15 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

2,7332,7552,74421 August 2026 — 2,738 members21 August 2026 — 2,737 members25 August 2026 — 2,734 members28 August 2026 — 2,733 members31 August 2026 — 2,734 members4 September 2026 — 2,741 members9 September 2026 — 2,745 members13 September 2026 — 2,745 members17 September 2026 — 2,749 members27 September 2026 — 2,755 members5 October 2026 — 2,753 members12 October 2026 — 2,749 members15 October 2026 — 2,746 members18 October 2026 — 2,749 members20 October 2026 — 2,747 members2,74721 August 202620 October 2026
15 measurements spanning 60 days, net +9. 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 2,730–2,758 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
20 Oct 2026, 17:092,747-2
18 Oct 2026, 00:382,749+3
15 Oct 2026, 09:282,746-3
12 Oct 2026, 07:542,749-4
5 Oct 2026, 08:212,753-2
27 Sept 2026, 09:152,755+6
17 Sept 2026, 19:172,749+4
13 Sept 2026, 14:322,745no change
9 Sept 2026, 07:562,745+4
4 Sept 2026, 02:382,741+7
31 Aug 2026, 06:322,734+1
28 Aug 2026, 01:342,733-1
25 Aug 2026, 01:332,734-3
21 Aug 2026, 20:062,737-1
21 Aug 2026, 08:452,738first 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.

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

“UPPSC Mains 5&6” (@UPPSCMAINSS), 2,747 members as measured 20 October 2026. Telegram Register, tgregister.com/channel/UPPSCMAINSS.

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.