Channel
Sanks
@sanketshah2105
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,186subscribers
-40 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002077136230 |
|---|---|
| Type | Channel |
| Username | @sanketshah2105 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 October 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/sanketshah2105 |
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 4 October 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 22:55 | 1,186 | -3 |
| 4 Oct 2026, 17:58 | 1,189 | no change |
| 25 Sept 2026, 17:02 | 1,189 | -4 |
| 12 Sept 2026, 18:01 | 1,193 | +6 |
| 8 Sept 2026, 22:36 | 1,187 | -11 |
| 3 Sept 2026, 10:47 | 1,198 | -4 |
| 31 Aug 2026, 01:24 | 1,202 | -5 |
| 27 Aug 2026, 19:28 | 1,207 | -5 |
| 24 Aug 2026, 16:59 | 1,212 | -4 |
| 17 Aug 2026, 12:43 | 1,216 | -5 |
| 14 Aug 2026, 09:28 | 1,221 | -3 |
| 11 Aug 2026, 07:38 | 1,224 | -2 |
| 10 Aug 2026, 16:45 | 1,226 | 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.
@fscayan · 61,772
Telegram ranks this channel #10 of 59 here — alongside 58 others — read 20 August 2026
@velaniparthofficial · 73,138
Telegram ranks this channel #11 of 59 here — alongside 58 others — read 19 August 2026
@TheFantasycricketgeek · 44,936
Telegram ranks this channel #21 of 74 here — alongside 73 others — read 27 August 2026
@SANDEEPNBA · 27,160
Telegram ranks this channel #26 of 66 here — alongside 65 others — read 10 September 2026
@Dream11Teamsfree8 · 46,780
Telegram ranks this channel #31 of 63 here — alongside 62 others — read 25 August 2026
@cricinformer · 263,067
Telegram ranks this channel #32 of 65 here — alongside 64 others — read 10 August 2026
@AakashChopraOfficial · 178,854
Telegram ranks this channel #33 of 63 here — alongside 62 others — read 11 August 2026
This channel appears in 7 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 October 2026 — this entry's latest reading, not the date you are reading this.
“Sanks” (@sanketshah2105), 1,186 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/sanketshah2105.
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.