Telegram RegisterThe public register of Telegram
Telegram profile photo for محبين الحاج ياسر حسين العيساوي/Yasser Hussain alaisawi

Channel

محبين الحاج ياسر حسين العيساوي/Yasser Hussain alaisawi

@alhashd_alshaebiu_1

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

226subscribers

-12 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001712531197
TypeChannel
Username@alhashd_alshaebiu_1
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 November 2026
Measurements held10
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/alhashd_alshaebiu_1

Topic

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 23 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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.

Observations

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.

Content that also appears on other registered channels

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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@dfdfdf9/13002 Aug 2026, 22:29 UTC@alhashd_alshaebiu_1/1447 · this entry2 Aug 2026, 22:47 UTC1.0018 minutes
@dfdfdf9/13073 Aug 2026, 16:47 UTC@alhashd_alshaebiu_1/1454 · this entry3 Aug 2026, 16:53 UTC1.007 minutes
@dfdfdf9/13104 Aug 2026, 08:06 UTC@alhashd_alshaebiu_1/1456 · this entry4 Aug 2026, 09:01 UTC1.0055 minutes
@dfdfdf9/13144 Aug 2026, 10:16 UTC@alhashd_alshaebiu_1/1460 · this entry4 Aug 2026, 10:22 UTC1.006 minutes
@dfdfdf9/13174 Aug 2026, 10:21 UTC@alhashd_alshaebiu_1/1461 · this entry4 Aug 2026, 10:22 UTC1.0072 seconds
@dfdfdf9/13184 Aug 2026, 10:21 UTC@alhashd_alshaebiu_1/1462 · this entry4 Aug 2026, 10:22 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@dfdfdf97 (7/7 hand-verifiable sample passed)1.007 minutes@dfdfdf9 (7–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 9 comparable posts for this entry, running 2 August 2026 to 6 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 4 channels, the one whose matching posts we hold earliest is @dfdfdf9. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, 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.

Channels linked by matching posts

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.

Growth

2262382327 August 2026 — 238 subscribers8 August 2026 — 238 subscribers7 September 2026 — 236 subscribers15 September 2026 — 233 subscribers29 September 2026 — 232 subscribers10 October 2026 — 231 subscribers16 October 2026 — 230 subscribers23 October 2026 — 229 subscribers6 November 2026 — 227 subscribers15 November 2026 — 226 subscribers7 August 202615 November 2026
10 measurements spanning 100 days, net -12. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 224–240 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Nov 2026, 12:01226-1
6 Nov 2026, 13:51227-2
23 Oct 2026, 15:09229-1
16 Oct 2026, 19:29230-1
10 Oct 2026, 11:21231-1
29 Sept 2026, 18:16232-1
15 Sept 2026, 16:21233-3
7 Sept 2026, 20:00236-2
8 Aug 2026, 09:50238no change
7 Aug 2026, 15:52238first reading

Engagement

10 posts held, back to 2 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 10 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3m 14s
Average length
1m 05s

Measured directly from 3 videos 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.

Reaction mix

22 reactions across 10 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤22100.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 10 of the 10 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 22 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 2 August 2026 to 6 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.

Recent posts

6 Aug 2026, 22:31 UTC14 views3 reactionsread 8 August 2026
Forwarded from @a4b44iVideo

قوة الشهيد ذو الفقار المكصوصي معاونية رئاسة الأركان لشؤون العمليات #هيئة_الحشد_الشعبي #طريق_نجف_كربلاء #رئاسة_اركان_هيئة_الحشد_الشعبي #فوج_الشهيد_ذوالفقار

❤3

5 Aug 2026, 20:21 UTC17 views3 reactionsread 8 August 2026
Forwarded from @a4b44iVideo

قوة الشهيد ذو الفقار المكصوصي التابعة لمعاونية رئاسة الأركان لشؤون العمليات #طريق_نجف_كربلاء #هيئة_الحشد_الشعبي #رئاسة_اركان_هيئة_الحشد_الشعبي #فوج_الشهيد_ذوالفقار

❤3

4 Aug 2026, 15:24 UTC16 views2 reactionsread 8 August 2026
Forwarded from @a4b44iVideo

معاون رئيس أركان هيئة الحشد الشعبي، ياسر العيساوي، يوجّه رسالة شكر وتقدير إلى مسؤولي هيئة الحشد الشعبي ومنتسبيها، تثمينًا لجهودهم الاستثنائية في إنجاح خطة تأمين الزيارة الأربعينية. #مثلي_لايبايع_مثله #هيئة_الحشد_الشعبي #رئاسة_اركان_هيئة_الحشد_الشعبي #المكتب_الاعلامي

❤2

4 Aug 2026, 10:22 UTC17 views1 reactionsread 8 August 2026
Forwarded from @a4b44i

العيساوي: اتصالات الحشد الشعبي وفّرت ملايين المكالمات المجانية وخدمات الإنترنت والطوارئ عبر الرقم 128 لخدمة زائري الأربعين . العيساوي: أكثر من 1000 آلية عملت على تزويد المواكب الحسينية بالثلج والمياه على امتداد محاور الزيارة الأربعينية. العيساوي: طبابة الحشد سخّرت مئات عجلات الإسعاف وإمكاناتها الطبية لتقديم خدمات صحية متواصلة لزائري الأربعين طوال فترة الزيارة.

❤1

4 Aug 2026, 10:22 UTC13 views1 reactionsread 8 August 2026
Forwarded from @a4b44i

العيساوي: انتهت مراسم الزيارة في جميع المحافظات، باستثناء محافظة كربلاء المقدسة. العيساوي: انتشرت قواتنا على جميع الطرق والمحاور المؤدية إلى كربلاء المقدسة. العيساوي: شاركت جميع المعاونيات والمديريات في تقديم خدمات استثنائية لزائري أربعينية الإمام الحسين (عليه السلام). العيساوي: هناك تنسيق عالٍ بين الحشد الشعبي والقوات الأمنية ولجنة الزيارات المليونية لضمان نجاح الخطة الأمنية والخدمية.

❤1

4 Aug 2026, 10:22 UTC13 views2 reactionsread 8 August 2026
Forwarded from @a4b44iPhoto

معاون رئيس أركان هيئة الحشد الشعبي لشؤون العمليات، ياسر حسين العيساوي: شاركت هيئة الحشد الشعبي بأكثر من 70 فوجًا في تأمين الحدود.

❤2

4 Aug 2026, 09:01 UTC11 views2 reactionsread 8 August 2026
Forwarded from @a4b44iPhoto

معاون رئيس أركان الحشد لشؤون العمليات يتفقد اللواء 72 ويطلع على تنفيذ خطة الأربعين أجرى معاون رئيس أركان هيئة الحشد الشعبي لشؤون العمليات، ياسر حسين العيساوي، زيارة إلى مقر اللواء (72)، للاطلاع على سير تنفيذ الخطة الأمنية والخدمية الخاصة بزيارة أربعينية الإمام الحسين (عليه السلام). واطلع العيساوي خلال الزيارة على انتشار القطعات وآلية تنفيذ الواجبات الميدانية، واستمع إلى إيجاز عن مجمل الإجراءات المتخذة لتأمين الزائر…

❤2

3 Aug 2026, 16:53 UTC12 views3 reactionsread 8 August 2026
Forwarded from @a4b44iPhoto

معاون رئيس أركان الحشد يزور قيادة قاطع الأنبار ويطلع على جاهزيتها وانتشارها خلال زيارة الأربعين زار معاون رئيس أركان هيئة الحشد الشعبي لشؤون العمليات، ياسر العيساوي، مقر قيادة عمليات قاطع الأنبار في كربلاء المقدسة حيث كان في استقباله قائد عمليات قاطع الأنبار للحشد الشعبي قاسم مصلح. واطلع العيساوي، برفقة مصلح، على سير عمل ألوية القاطع وانتشارها الميداني في المحور الجنوبي لمدينة كربلاء المقدسة، مستمعا إلى إيجاز عن ال…

❤3

2 Aug 2026, 22:47 UTC17 views3 reactionsread 8 August 2026
Forwarded from @a4b44iPhoto

العيساوي يزور مقر مديرية الجهد الخدمي في كربلاء المقدسة وزيارة أخرى لقاطع مسؤولية قوة الشهيد ذوالفقار على طريق نجف كربلاء #مثلي_لايبايع_مثله #هيئة_الحشد_الشعبي #رئاسة_اركان_هيئة_الحشد_الشعبي #المكتب_الاعلامي

❤3

Showing the 10 most recent of 10 posts we hold for @alhashd_alshaebiu_1. 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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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 15 November 2026 — this entry's latest reading, not the date you are reading this.

“محبين الحاج ياسر حسين العيساوي/Yasser Hussain alaisawi” (@alhashd_alshaebiu_1), 226 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/alhashd_alshaebiu_1.

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.