Channel
Taqaror
@TaqarorAF
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,611subscribers
+85 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001694280480 |
|---|---|
| Type | Channel |
| Username | @TaqarorAF |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/TaqarorAF |
Topic
Job listings — 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 16 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 07:37 | 2,611 | +1 |
| 31 Oct 2026, 04:08 | 2,610 | -2 |
| 28 Oct 2026, 12:37 | 2,612 | +14 |
| 25 Oct 2026, 20:21 | 2,598 | -5 |
| 19 Oct 2026, 21:29 | 2,603 | -3 |
| 16 Oct 2026, 17:17 | 2,606 | +47 |
| 13 Oct 2026, 21:48 | 2,559 | +6 |
| 8 Oct 2026, 21:41 | 2,553 | +20 |
| 2 Oct 2026, 09:19 | 2,533 | +55 |
| 16 Sept 2026, 13:36 | 2,478 | -2 |
| 16 Sept 2026, 00:11 | 2,480 | no change |
| 12 Sept 2026, 16:21 | 2,480 | -6 |
| 8 Sept 2026, 10:20 | 2,486 | -4 |
| 2 Sept 2026, 18:34 | 2,490 | -3 |
| 30 Aug 2026, 06:25 | 2,493 | -3 |
| 27 Aug 2026, 07:42 | 2,496 | -7 |
| 23 Aug 2026, 22:23 | 2,503 | -13 |
| 20 Aug 2026, 10:52 | 2,516 | -6 |
| 17 Aug 2026, 09:24 | 2,522 | -4 |
| 13 Aug 2026, 14:36 | 2,526 | 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.
@unjobsofficial · 25,183
Telegram ranks this channel #8 of 69 here — alongside 68 others — read 13 September 2026
@wazifaha · 86,132
Telegram ranks this channel #10 of 78 here — alongside 77 others — read 21 August 2026
@acbarjob · 25,114
Telegram ranks this channel #18 of 74 here — alongside 73 others — read 14 September 2026
@dl_ketab · 60,528
Telegram ranks this channel #85 of 86 here — alongside 85 others — read 22 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“Taqaror” (@TaqarorAF), 2,611 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/TaqarorAF.
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.