أسعد الله أيّامكم بذكرى ولادة الرسول الأعظم🌿 «أبلغي سلامي لرسولنا العظيم، وأبلغيهِ أنّني سأدافع عن إسلامهِ ما دمتُ حيّا. وإنّي لأرجو نصرتهُ وشفاعته». من رسالة الحاج قاسم سليماني لِابنة أحد الشهداء عندَ عزمها علی زيارة مدینة الرسول الأعظم 🌿.

Channel
مكتب الحاج قاسم سليماني / عربي
@hqs_ar
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
13,358subscribers
-99 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001574290706 |
|---|---|
| Type | Channel |
| Username | @hqs_ar |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/hqs_ar |
Topic
Religion — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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, 17:16 | 13,358 | -5 |
| 17 Sept 2026, 04:59 | 13,363 | +3 |
| 15 Sept 2026, 02:56 | 13,360 | -3 |
| 13 Sept 2026, 09:58 | 13,363 | -7 |
| 11 Sept 2026, 16:39 | 13,370 | -4 |
| 9 Sept 2026, 04:56 | 13,374 | -5 |
| 5 Sept 2026, 18:56 | 13,379 | -1 |
| 3 Sept 2026, 18:20 | 13,380 | +7 |
| 2 Sept 2026, 14:07 | 13,373 | -3 |
| 1 Sept 2026, 16:08 | 13,376 | -2 |
| 31 Aug 2026, 16:42 | 13,378 | +1 |
| 30 Aug 2026, 18:04 | 13,377 | -6 |
| 29 Aug 2026, 16:34 | 13,383 | -8 |
| 28 Aug 2026, 15:52 | 13,391 | +1 |
| 27 Aug 2026, 18:16 | 13,390 | -2 |
| 26 Aug 2026, 17:02 | 13,392 | -3 |
| 25 Aug 2026, 14:55 | 13,395 | -9 |
| 24 Aug 2026, 16:15 | 13,404 | -1 |
| 23 Aug 2026, 00:52 | 13,405 | +3 |
| 21 Aug 2026, 13:35 | 13,402 | first reading |
Engagement
4 posts held, back to 3 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 50 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 8.53%
- avg views ÷ 13,358 subscribers
- Avg views / post
- 1,140
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 4 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 4 (3 August 2026 – 29 August 2026) |
| Views total | 1,140 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 20:15 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Video runtime
- 16s
- Average length
- 16s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
جانب من الفعاليّات المصاحبة لـ«موكب الحاج قاسم سليماني» في الأربعين الحسينيّ، عمود 533
مِن المسيرة العزائية المتوجّهة نحو مقرّ «موكب الحاج قاسم سليماني» عمود 533 تحت عنوان: يالثارات الوليّ
راية الثأر الخفّاقة طوال أيّام مسير الأربعين الحسيني بعنوان: «يالثارات الوليّ» والتي يتناوب الزوّار على حملها، من الفعاليات المصاحبة لنشاط موكب مكتب الحاج قاسم سليماني، عمود 533
Showing the 4 most recent of 4 posts we hold for @hqs_ar. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.
@Abumahdi_com · 63,119
Telegram ranks this channel #4 of 89 here — alongside 88 others — read 23 August 2026
@Khamenei_arabi · 79,269
Telegram ranks this channel #5 of 87 here — alongside 86 others — read 18 August 2026
@soleimany_ir · 38,107
Telegram ranks this channel #15 of 93 here — alongside 92 others — read 31 August 2026
@Al7hashd · 25,438
Telegram ranks this channel #18 of 82 here — alongside 81 others — read 14 September 2026
@ya3abbas · 25,257
Telegram ranks this channel #26 of 84 here — alongside 83 others — read 14 September 2026
@almaareflb · 25,713
Telegram ranks this channel #50 of 92 here — alongside 91 others — read 13 September 2026
@pubic_Finance · 24,324
Telegram ranks this channel #56 of 89 here — alongside 88 others — read 16 September 2026
@StateMediaTeamForums · 25,001
Telegram ranks this channel #59 of 87 here — alongside 86 others — read 15 September 2026
@QafArt · 22,205
Telegram ranks this channel #70 of 90 here — alongside 89 others — read 21 September 2026
@alhashed_alshaebe · 39,356
Telegram ranks this channel #79 of 87 here — alongside 86 others — read 31 August 2026
@typokar · 25,833
Telegram ranks this channel #92 of 92 here — alongside 91 others — read 13 September 2026
This channel appears in 11 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.
“مكتب الحاج قاسم سليماني / عربي” (@hqs_ar), 13,358 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/hqs_ar.
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.