Channel
@HXYL000
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
9subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001968216276 |
|---|---|
| Type | Channel |
| Username | @HXYL000 |
| Description | USDT红包炸雷群 |
| Created | 23 June 2023 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/HXYL000 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 13:00 | 9 | no change |
| 7 Aug 2026, 10:10 | 9 | first reading |
11 posts held, back to 23 June 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 pageof 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 11 posts for this entry, the most recent from 8 July 2025. An engagement rate over an empty window would be a number about nothing.
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.
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 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 2reactions 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 23 June 2023 to 8 July 2025, 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 28 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
https://t.me/+V6BksXQf2IQzNTA1
https://t.me/HXYL66
https://t.me/+V6BksXQf2IQzNTA1
❤2
⬆️⬆️上方点击进群链接-24小时开车⬆️⬆️
✈️【汇鑫娱乐】- USDT红包扫雷TG群 ✈️ 1️⃣无需注册，上分即可开始游戏，发红包或抢红包 2️⃣小群限注5U-50U💙大群限注20U-1000U，两群余额互通 3️⃣由玩家在群内发送任意指令后，由机器人代发红包 4️⃣雷数可设置0-9任何一个数，比如20-1或20/1均可 5️⃣红包数量固定为6包，抢到雷者固定赔付本金1.8倍 6️⃣本群玩法公益，赢与输都是玩家之间对赌。 7️⃣集团不参与游戏，公平公正，发包盈利者抽水0.05 8️⃣邀请新成员进群邀请者账户自动返现0.1U 9️⃣邀请成员进群上分发包盈利后，邀请者秒返现%2 🔟群聊对话框输入 / 即可生成您的专属代理线。 👉汇鑫娱乐频道: @HXYL000 👉汇鑫娱乐财务: @HXYL999 👉汇鑫在线客服: @HXYL333 👉汇鑫商务合作: @HXYL666
https://t.me/+2E-PCOQlB4szMGJl
https://t.me/+V6BksXQf2IQzNTA1
Channel name was changed to «🧧汇鑫娱乐🧧红包扫雷🧧»
Channel photo updated
Channel created
Showing the 11 most recent of 11 posts we hold for @HXYL000. 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.
@HXYL000 named 2 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“🧧汇鑫娱乐🧧红包扫雷🧧” (@HXYL000), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/HXYL000.
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.