Channel
@mangguohash
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
54,132subscribers
-13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001788271269 |
|---|---|
| Type | Channel |
| Username | @mangguohash |
| Description | 官方网址： http://www.mghx77.com 播报游戏：https://t.me/MGhash0000 芒果综合频道：https://t.me/mgjt1 💁♂️客服： @mghx77 💁招商： @qitongwei11（拿盘联系） 💁芒果影院： @mango887_bot |
| Created | Between 1 December 2021 and 8 August 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/mangguohash |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.
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.
Posts published here appear word for word on 1 other registered channel. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @mangguohash/142 · this entry22 Aug 2022, 18:20 UTC | @mangguojingcai/75622 Aug 2022, 18:21 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @mangguojingcai | 8 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (7–1) |
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 19 comparable posts for this entry, running 8 August 2022 to 10 March 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.
Across the whole group of 2, the earliest publisher we hold is @mangguohash — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 20:15 | 54,132 | -2 |
| 14 Aug 2026, 07:16 | 54,134 | -1 |
| 12 Aug 2026, 21:07 | 54,135 | -3 |
| 11 Aug 2026, 22:23 | 54,138 | -2 |
| 10 Aug 2026, 22:17 | 54,140 | -1 |
| 9 Aug 2026, 18:42 | 54,141 | -4 |
| 7 Aug 2026, 06:00 | 54,145 | no change |
| 7 Aug 2026, 05:49 | 54,145 | first reading |
20 posts held, back to 8 August 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 23 pagesof 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 20 posts for this entry, the most recent from 10 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 16 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
6,799 reactions across 8 posts, in 12 distinct kinds. The most used accounts for 67.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💩 | 4,570 | 67.2% | |
| 🤯 | 309 | 4.54% | |
| 🤔 | 306 | 4.50% | |
| 👎 | 282 | 4.15% | |
| 🤬 | 275 | 4.04% | |
| 🤮 | 272 | 4.00% | |
| 😢 | 267 | 3.93% | |
| 😁 | 256 | 3.77% | |
| 😱 | 250 | 3.68% | |
| 👍 | 8 | 0.118% | |
| ❤ | 3 | 0.044% | |
| 🥰 | 1 | 0.015% |
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 9 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 6,799reactions 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 8 August 2022 to 10 March 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.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
尊敬的芒果哈希俱乐部成员们，由于平台系统故障尚在维护升级，期间给各位带来不便，芒果全体员工在此给给位说声抱歉！ 经集团商量决定，截止今日为止，期间下注未赔付的订单，平台已经在统计核实，也会尽快给予赔付。郑重声明，9月28日零点以后直至正常开机运营期间若还有下注未赔付的，平台将不再处理，请各位相互转告。也希望各位随时关注平台的官方频道最新动态！ 官方频道：https://t.me/mangguohash 官方网站：http://www.mghx77.com
💩1,450🤔92🤬87🤯86😢85🤮78👎76😁63
尊敬的各位俱乐部爱好者们，，随着【芒果哈希竞彩俱乐部】的会员玩家人数日益增加，为满足广大哈希爱好者们的需求，平台决定将于2022年9月20号（今天）北京时间 10：30进行维护升级，请大家在维护期间暂停投注，感谢大家的理解与配合。 官方频道：https://t.me/mangguohash 官方网站：http://www.mghx77.com 播报游戏：https://t.me/MGhash0000
💩1,630🤯114👎91🤔91😁90🤮88😢84🤬81
🏅🏅芒果哈希俱乐部喜迎金秋，活动已经圆满结束。 为了满足广大玩家朋友的需求，现推出以上福利活动奖励！！福利多多奖励多多，欢迎各位前来领取，平台备足500W美金欢迎亲们前来爆庄！！！！🏆🏆 1、注册成为代理之后自动送10U红包。 2、新玩家可享受试玩5次包赔福利（玩法不限，单双、双尾、牛牛均可参与） ，每次投注10-11USDT或100-101TRX，五次投注结束后计算总输赢，赢了归您，输了退您！ 3、爆庄奖励 爆庄奖励 单个账户盈利5万奖励588U/trx 单个账户盈利10万奖励1288U/trx 单个账户盈利20万奖励3288U/trx 单个账户盈利50万奖励8888U/trx 单个账户盈利100万奖励18888U/trx (单个账户为准 当日为准，机器人自动申请领取) 4、牛牛/PC28负分扶持奖励 当日负分1000U，领取亏损的1% 当日负分5000U，领取亏损的2% 当日负分10000U，领取亏损的3% 当日负分1…
💩1,490🤔123👎115🤯109😱109🤬107🤮106😁103
🎊🎊芒果哈希中秋狂欢🎊🎊 举杯邀明月，月圆人团圆，共享中秋月，盛世好佳节! 值此佳节，芒果哈希俱乐部特筹备中秋福利活动，三重好礼乐享不停！ 好礼一：流水奖励 9.10日介绍玩家当日流水打满50W USDT 芒果哈希免费赠送iPhone14一台 介绍获取奖励：即A邀请B，B达标后，A即可获取奖励！ B邀请C，C达标后，B即可获取奖励，A奖励无效。 好礼二：下注奖励 当日下注18局奖励388.88TRX 注：U下注20起为有效投注，TRX100起为有效投注！ 好礼三：邀请奖励 邀请2人，单号流水达25000U，奖励100USDT。 邀请5人，单号流水达50000U，奖励300USDT。 邀请7人，单号流水达70000U，奖励600USDT。 邀请9人，单号流水达100000U，奖励999USDT。 注：TRX流水乘以10计算。 （活动启用日期：9月10号24点后开始，中秋活动启用期间，其余活动暂时取消。）
尊敬的各位俱乐部爱好者们，经过平台系统不断优化改进，为给各位爱好者们带来更好的游戏体验，自9月4号起，推广佣金当日提现当日秒到！ 24⌚️小时的在线客服💁解决一切疑难杂症（最贴心的服务） 365🌍天风雨无阻与您同在，🤝一起进退（最无暇的朋友） 🧧🧧新增流水，负分，邀请，注册送U,包赔（最真诚的福利） 单单⚡️3秒结算，❌无卡款，❌无暗扣，❌无拖欠（最稳定的支付） 🤖机器人与飞机✈️联通，无需网页投注，不担心被授权，所有操作智能执行（最便捷操作） 我有10之最邀请你加入芒果家庭，另外5之最请联系我告知于你🤒🤒
👍1
🍋平台数据迁移完成，可正常进行游戏！ 🏅🏅芒果哈希俱乐部喜迎金秋，回馈社会，满足广大玩家朋友的需求，现推出以上九月福利活动奖励！！福利多多奖励多多，欢迎各位前来领取，平台备足500W美金欢迎亲们前来爆庄！！！！🏆🏆 以上活动自九月1日起正式执行，请各位相互转告！ 官方频道：https://t.me/mangguohash 官方网站：http://www.mghx77.com 播报游戏：https://t.me/MGhash0000
👍1
尊敬的各位俱乐部爱好者们，平台将于九月二日北京时间凌晨四点(一个半小时后)，全面服务迁移，预计时长一个小时，届时充提币功能会关闭，请大家在维护期间暂停投注，感谢大家的理解与配合。
🏅🏅芒果哈希俱乐部喜迎金秋，回馈社会，满足广大玩家朋友的需求，现推出以上九月福利活动奖励！！福利多多奖励多多，欢迎各位前来领取，平台备足500W美金欢迎亲们前来爆庄！！！！🏆🏆 以上活动自九月1日起正式执行，请各位相互转告！ 官方频道：https://t.me/mangguohash 官方网站：http://www.mghx77.com 播报游戏：https://t.me/MGhash0000
尊敬的芒果哈希会员们 经集团老板们商量决定，现下架部分福利活动，现有的福利活动请在机器人里查看和申请。谢谢大家的支持和理解，也感谢你们的一路陪伴！ 🍋🍋官方频道：https://t.me/mangguohash 🍋🍋 平台网站：http://www.mghx77.com
👍1
🔉🔉🔉为给长久以来支持芒果的各位创造良好的游戏环境，经商议将单双游戏玩法更改【⚠️取消后三位字母判定法，字母判定无限前移直到数字出现】 🔉🔉🔉目前平台所有的福利活动请以机器人文字为准。详情查看机器人福利活动栏 游戏限额： USDT：10-30000 TRX：100-300000 🥭金秋来临之际，芒果奖池将备足500W美金供各位前来娱乐，同时配备了🙎🏻♀️24小时专线美女客服，望各位老板能在芒果玩的开心，玩的愉快。
🍾🎊恭祝 神秘大哥 在芒果哈希 喜提130000美金大奖🎊 🌈🌈芒果自上调限不到三日，宾客爆满，爆庄大客接踵而来！平台备足500万美金欢迎您们前来爆庄，亲们，赶快动起您的金手指，超额大奖等着您来领取🎖🎖 🍋芒果哈希竞彩俱乐部，最公平最公正最透明的娱乐方式 ，🏆平台资金雄厚，玩家首选🏆 🔜 平台网站：http://www.mghx77.com/
Showing the 12 most recent of 20 posts we hold for @mangguohash. 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.
Citation-graph rank — 394,181 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“🥭芒果哈希俱乐部🏆” (@mangguohash), 54,132 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/mangguohash.
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.