Channel
GPSC WISDOM
@DYSOgoal2023
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,178subscribers
-208 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 | -1001854245677 |
|---|---|
| Type | Channel |
| Username | @DYSOgoal2023 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/DYSOgoal2023 |
Topic
Other / unclassifiable — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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 |
|---|---|---|
| 4 Nov 2026, 12:04 | 4,178 | -2 |
| 1 Nov 2026, 18:40 | 4,180 | -11 |
| 29 Oct 2026, 16:06 | 4,191 | -6 |
| 27 Oct 2026, 00:35 | 4,197 | -1 |
| 24 Oct 2026, 11:04 | 4,198 | -7 |
| 21 Oct 2026, 05:51 | 4,205 | -5 |
| 18 Oct 2026, 13:46 | 4,210 | -8 |
| 15 Oct 2026, 14:48 | 4,218 | -5 |
| 12 Oct 2026, 12:47 | 4,223 | -26 |
| 5 Oct 2026, 21:55 | 4,249 | -30 |
| 28 Sept 2026, 13:38 | 4,279 | -26 |
| 18 Sept 2026, 10:56 | 4,305 | -6 |
| 13 Sept 2026, 19:38 | 4,311 | -13 |
| 10 Sept 2026, 09:59 | 4,324 | -16 |
| 4 Sept 2026, 18:14 | 4,340 | -4 |
| 3 Sept 2026, 23:20 | 4,344 | no change |
| 1 Sept 2026, 08:07 | 4,344 | -14 |
| 29 Aug 2026, 05:25 | 4,358 | -5 |
| 26 Aug 2026, 04:33 | 4,363 | -7 |
| 23 Aug 2026, 13:19 | 4,370 | 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.
@toothepoint · 47,631
Telegram ranks this channel #20 of 77 here — alongside 76 others — read 26 August 2026
@UGC_NET_JRF_NTA_CSIR_SO · 144,295
Telegram ranks this channel #57 of 78 here — alongside 77 others — read 12 August 2026
@ganitreasoningmaths · 23,686
Telegram ranks this channel #64 of 73 here — alongside 72 others — read 18 September 2026
@becoming_ias_super_simplified · 38,363
Telegram ranks this channel #87 of 88 here — alongside 87 others — read 30 August 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“GPSC WISDOM” (@DYSOgoal2023), 4,178 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/DYSOgoal2023.
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.