Channel
Clat material community🚀
@Vidhigya_MB
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,554subscribers
+97 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002054165663 |
|---|---|
| Type | Channel |
| Username | @Vidhigya_MB |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/Vidhigya_MB |
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 94% 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 |
|---|---|---|
| 19 Sept 2026, 12:15 | 3,554 | +16 |
| 15 Sept 2026, 02:01 | 3,538 | +10 |
| 11 Sept 2026, 13:00 | 3,528 | +15 |
| 8 Sept 2026, 00:27 | 3,513 | no change |
| 6 Sept 2026, 17:39 | 3,513 | +25 |
| 1 Sept 2026, 04:15 | 3,488 | +24 |
| 25 Aug 2026, 22:19 | 3,464 | +7 |
| 22 Aug 2026, 14:45 | 3,457 | 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.
@law_exam_clat_legal_lsat_pdf · 58,910
Telegram ranks this channel #19 of 59 here — alongside 58 others — read 22 August 2026
@twelveminutestoclat · 27,541
Telegram ranks this channel #33 of 50 here — alongside 49 others — read 10 September 2026
@IBPS_RRB_PO_CLERK_Exam_PDF_Notes · 55,515
Telegram ranks this channel #36 of 66 here — alongside 65 others — read 23 August 2026
@originclat · 27,652
Telegram ranks this channel #40 of 57 here — alongside 56 others — read 10 September 2026
@LegalEdge · 47,345
Telegram ranks this channel #40 of 55 here — alongside 54 others — read 27 August 2026
@GK_Today_PDF · 38,725
Telegram ranks this channel #47 of 71 here — alongside 70 others — read 31 August 2026
@lawpreptutorial · 40,950
Telegram ranks this channel #48 of 57 here — alongside 56 others — read 30 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Clat material community🚀” (@Vidhigya_MB), 3,554 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Vidhigya_MB.
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.