Telegram RegisterThe public register of Telegram

Channel

YW哈希官方频道

@AEONHASH

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

4,801subscribers

-59 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002432449489
TypeChannel
Username@AEONHASH
Description官方客服: @a111 YW哈希双向客服: @YWHXSX_bot 官方频道: @AEONHASH 观战频道: @ywhxgz 投注机器人: @ywhxkf
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/AEONHASH

Topic

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Observations

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.

Views per post sit far above this size band

15,600 average views per post against 4,801 subscribers — an engagement rate of 325.9%. Across the 2,355 registered channels in the same cohort — 3,164–9,990 subscribers, posting mainly in Chinese — the middle half sit between 2.67% and 19.2%, with a median of 8.16%.

What this was computed from
Window30 days (13 July 2026 12 August 2026)
Posts measured24 of 24 published in the window (0 exact, 24 rounded by Telegram)
Views totalled375,520
Mature posts only325.9% over 24 posts read at least 24h after publication
Subscribers4,801 measured 10 August 2026
Cohortb3162:zho · 2,355 channels · p10 0.77% · p25 2.67% · p50 8.16% · p75 19.2% · p90 38.6%
Position in cohort99.788th percentile · 39.9× the cohort median
Uncertainty±0.034% of the figure, from Telegram’s rounding
Post languageChinese · 100.0%of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 12 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.

Growth

4,8014,8604,830.57 August 2026 — 4,860 subscribers7 August 2026 — 4,856 subscribers10 August 2026 — 4,801 subscribers7 August 202610 August 2026
3 measurements spanning 3 days, net -59. 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,792–4,869 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 10:454,801-55
7 Aug 2026, 16:024,856-4
7 Aug 2026, 14:174,860first reading

Engagement

24 posts held, back to 3 August 2026the 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
325.9%
avg views ÷ 4,801 subscribers
Avg views / post
15,600
24 posts measured
Reaction rate
0.005%
reactions ÷ views · ER floor
Posts in window
24
of 24 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. It is computed over the 2 of 24 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held24 (3 August 202610 August 2026)
Views total375,520
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 05:19 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
138
Videos
18
Links
46

Lifetime counters from Telegram’s own channel header, read 12 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.

Video runtime
3m 07s
Average length
3m 07s

Measured directly from 1 video 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

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
150.0%
🥰150.0%

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 2 of the 24 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 24 most recent posts we hold, published 3 August 2026 to 10 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.

Recent posts

10 Aug 2026, 16:51 UTC≈11,400 viewsread 12 August 2026
Photo

🤩🤩🤩🤩🤩 😂昨日喜报😂 🔥恭喜哈希界大佬xSYLfD强势登榜 💰昨日累计盈利:37992USDT 😀祝大哥乘风破浪,稳健投注,日日爆庄! 🛡百万奖池链上可查 ⚡️⚡️⚡️⚡️您身边的USDT取款机 ❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️ ━━━━━━━━━━━━━━ 🤩官方客服:@a111 🤩观战频道:@ywhxgz

10 Aug 2026, 07:52 UTC≈12,600 viewsread 12 August 2026
Photo

😂连胜喜报😂 🔥恭喜哈希界大佬 aNt7EY 强势豪取九连红,势不可挡! 💰九把累计盈利:134442USDT 😀祝大哥乘风破浪,稳健投注,日日爆庄! 🛡九连红战绩查看 ⚡️⚡️⚡️⚡️您身边USDT提款机 ❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️ ━━━━━━━━━━━━━━ 🤩官方客服:@a111 🤩观战频道:@ywhxgz

9 Aug 2026, 09:36 UTC≈12,800 viewsread 12 August 2026
Photo

🤩🤩🤩🤩🤩 😂昨日喜报😂 🔥恭喜哈希界大佬aNt7EY强势登榜 💰昨日累计盈利:47324USDT 😀祝大哥乘风破浪,稳健投注,日日爆庄! 🛡百万奖池链上可查 ⚡️⚡️⚡️⚡️您身边的USDT取款机 ❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️ ━━━━━━━━━━━━━━ 🤩官方客服:@a111 🤩观战频道:@ywhxgz

8 Aug 2026, 07:23 UTC≈14,500 viewsread 12 August 2026
Photo

🫰 防诈骗公告🫰 😊近期发现,不法分子冒充本平台玩家,通过客服获取玩家信息后,假冒本平台离职人员,以“高返水”“高福利”“高返奖”等虚假承诺诱导玩家转入其平台。 😊经了解,此类平台实为诈骗平台(俗称“杀猪盘”),其返奖地址余额最多十几万U,且赔率自动浮动。当玩家开始盈利时,系统会恶意调整赔率,甚至降至1.5倍等任意赔率,以达到控制玩家收益、诱导持续充值的目的,最终造成资金损失。 💡本平台郑重声明:TRX哈希为假冒骗子平台,与本平台无任何关联。 该平台利用“包赔”等话术吸引玩家投注,并冒用本平台返奖地址进行验资,制造虚假资金实力。安全测试方式可向其玩法地址投注1笔2TRX验证是否为本集团资金池地址进行派奖。

6 Aug 2026, 16:41 UTC≈15,800 viewsread 12 August 2026
Photo

🤩🤩🤩🤩🤩 😂昨日喜报😂 🔥恭喜哈希界大佬8aBwv 强势登榜 💰昨日累计盈利:41641 USDT 😀祝大哥乘风破浪,稳健投注,日日爆庄! 🛡百万奖池链上可查 ⚡️⚡️⚡️⚡️您身边的USDT取款机 ❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️ ━━━━━━━━━━━━━━ 🤩官方客服:@a111 🤩观战频道:@ywhxgz

