4 measurements spanning 14 days, net +5. 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 7,656–7,667 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
28 Aug 2026, 11:55
7,666
+9
18 Aug 2026, 23:25
7,657
-2
16 Aug 2026, 02:13
7,659
-2
14 Aug 2026, 13:16
7,661
first reading
Engagement
44 posts held, back to 18 June 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 7 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
26.8%
avg views ÷ 7,666 subscribers
Avg views / post
2,050
28 posts measured
Reaction rate
0.594%
reactions ÷ views · ER floor
Posts in window
28
of 44 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 28 August 2026
Posts held
44 (18 June 2026 – 28 August 2026)
Views total
57,440
Reactions total
341
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
28 Aug 2026, 21:08 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
Photos
≈622
Videos
≈144
Links
≈1,720
Lifetime counters from Telegram’s own channel header, read 28 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
3m 59s
Average length
1m 20s
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
863 reactions across 42 posts, in 9 distinct kinds. The most used accounts for 46.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
399
46.2%
👍
334
38.7%
🥰
54
6.26%
😁
30
3.48%
👏
20
2.32%
🔥
12
1.39%
💊
6
0.695%
👌
5
0.579%
👎
3
0.348%
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 42 of the 44 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 863reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 44 most recent posts we hold, published 18 June 2026 to 28 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.
🇮🇶 العامري لشيوخ عموم عشائر العراق:
- سنشرع قانون الحشد الشعبي، وقد تحدثنا مع رئيس الوزراء، وهو يؤيد ذلك.
- فصـ..ـائل المقـ..ـاومة أناس عقلاء، دافعوا عن العراق وسيادته، وقاتلوا الاحتلال ود11عش.
قانون الحشد الشعبي استحقاق وإنصاف لرجال قدموا التضحيات دفاعاً عن العراق.
#قانون_الحشد_الشعبي
#حقوق_الحشد
#الحشد_الشعبي
https://t.me/yahco
تحالف الاقوياء لإقرار قانون الحشد نجح في بناء تفاهمات واسعة مع مختلف الكتل والقوى السياسية، وحشد الدعم النيابي اللازم للمضي بتشريع القانون وإقراره
https://t.me/yahco
تحالف الاقوياء لإقرار قانون الحشد :
السيد رئيس مجلس الوزراء وقّع على قانونَي الخدمة والتقاعد والهيكلية، ومن المقرر أن يصلا إلى مجلس النواب الاسبوع القادم للمضي بإقرارهما .
https://t.me/yahco
النائب الأول لرئيس البرلمان عدنان فيحان: الحشد الشعبي تأسس في ظرف استثنائي بطابع عقائدي واجتماعي وقانوني.. ضرورة أن يشرع قانون ينظم هيكلة الحشد الشعبي
https://t.me/yahco
هيئة الحشد الشعبي:
الفياض: رئيس الوزراء سيقدم قانون الحشد الشعبي إلى البرلمان قريبا بعد إجراء بعض التعديلات.
الفياض: فك الارتباط عن الحشد الشعبي يجب أن يجري وفق خطط مدروسة وانتقال آمن.
الفياض: يجب مراعاة التاريخ الجهادي والوطني للفصائل والتعامل مع الملف بحكمة.
الفياض: الفصائل ليسوا أعداء للعراق، وسوف ينسجمون مع المتغيرات القادمة بعد الانسحاب الأمريكي.
الفياض: أي فرد من الحشد الشعبي عليه أمر قضائي، نحن من سيعتقله …
هيئة الحشد الشعبي:
الفياض: نحن من نواجه الخطر، ونعمل كل ما يلزم شرعا وقانونا للدفاع عن كل فرد في الحشد الشعبي.
الفياض: الهجمات الإعلامية التي تستهدفني تحاول الإساءة لي رسميا وشعبيا وإقليميا.
الفياض: نحن من يدرك ويعلم الخطر الذي يتعرض له الحشد الشعبي، وليس بعض النواب أو الجهات الإعلامية.
الفياض: اسمي يتكرر استهدافه في كل المواسم، ودائما يتزامن مع عرض قانون الحشد الشعبي في البرلمان.
الفياض: لا يمكن إخلاء جميع مقرات…
الزيدي: الحكومة ستمضي بتقديم قانون هيئة الحشد لإقراره بوصفها جزءاً من تشكيلات القوات المسلحة
https://t.me/yahco
👍8❤2
Showing the 12 most recent of 44 posts we hold for @yahco. 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.
Posts edited after publishing
@yahco edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
18 August 2026
Most recent edit
18 August 2026
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.
قناة رواتب الحشد والمعلومات الادارية والمالية والعسكريه @A_7110 · 50,658 Telegram ranks this channel #11 of 88 here — alongside 87 others — read 25 August 2026
مدير الدائرة الادارية والمالية العامة @husseinismal · 77,191 Telegram ranks this channel #18 of 85 here — alongside 84 others — read 19 August 2026
محمد صادق @M0hammedsadiq · 43,055 Telegram ranks this channel #46 of 70 here — alongside 69 others — read 28 August 2026
أمة الحشد | crowd nation @crowdnation · 113,482 Telegram ranks this channel #59 of 93 here — alongside 92 others — read 14 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 28 August 2026 — this
entry's latest reading, not the date you are reading this.
“ابناء الحشد” (@yahco), 7,666 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/yahco.
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.