Channel
Static GK and Current Affairs
@static_gk_current_affairs
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,167subscribers
-59 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 | -1001660158498 |
|---|---|
| Type | Channel |
| Username | @static_gk_current_affairs |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/static_gk_current_affairs |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 5 Nov 2026, 09:21 | 3,167 | -4 |
| 2 Nov 2026, 01:07 | 3,171 | -2 |
| 29 Oct 2026, 21:58 | 3,173 | -5 |
| 27 Oct 2026, 00:41 | 3,178 | -1 |
| 24 Oct 2026, 11:16 | 3,179 | +4 |
| 21 Oct 2026, 14:04 | 3,175 | -1 |
| 18 Oct 2026, 08:16 | 3,176 | +2 |
| 15 Oct 2026, 07:57 | 3,174 | -4 |
| 12 Oct 2026, 14:01 | 3,178 | -7 |
| 5 Oct 2026, 10:59 | 3,185 | -6 |
| 27 Sept 2026, 02:40 | 3,191 | -12 |
| 17 Sept 2026, 14:18 | 3,203 | -3 |
| 13 Sept 2026, 02:56 | 3,206 | -1 |
| 10 Sept 2026, 00:10 | 3,207 | no change |
| 8 Sept 2026, 19:15 | 3,207 | -4 |
| 3 Sept 2026, 20:55 | 3,211 | -5 |
| 31 Aug 2026, 08:02 | 3,216 | -1 |
| 28 Aug 2026, 05:13 | 3,217 | -1 |
| 25 Aug 2026, 00:11 | 3,218 | -2 |
| 21 Aug 2026, 22:26 | 3,220 | 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.
@kdlive · 158,497
Telegram ranks this channel #10 of 87 here — alongside 86 others — read 12 August 2026
@kdcampuschakde · 19,626
Telegram ranks this channel #18 of 64 here — alongside 63 others — read 30 September 2026
@kanpurwalavikrant · 34,714
Telegram ranks this channel #48 of 69 here — alongside 68 others — read 2 September 2026
This channel appears in 3 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“Static GK and Current Affairs” (@static_gk_current_affairs), 3,167 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/static_gk_current_affairs.
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.