4 Aug 2026, 13:21 UTC≈18,100 views1 reactionsread 12 August 2026
Video

🤩🤩🤩🤩🤩 🤩机器人使用教程🤩 🤩USDT / TRX 转账即投注 无需注册|无需上下分|转账即玩, 一笔一返|3秒自动返奖 🚀3分钟快速了解「永旺哈希机器人」 💡全自动结算 秒速返奖 💡全程智能运行 无人工干预 💡24小时稳定运行 安全高效 🛡真正公平 · 真正公开 · 真正透明 🛡基于区块链哈希开奖机制, 每一期开奖结果均可链上查询、公开验证。 🔥 选择永旺哈希娱乐 🔥 体验风靡全球的区块链多元化娱乐玩法。

🥰1

3 Aug 2026, 11:39 UTC≈18,800 viewsread 12 August 2026
Photo

⚡️押庄闲限额: 2-5万T 30-2万U ⚡️押和限额:2T-1万T 30U-5千U ⚡️赔率: 押庄/闲 1:2 押和 1:7.5 ------------------------------------- ⚡️规则: ⚡️区块哈希最后5位字符为开奖结果 ⚡️根据转账金额的“个位数”判定押注类型的庄、闲或者和 ⚡️前2位为庄家,中间为间隔符,后两位为闲家 ⚡️两位字符相加得点(字母为0)⚡️⚡️比较 9点最大 0点最小 同点为和 ------------------------------------- 投注地址(⚡️点击即可复制⚡️): TRdXGKi1f2tgP8kdJDHkoKfob48HxEEEYW

3 Aug 2026, 11:39 UTC≈18,800 viewsread 12 August 2026
Photo

⚡️限额:2T-5万T 30U-2万U ⚡️赔率:1.97 ------------------------------------- ⚡️规则: ⚡️转账交易产生的区块哈希值(Block hash)最后5位字符作为开奖结果;字母代表 10 ⚡️前 3 位为庄,后 3 位为闲,中间 1 位共用 ⚡️三位字符相加得点(字母为10)⚡️⚡️比较 10点最大 1点最小 ------------------------------------- 投注地址(⚡️点击即可复制⚡️): TTqB9MivvEkqUeroGNbc4saGQPsQGGGGYW

3 Aug 2026, 11:39 UTC≈18,800 viewsread 12 August 2026
Photo

⚡️押庄闲限额: 2T-10万T 30U-3万U ⚡️押和限额:2T-1万T 30U-5千U ⚡️赔率: 押庄/闲 1:1.98 押和 1:7.5 ------------------------------------- ⚡️规则: ⚡️区块哈希最后5位字符为开奖结果 ⚡️根据转账金额的“个位数”判定押注类型的庄、闲或者和 ⚡️前2位为庄家,中间为间隔符,后两位为闲家 ⚡️两位字符相加得点(字母为0)⚡️⚡️比较 9点最大 0点最小 同点为和 ------------------------------------- 投注地址(⚡️点击即可复制⚡️): TNnuCLhLYAz1TEmtZN3WEiwhZHHhQFFFYW

3 Aug 2026, 11:39 UTC≈18,700 viewsread 12 August 2026
Photo

⚡️限额:2T-10万T 30U-3万U ⚡️赔率:1~10倍×0.98 ------------------------------------- ⚡️规则: ⚡️转账交易产生的区块哈希值(Block hash)最后5位字符作为开奖结果;字母代表 10 ⚡️前 3 位为庄,后 3 位为闲,中间 1 位共用 ⚡️1-9几点即几倍,合计整数为⚡️⚡️10倍 ------------------------------------- 投注地址(⚡️点击即可复制⚡️): TME7EumNDDC7tCkymvp2rWLJsRiReDDDYW

3 Aug 2026, 11:39 UTC≈18,700 viewsread 12 August 2026
Photo

⚡️限额:2T-10万T 30U-3万U ⚡️赔率:1:2 ------------------------------------- ⚡️规则: ⚡️转账交易产生的区块哈希值(Block hash)最后2位字符作为开奖结果。 ⚡️如获得【数字+字母】或【字母+数字】,则视为中奖 ------------------------------------- 投注地址(⚡️点击即可复制⚡️): TRfwBYkqxtwWtCWXQGQvju5jnhHruCCCYW

3 Aug 2026, 11:39 UTC≈18,700 viewsread 12 August 2026
Photo

⚡️限额:2T-5万T 30U-2万U ⚡️赔率: 1:1.95 ------------------------------------- ⚡️规则: ⚡️转账交易产生的区块哈希值(Block hash)最后1位数字(忽略字母)作为开奖结果 ⚡️数字0、1、2、3、4识別为押小 ⚡️数字5、6、7、8、9识别为押大 ⚡️根据转账数额“个位数”判定押注类型 ⚡️如投注 1000 USDT “个位数”识别为0,择小(个位数0-4判定为押小) ⚡️如投注 1009 USDT“个位数”识别为9,押大(个位数5-9判定为押大) ------------------------------------- 投注地址(⚡️点击即可复制⚡️ ): TVd2xv8chzm4Tfha77c4aAALMRBnYBBBYW

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

Citation-graph rank — 388,064 of 1,151,006entries 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.

Mentions

Named by 2 registered channels — 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.

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

“YW哈希官方频道” (@AEONHASH), 4,801 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/AEONHASH.

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.