Channel
🎓حقوقی های آزاد🎓
@justice_law98
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,787subscribers
-16 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001029003924 |
|---|---|
| Type | Channel |
| Username | @justice_law98 |
| Description | کانال حقوقی های آزاد تاسیس: دی ١٣٩۴ ویژه دانشجویان و فارغ التحصیلان حقوق جزوات،کتاب، فایل های صوتی، مقالات، نکات حقوقی و کاربردی به بیان ساده ارائه اخبار و آزمون های حقوقی و هر آنچه یک شخص باید از حقوق بداند https://t.me/iHarfBot?start=282129429 |
| Created | Between 1 January 2016 and 30 April 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 September 2026 |
| Last confirmed live | 23 September 2026 |
| Measurements held | 13 |
| On Telegram | t.me/justice_law98 |
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 23 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 |
|---|---|---|
| 23 Sept 2026, 15:58 | 1,787 | no change |
| 15 Sept 2026, 23:19 | 1,787 | -4 |
| 12 Sept 2026, 12:59 | 1,791 | -6 |
| 8 Sept 2026, 13:37 | 1,797 | +1 |
| 31 Aug 2026, 08:45 | 1,796 | -2 |
| 28 Aug 2026, 09:35 | 1,798 | -4 |
| 25 Aug 2026, 01:35 | 1,802 | +1 |
| 21 Aug 2026, 22:15 | 1,801 | +2 |
| 18 Aug 2026, 12:04 | 1,799 | -4 |
| 12 Aug 2026, 16:14 | 1,803 | -2 |
| 9 Aug 2026, 15:14 | 1,805 | +1 |
| 6 Aug 2026, 12:11 | 1,804 | +1 |
| 5 Aug 2026, 21:29 | 1,803 | 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.
@jazaghafoori · 59,020
Telegram ranks this channel #14 of 77 here — alongside 76 others — read 23 August 2026
@LAWw_test · 23,829
Telegram ranks this channel #31 of 70 here — alongside 69 others — read 17 September 2026
@football_Dafnews · 21,381
Telegram ranks this channel #32 of 58 here — alongside 57 others — read 23 September 2026
@HOUSEBOOKLAW · 31,393
Telegram ranks this channel #43 of 69 here — alongside 68 others — read 6 September 2026
This channel appears in 4 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 23 September 2026 — this entry's latest reading, not the date you are reading this.
“🎓حقوقی های آزاد🎓” (@justice_law98), 1,787 subscribers as measured 23 September 2026. Telegram Register, tgregister.com/channel/justice_law98.
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.