3 measurements spanning 11 days, net -2. 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 203–205 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
18 Sept 2026, 20:41
203
-2
8 Sept 2026, 20:22
205
no change
8 Sept 2026, 05:17
205
first reading
Engagement
20 posts held, back to 23 August 2025 — 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.
ERR · 30 days
10.3%
avg views ÷ 203 subscribers
Avg views / post
21.0
1 post measured
Reaction rate
14.3%
reactions ÷ views · ER floor
Posts in window
1
of 20 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 5 September 2026
Posts held
20 (23 August 2025 – 5 September 2026)
Views total
21
Reactions total
3
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Sept 2026, 20:22 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.
Reaction mix
48 reactions across 15 posts, in 2 distinct kinds. The most used accounts for 62.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
30
62.5%
👍
18
37.5%
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 15 of the 20 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 48 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 23 August 2025 to 5 September 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.
۱۴۰۵٫۰۶٫۱۴ | ۲۰۲۶٫۰۹٫۰۵
#صحبت_خودمونی
اینو حتما و حتما گوش کنید
گوش کردین، یه ریکشن بده، بدونم هستی
🚨 چند تا توصیه در مورد ویروس جدید
چنل لایوترید و سیگنال از این هفته
چنل در تلگرامه، نوتیفیکشن روشن باشه
کپی همه تریدها به صورت خودکار و آنی
عضویت یک هفته بصورت کاملا رایگان
چیکار کنم؟ توضیح دادم تو ویس ...
✅ برای عضویت پیام بدین
اعضای قبلی چنل سیگنال، حتما پیام بدن
👇👇
🆔 @MHBForex
1404.06.16 / 2025.09.07
#BTCUSDT #Daily
بیتکوین در تایم روزانه بین نواحی عرضه و تقاضا در حال نوسان و افت قیمت هستش، سناریو محتمل اینه که تا دیمند افت کنه ❤️
یه پوزیشن شورت تو ذهنم هست که این مدل پرریسکشه، کم ریسکش اینه که اون پینبار نزولی قبلش رو به عنوان استاپ در نظر بگیرم💐
#بیتکوین #تحلیل_بیتکوین #تحلیل_بیت_کوین #بیت_کوین
@MHTahlil
1404.06.16 / 2025.09.07
#XAUUSD #Daily
این بزرگوار رو بهتون گفتم این سری دیگه میخواد رد شه و اونس بالاخره از این ناحیه عرضه عبور کرد، تو هفته آینده احتمالش هست که یه افتی اتفاق بیفته و یه پولبک به ناحیه عرضه بزنه، اگه بخواد به ناحیه دیمند برسه عملا یه فیک برک اوت ثبت میکنه که داستان میشه ❤️
بعید میدونم فیک برکاوت داشته باشیم
#اونس #اونس_طلا #تحلیل_اونس
@MHTahlil
1404.06.16 / 2025.09.07
#EURUSD #Weekly
یورو در تایم هفتگی همچنان پشت ناحیه عرضه منتظره و هنوز افت نکرده، فکر کنم منتظر پاول هستند که نرخ بهره رو کاهش بدن و از این ناحیه عبور کنه، کاهش نرخ بهره منجر به عبور قیمت از این مقاومت خواهد شد ❤️
گزارش مشاغل اومد و نرخ افتضاح ۲۲ هزار تا رو داشت، احتمال کاهش نرخ بهره خیلی زیاده، حتی ممکنه ۰.۵ واحد کاهش داشته باشیم و اینا دلار رو تضعیف خواهند کرد.
این هفته تا چهارشنبه تکنیکا…
۱۴۰۴.۰۶.۱۰
#صحبت_خودمونی #مشاوره
در مورد دلار، طلا و مکانیزم ماشه
✅ دلار و طلا بخریم یا بفروشیم؟
✅ حتما باید دلار یا طلا بخـریم؟
✅ آیا میتونم به فروش فکر کنم؟
و چند توصیه برادرانه به شما عزیزانم
سوالی داشتین بپرسین:
@MHBForex
1404.06.08 / 2025.08.30
#XAUUSD #4H
یه نمای کلی از تایم ۴ ساعته براتون فرستادم، دیمند ۴ ساعته دقیقا تو دل دیمند روزانه است که رسم نکردم. آخر هفتهای نقدینگی تمام سقفهای اخیر رو زد. حالا ۲ تا سناریو داریم
حدست کدوم یکیه؟
سناریو ۱: افت کنه و بیاد به دیمند روزانه برسه 👍
سناریو ۲:بالای سقفها تثبیت بشه و بره برای ۳۵۰۰ دلار ❤️
ریکشنش رو بزن
#اونس #اونس_طلا #تحلیل_اونس
@MHTahlil
1404.06.08 / 2025.08.30
#XAUUSD #Daily
این لگ اخیر اونس تمیزه و احساس میکنم این سری میخواد بره بالای سقف قبلی رو جمع کنه و در ادامه بره واسه ۴۰۰۰ دلار ❤️
برای خرید طلا تو بازار داخلی ازم پرسیدین، بخرین، پله پله بخرین، درسته که مهلت یه ماهه برای اکتیو شدن مکانیزم ماشه دادند، اما اینا بعید میدونم بتونند تو این یه ماه حرکتی بزنند
#اونس #اونس_طلا #تحلیل_اونس
@MHTahlil
1404.06.05 / 2025.08.27
#XAUUSD #4H
اینم از چارت اونس، یه پوزیشن فروش داریم که براتون رسم کردم و تازه از ضرر اومده بیرون و چندرغازی تو سوده، برای این چارت میتونیم دو تا سناریو در نظر بگیریم ...
سناریو اول: پوزیشن اخیر حداقل ریوارد ۱ رو بده و افت کنه
سناریو دوم: این پوزیشن استاپ بخوره و آخرین سقف رو سوئیپ کنه
نظرتون؟
سناریو اول: 👍🏻
سناریو دوم: ❤️
#اونس #اونس_طلا #تحلیل_اونس
@MHTahlil
1404.06.05 / 2025.08.27
#EURUSD #4H
وضعیت یورو در تایم چهارساعته رو میبینین، یه سوئیپ نقدینگی سقفهای اخیر انجام داد و افت کرد، حالا رسیده به بیس اون حرکت شارپی جمعه هفته گذشته ...
دو تا تصمیم میتونه بگیره
سناریو اول: از همین ناحیه مجددا به سمت بالا حرکت کنه و سناریو دوم: یا اینکه بیاد و پایین این حرکت شارپی رو ببینه و تمام پوزیشنهای خرید رو استاپ بزنه
نظرتون؟
سناریو اول: 👍🏻
سناریو دوم: ❤️
#یورو #یورودلار #ت…
Showing the 12 most recent of 20 posts we hold for @MHTahlil. 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.
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.
Ensiven Yoga @Ensivenyoga · 29,640 Telegram ranks this channel #27 of 70 here — alongside 69 others — read 8 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 18 September 2026 — this
entry's latest reading, not the date you are reading this.
“MHTahlil | اماچ تحلیل” (@MHTahlil), 203 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/MHTahlil.
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.