Channel
حقوق پلاس⚖️
@testtalifi
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,867subscribers
+56 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001831371995 |
|---|---|
| Type | Channel |
| Username | @testtalifi |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 September 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/testtalifi |
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 71% 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 |
|---|---|---|
| 9 Nov 2026, 00:51 | 1,867 | +6 |
| 5 Nov 2026, 09:06 | 1,861 | +1 |
| 2 Nov 2026, 05:48 | 1,860 | -2 |
| 30 Oct 2026, 07:28 | 1,862 | +5 |
| 26 Oct 2026, 21:19 | 1,857 | -1 |
| 24 Oct 2026, 01:11 | 1,858 | +6 |
| 21 Oct 2026, 11:05 | 1,852 | +1 |
| 18 Oct 2026, 11:16 | 1,851 | -1 |
| 15 Oct 2026, 11:59 | 1,852 | +1 |
| 12 Oct 2026, 07:56 | 1,851 | +9 |
| 5 Oct 2026, 13:56 | 1,842 | +9 |
| 27 Sept 2026, 23:17 | 1,833 | +5 |
| 23 Sept 2026, 01:31 | 1,828 | no change |
| 18 Sept 2026, 05:21 | 1,828 | +5 |
| 14 Sept 2026, 06:17 | 1,823 | +2 |
| 10 Sept 2026, 22:17 | 1,821 | +5 |
| 5 Sept 2026, 16:38 | 1,816 | +2 |
| 1 Sept 2026, 12:17 | 1,814 | -1 |
| 29 Aug 2026, 08:03 | 1,815 | +2 |
| 26 Aug 2026, 01:57 | 1,813 | 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.
@LAWw_test · 24,076
Telegram ranks this channel #19 of 70 here — alongside 69 others — read 17 September 2026
@lexcollege · 39,565
Telegram ranks this channel #35 of 86 here — alongside 85 others — read 1 September 2026
@Law_TesT2 · 63,253
Telegram ranks this channel #72 of 87 here — alongside 86 others — read 22 August 2026
@fasleeghtesad · 55,005
Telegram ranks this channel #80 of 86 here — alongside 85 others — read 23 August 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“حقوق پلاس⚖️” (@testtalifi), 1,867 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/testtalifi.
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.