Channel
Gourav Uppal, AIR-174 UPSC CSE 2023
@gourav_uppal
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,066subscribers
+10 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002051336378 |
|---|---|
| Type | Channel |
| Username | @gourav_uppal |
| Description | Optional - Anthropology (score - 300) IG: https://www.instagram.com/gouravuppal_ips |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 September 2026 |
| Last confirmed live | 20 September 2026 |
| Measurements held | 10 |
| On Telegram | t.me/gourav_uppal |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Sept 2026, 02:11 | 2,066 | no change |
| 18 Sept 2026, 19:01 | 2,066 | -5 |
| 14 Sept 2026, 08:36 | 2,071 | -4 |
| 10 Sept 2026, 16:17 | 2,075 | -6 |
| 5 Sept 2026, 05:37 | 2,081 | -6 |
| 1 Sept 2026, 03:15 | 2,087 | -2 |
| 29 Aug 2026, 01:35 | 2,089 | +3 |
| 26 Aug 2026, 06:06 | 2,086 | +2 |
| 23 Aug 2026, 14:16 | 2,084 | +28 |
| 22 Aug 2026, 06:45 | 2,056 | 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.
@IASdwijgoel · 26,641
Telegram ranks this channel #25 of 70 here — alongside 69 others — read 12 September 2026
@aditya297ias · 33,525
Telegram ranks this channel #27 of 77 here — alongside 76 others — read 4 September 2026
@anthropology · 39,309
Telegram ranks this channel #33 of 75 here — alongside 74 others — read 31 August 2026
@AnimeshPradhan_AIR2 · 61,619
Telegram ranks this channel #43 of 78 here — alongside 77 others — read 22 August 2026
@DrNeha_anthropology · 24,943
Telegram ranks this channel #48 of 67 here — alongside 66 others — read 15 September 2026
@anthroguru · 28,438
Telegram ranks this channel #52 of 80 here — alongside 79 others — read 9 September 2026
This channel appears in 6 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 20 September 2026 — this entry's latest reading, not the date you are reading this.
“Gourav Uppal, AIR-174 UPSC CSE 2023” (@gourav_uppal), 2,066 subscribers as measured 20 September 2026. Telegram Register, tgregister.com/channel/gourav_uppal.
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.