Channel
@alhashediq
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
982subscribers
-3 since we began measuring on 16 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001683642229 |
|---|---|
| Type | Channel |
| Username | @alhashediq |
| 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 | 4 November 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/alhashediq |
Politics & activism — 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 3 October 2026 and assigned it the closest of 31 fixed categories, at 81% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 4 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @alhashediq/1898 · this entry11 Aug 2026, 10:22 UTC | @a4b44i/450611 Aug 2026, 13:31 UTC | 1.00 | 3.1 hours |
| @alhashediq/1907 · this entry12 Aug 2026, 11:16 UTC | @a4b44i/451512 Aug 2026, 12:43 UTC | 1.00 | 87 minutes |
| @alhashediq/1908 · this entry12 Aug 2026, 17:05 UTC | @a4b44i/451612 Aug 2026, 18:45 UTC | 1.00 | 1.7 hours |
| @alhashediq/1912 · this entry16 Aug 2026, 16:40 UTC | @a4b44i/452416 Aug 2026, 17:43 UTC | 1.00 | 63 minutes |
| @alhashediq/1916 · this entry23 Aug 2026, 15:06 UTC | @a4b44i/453823 Aug 2026, 16:13 UTC | 1.00 | 67 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @a4b44i | 5 (5/5 hand-verifiable sample passed) | 1.00 | 87 minutes | this entry (5–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 5 comparable posts for this entry, running 11 August 2026 to 23 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 4 channels, the one whose matching posts we hold earliest is @dfdfdf9. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 4 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 19:37 | 982 | -5 |
| 28 Oct 2026, 15:18 | 987 | +1 |
| 21 Oct 2026, 06:10 | 986 | -4 |
| 13 Oct 2026, 04:28 | 990 | +3 |
| 3 Oct 2026, 07:21 | 987 | +4 |
| 18 Sept 2026, 14:00 | 983 | -2 |
| 16 Sept 2026, 13:22 | 985 | no change |
| 16 Sept 2026, 12:47 | 985 | first reading |
5 posts held, back to 11 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 23 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
7 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 3 of the 5 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 11 August 2026 to 23 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
رئيس هيئة الحشد الشعبي وقياداته يستقبلون وفداً إيرانياً لتقديم الشكر للعراق على مشاركته في تشييع السيد الخامنئي استقبل رئيس هيئة الحشد الشعبي السيد فالح الفياض، بحضور عدد من قيادات الهيئة اليوم الأحد ، وفداً من الجمهورية الإسلامية الإيرانية، موفداً من قائد الثورة الإسلامية السيد مجتبى خامنئي، لتقديم الشكر والتقدير إلى العراق، حكومةً وشعباً، على مواقفه ومشاركته في مراسم تشييع وتوديع السيد علي الخامنئي. وأعرب الوفد ا…
❤4
برئاسة معاون رئيس الأركان يزور قيادة عمليات البصرة للجيش زار وفد من هيئة الحشد الشعبي، برئاسة السيد ياسر حسين العيساوي، معاون رئيس أركان الحشد الشعبي، وبرفقة قائد عمليات البصرة للحشد الشعبي مهدي عبد الواحد، قيادة عمليات البصرة للجيش، حيث كان في استقبال الوفد قائد عمليات البصرة للجيش اللواء الركن أثير حمزة جاسم، وذلك بمناسبة تسنّمه مهام عمله الجديد. وهنّأ الوفد اللواء الركن أثير حمزة جاسم بمناسبة تسلّمه مهامه، متمني…
❤1
زار معاون رئيس أركان هيئة الحشد الشعبي السيد ياسر حسين العيساوي المديرية العامة للتدريب في هيئة الحشد الشعبي، حيث التقى مديرها العام السيد عمار كريم السراي. وجرى خلال اللقاء بحث واقع العملية التدريبية والبرامج المعتمدة في المديرية، إلى جانب مناقشة سبل تطوير المناهج والارتقاء بمستوى التأهيل العسكري والمهني للمقاتلين، بما ينسجم مع متطلبات المرحلة وخصوصية المهام الموكلة إلى تشكيلات هيئة الحشد الشعبي. وأكد العيساوي أهمية…
معاون رئيس أركان الحشد الشعبي ياسر العيساوي يتفقد قاطع عمليات سامراء، للإطلاع على مستوى الجهوزية الأمنية والمهام الموكلة لتأمين الأضرحة المقدسة ومحيطها. #هيئة_الحشد_الشعبي #رئاسة_اركان_هيئة_الحشد_الشعبي #المكتب_الاعلامي
❤2
معاون رئيس أركان هيئة الحشد الشعبي يتفقد قاطع عمليات سامراء أجرى معاون رئيس أركان هيئة الحشد الشعبي، السيد ياسر حسين العيساوي، زيارة ميدانية إلى قاطع عمليات سامراء للحشد الشعبي، للاطلاع على سير العمل والمهام الأمنية التي تضطلع بها قوات الحشد الشعبي في حماية مدينة سامراء المقدسة وتأمين محيطها. وعقد العيساوي، خلال الزيارة، اجتماعًا موسعًا بحضور عدد من مسؤولي ومديري المديريات الساندة، جرى خلاله استعراض الوضع الأمني في …
Showing the 5 most recent of 5 posts we hold for @alhashediq. 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.
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.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“المكتب الإعلامي لرئاسة أركان هيئة الحشد الشعبي” (@alhashediq), 982 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/alhashediq.
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.