Channel
@MHDBw
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
25subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002028939072 |
|---|---|
| Type | Channel |
| Username | @MHDBw |
| Created | 23 October 2023 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/MHDBw |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 09:36 | 25 | +1 |
| 11 Aug 2026, 11:16 | 24 | no change |
| 7 Aug 2026, 16:12 | 24 | first reading |
7 posts held, back to 23 October 2023 — 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 7 posts for this entry, the most recent from 24 October 2023. An engagement rate over an empty window would be a number about nothing.
6 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 33.3% | |
| 🤯 | 2 | 33.3% | |
| 👎 | 1 | 16.7% | |
| 🔥 | 1 | 16.7% |
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 7 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 23 October 2023 to 24 October 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
末吭担保 pinned «末吭致力于打造tg第一大团队，做出特色，回到tg刚开始的样子！ 末吭担保最低担保金额100u，交易时不可超担保额交易，超出部分不退还，请消费者注意⚠️ 末吭担保全体工作人员不会主动私信你，也不可能在你出现纠纷的时候对你进行索要金钱，如有工作人员出现此状况，请举报！⚠️ 末吭担保目前工作成员名单： 末吭 @MoHangCN 纠纷处理Mal @MaI_V4Bot 纠纷处理小唐 @MHDBXT_Bot 官方记账 @MoHangJZBOT 验群机器人 @MoHangConfirm_BOT 末吭团队目前项目频道：…»
末吭致力于打造tg第一大团队，做出特色，回到tg刚开始的样子！ 末吭担保最低担保金额100u，交易时不可超担保额交易，超出部分不退还，请消费者注意⚠️ 末吭担保全体工作人员不会主动私信你，也不可能在你出现纠纷的时候对你进行索要金钱，如有工作人员出现此状况，请举报！⚠️ 末吭担保目前工作成员名单： 末吭 @MoHangCN 纠纷处理Mal @MaI_V4Bot 纠纷处理小唐 @MHDBXT_Bot 官方记账 @MoHangJZBOT 验群机器人 @MoHangConfirm_BOT 末吭团队目前项目频道： 通知频道 t.me/MoHangNoti 讨论群组 t.me/MoHangTalk 担保频道 t.me/MHDBw (末吭担保网首字母) 供需频道 t.me/MHGXp (末吭供需频首字母) 假证频道 t.me/MoHangCard 在我方公群被骗，被杀鱼，我方必然追究到底，无论如何，我们会在我们所能范围内帮助您！ 感…
上押500u✅ 上押人： t.me/KKLX14 公群： （隐藏） 编号： #2 已在末吭担保退押 已在末吭担保退押 已在末吭担保退押
🤯2
末吭担保 pinned «这里是末吭担保！担保找 @MoHangCN ！ 100u起！信誉担保！！！ 其他业务见群简介！»
上押100u✅ 上押人： t.me/Eshenchadang 公频： t.me/hujipindaoCD 编号： #1 已在末吭担保退押 已在末吭担保退押 已在末吭担保退押
🔥1
这里是末吭担保！担保找 @MoHangCN ！ 100u起！信誉担保！！！ 其他业务见群简介！
👍2👎1
Channel created
Showing the 7 most recent of 7 posts we hold for @MHDBw. 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.
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.
@MHDBw named 5 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“末吭担保” (@MHDBw), 25 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/MHDBw.
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.