Channel
Easy_GKGS
@Easy_GKGS
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,248subscribers
-71 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002135994652 |
|---|---|
| Type | Channel |
| Username | @Easy_GKGS |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/Easy_GKGS |
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 17 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 15:58 | 2,248 | -1 |
| 30 Oct 2026, 18:27 | 2,249 | -5 |
| 27 Oct 2026, 19:41 | 2,254 | -3 |
| 24 Oct 2026, 14:55 | 2,257 | -1 |
| 21 Oct 2026, 04:37 | 2,258 | -2 |
| 18 Oct 2026, 04:06 | 2,260 | +1 |
| 15 Oct 2026, 08:16 | 2,259 | -8 |
| 12 Oct 2026, 13:35 | 2,267 | -16 |
| 5 Oct 2026, 18:40 | 2,283 | -7 |
| 27 Sept 2026, 19:40 | 2,290 | -12 |
| 17 Sept 2026, 15:26 | 2,302 | no change |
| 15 Sept 2026, 12:00 | 2,302 | -6 |
| 11 Sept 2026, 13:36 | 2,308 | -4 |
| 7 Sept 2026, 05:18 | 2,312 | -4 |
| 2 Sept 2026, 07:34 | 2,316 | -2 |
| 30 Aug 2026, 17:45 | 2,318 | -3 |
| 27 Aug 2026, 10:35 | 2,321 | +2 |
| 24 Aug 2026, 18:07 | 2,319 | +3 |
| 18 Aug 2026, 05:34 | 2,316 | -2 |
| 14 Aug 2026, 21:54 | 2,318 | 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.
@ChetanSaxena · 24,058
Telegram ranks this channel #9 of 70 here — alongside 69 others — read 16 September 2026
@EnglishByBinodSharma · 26,002
Telegram ranks this channel #18 of 71 here — alongside 70 others — read 25 September 2026
@naman21 · 25,231
Telegram ranks this channel #22 of 59 here — alongside 58 others — read 16 September 2026
@varunawasthiGS · 238,558
Telegram ranks this channel #58 of 85 here — alongside 84 others — read 11 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total, of which the 4 where it ranks highest are shown above. 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“Easy_GKGS” (@Easy_GKGS), 2,248 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/Easy_GKGS.
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.