Channel
@HH_XXHY
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
57subscribers
+50 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004498556386 |
|---|---|
| Type | Channel |
| Username | @HH_XXHY |
| Created | 8 August 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/HH_XXHY |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 18:47 | 57 | +50 |
| 12 Aug 2026, 16:45 | 7 | no change |
| 10 Aug 2026, 01:15 | 7 | first reading |
11 posts held, back to 8 August 2026 — 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 pageof Telegram’s post history, 20 posts per page.
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 1 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 11 (8 August 2026 – 12 August 2026) |
| Views total | 525 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 16:45 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 1 of the 11 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 8 August 2026 to 12 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.
含含核验机器人已完全恢复 🤖 @HH_XXHY_bot 各位支持我的老板，我表示非常的抱歉😥由于所有的运行代码和服务器的运行、管理与维护，全权有我一人操办，再有的时候确实很忙。 今天下午机器人其实已经不停机更新了，不清楚各位各位老板们发现没，一直到目前，所有的功能全部可以正常运行，为了表达歉意，今晚来私信我的，发ID给我，都免费给1️⃣0️⃣0️⃣积分，希望各位老板往后可以多多支持，后续含含机器人🤖也定会添加更多的核验功能供各位老板使用🤝🤝🤝 有意向的老板可以联系我👉 @MHOVO888 目前功能：如图👆
Sticker, posted without a caption
我没招了，兄弟们，我一直忙到现在，等会还要出去一趟，机器人什么时候好了，在通知吧，反正我现在没时间写代码，一个人办事太忙了
❤1
停机更新
机器人有点问题，可以给我反馈，今晚不停机跟新
含含核验机器人已上架🎉🎉🎉 🤖 @HH_XXHY_bot 目前功能： 2ys - 机主2要素核验 3ys_1 - 机主3要素单次核验 3ys_2 - 机主3要素批量核验 12306 - 12306批量核验 invoice - 查询企业银行账户 核验机器人已经上架啦，无限制无遗漏不抽风，需要充值联系 @MHOVO888
昨晚由于接口被诈骗犯【同塔】【小云朵】【无情】均属同一人，且是惯犯❗️被🤬恶意调用🤬 导致机器人🤖目前功能全部用不了，接口已被拒绝访问❌ 机器人将于12点，重新调取新的接口，更改所有的信息，原本的接口就当喂狗了 有认识以上诈骗犯的可以转告他，他就是个👉🤡，请各位老板请谨慎对待，慎防诈骗，他们的机器人更是不要使用，以免随时跑路，损失的是各位老板的米💵💵💵
即将上批量核验机器人 功能： 2ys - 机主2要素核验 3ys_1 - 机主3要素单次核验 3ys_2 - 机主3要素批量核验 12306 - 12306批量核验 invoice - 查询企业银行账户
🎰 含含核验机器人开业福利🎉🎉 📮 抽奖条件: 🎫 加入-含含核验频道 🎁 奖品内容: 卡反 × 5 2usdt × 5 码反 × 5 机主 × 10 含含核验机器人天会员×5 × 5 😊 参与人数: 开奖需要参与人数到达 100
Channel photo updated
Channel created
Showing the 11 most recent of 11 posts we hold for @HH_XXHY. 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 — 1,222,430 of 1,481,306entries 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.
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.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“含含核验频道” (@HH_XXHY), 57 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/HH_XXHY.
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.