Channel
Judiciary Exams
@JudiciaryLawExams
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
7,565subscribers
+517 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001857647465 |
|---|---|
| Type | Channel |
| Username | @JudiciaryLawExams |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/JudiciaryLawExams |
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 12 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 05:19 | 7,565 | +99 |
| 13 Sept 2026, 04:59 | 7,466 | +34 |
| 9 Sept 2026, 07:16 | 7,432 | +85 |
| 4 Sept 2026, 04:18 | 7,347 | -45 |
| 31 Aug 2026, 10:35 | 7,392 | +36 |
| 28 Aug 2026, 15:24 | 7,356 | +17 |
| 26 Aug 2026, 21:04 | 7,339 | no change |
| 25 Aug 2026, 11:23 | 7,339 | +153 |
| 22 Aug 2026, 16:04 | 7,186 | +134 |
| 19 Aug 2026, 10:14 | 7,052 | +4 |
| 18 Aug 2026, 12:30 | 7,048 | 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.
@JudiciaryGold · 33,120
Telegram ranks this channel #6 of 65 here — alongside 64 others — read 4 September 2026
@UGCNET_JRF_NTA · 41,671
Telegram ranks this channel #10 of 72 here — alongside 71 others — read 29 August 2026
@Yojana_Kurukshetra_Magazines · 27,371
Telegram ranks this channel #15 of 77 here — alongside 76 others — read 11 September 2026
@theshubhamsir · 29,316
Telegram ranks this channel #15 of 73 here — alongside 72 others — read 8 September 2026
@pwlawwallah · 84,878
Telegram ranks this channel #17 of 77 here — alongside 76 others — read 18 August 2026
@LawPrepJudiciary · 23,837
Telegram ranks this channel #29 of 82 here — alongside 81 others — read 17 September 2026
This channel appears in 6 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Judiciary Exams” (@JudiciaryLawExams), 7,565 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/JudiciaryLawExams.
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.