Telegram RegisterThe public register of Telegram

Channel

𝐌𝐇𝐌.𝐂𝐇𝐀𝐍𝐍𝐄𝐋

@MHM_BOT_Channel

On this record: Growth · Engagement · Posts · Citations · Cite this entry

4,080subscribers

-47 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003774049870
TypeChannel
Username@MHM_BOT_Channel
CreatedBetween 1 February 2026 and 23 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/MHM_BOT_Channel

Growth

4,0804,1274,103.58 August 2026 — 4,127 subscribers8 August 2026 — 4,127 subscribers8 August 2026 — 4,115 subscribers11 August 2026 — 4,080 subscribers8 August 202611 August 2026
4 measurements spanning 3 days, net -47. 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 4,073–4,134 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 15:064,080-35
8 Aug 2026, 22:244,115-12
8 Aug 2026, 19:004,127no change
8 Aug 2026, 18:494,127first reading

Engagement

17 posts held, back to 23 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.62%
avg views ÷ 4,080 subscribers
Avg views / post
270
6 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
6
of 17 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
WindowRolling 30 days · latest post in window 25 July 2026
Posts held17 (23 June 202625 July 2026)
Views total1,621
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 19:00 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.

Recent posts

25 Jul 2026, 15:51 UTC54 viewsread 8 August 2026
Forwarded from @MHM_GiftPhoto

PvP راند 1866 هست راند 2000 غیر از کل کوین ها برنده t.me/nft/ChillFlame-285442 این nft هم میبره 🏋️‍♂️

25 Jul 2026, 13:14 UTC67 viewsread 8 August 2026

@MHM_ads_bot بات تبلیغات ران شد ‼️ حالا این بات چیکار میکنه ؟ چنل دار ها ➕ شما اگه چنل دارید میتونید این باتو توی چنلتون ادمین کنید و یه قیمت واسه هر پست تبلیغات تعیین کنید و بیان تبلیغات بدن بعدش میتونید موجودیتونو برداشت کنید ➕ گپ دار ها 👥 شما میتونید گپتونو توی بات ثبت کنید و اگه کسای ثبت سفارش ممبر کرده باشهعضوین اجباری بات فعال میشه و تا عضو چنل تبلیغاتی نشن نمیتونن پیام بدن قیمت ممبر و ما تعیین میکنیم که فعلا

22 Jul 2026, 21:37 UTC63 viewsread 8 August 2026
Forwarded from @MHMHOKMPhoto

New update 🤜 Now we have a team pvp bot. You can be in a team with your friends and pvp with the others. 🤝🤜 @MHMHOKM_BOT اپدیت جدید 🤜 حالا توی بات pvp تیمی داریم شما میتونید با دوستاتون توی ۱ تیم باشید و با بقیه pvp کنید. 🤝🤜

20 Jul 2026, 19:08 UTC90 viewsread 8 August 2026
Forwarded from @Hapooy_Channel

اپدیت جدید بات هاپویی ‼️ قابلیت خرید سگ های جدید.🐶 8 سگ اضافه شده به بات که شما از توی قسمت شاپ وقتی بنویسید هاپو میتونید اونارو بخرید🐕 با خرید اونا سرعت کارخونه هاتون و جنع آوری هاپو کوین هاتون بیشتر میشه. همین الان هاپو های جدیدو بخرید 🐩 @Hapooy_bot

13 Jul 2026, 14:28 UTC≈1,040 viewsread 8 August 2026

از این به بعد اخبار آپدیت های جدید بات هیدن چت @MHM_HidenChat_bot توی این جنل میزاریم : @MHM_HidenChat_Channel

12 Jul 2026, 11:10 UTC905 viewsread 8 August 2026

یه بات داریم میزنیم برای اینکه چنل ها و گپ های کوچک هم بتونن تبلیغات بگیرن و درآمد داشته باشن 😌

10 Jul 2026, 19:32 UTC320 viewsread 8 August 2026
Forwarded from @MHM_SHOP

@MHMShop_bot خرید استارز ⭐ خرید پریموم تلگرام ⭐️ خرید تون 💎 خرید گیفت 🧸

9 Jul 2026, 18:15 UTC897 viewsread 8 August 2026

@MHM_CHALLENGE_BOT ربات برای کمک در چالش گذاشتن در چنل مثل شمردن ست های کازینو و چالش کامنتی گذاشتن 😴

9 Jul 2026, 17:29 UTCviews —

𝐌𝐇𝐌.𝐂𝐇𝐀𝐍𝐍𝐄𝐋 pinned «MHM BOTS ⚫️ @MHM_HidenChat_bot 🖤 @MHMHOKM_BOT 🔥 @MHM_price_bot 🕯 @MHMShop_bot ⭐️ @MHM_CHALLENGE_BOT 🎮 @Hapooy_bot 🙂»

Showing the 12 most recent of 17 posts we hold for @MHM_BOT_Channel. 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

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

Names

Channels on the register whose handles appear in this channel's posts.

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.

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

“𝐌𝐇𝐌.𝐂𝐇𝐀𝐍𝐍𝐄𝐋” (@MHM_BOT_Channel), 4,080 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/MHM_BOT_Channel.

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.