Channel
@hqyl88
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
7,472subscribers
-1,651 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002454583941 |
|---|---|
| Type | Channel |
| Username | @hqyl88 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/hqyl88 |
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 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 2 other registered channels. 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 |
|---|---|---|---|
| @HQYLTG/53612 Jul 2026, 14:22 UTC | @hqyl88/979 · this entry12 Jul 2026, 14:22 UTC | 1.00 | under a minute |
| @hqyl88/981 · this entry15 Jul 2026, 01:05 UTC | @HQYLTG/53815 Jul 2026, 01:05 UTC | 1.00 | under a minute |
| @hqyl88/991 · this entry24 Jul 2026, 03:55 UTC | @HQYLTG/54824 Jul 2026, 03:56 UTC | 1.00 | 72 seconds |
| @hqyl88/992 · this entry26 Jul 2026, 09:28 UTC | @HQYLTG/54926 Jul 2026, 09:28 UTC | 1.00 | under a minute |
| @HQYLTG/55129 Jul 2026, 14:31 UTC | @hqyl88/994 · this entry29 Jul 2026, 14:31 UTC | 1.00 | under a minute |
| @hqyl88/997 · this entry2 Aug 2026, 03:06 UTC | @HQYLTG/5542 Aug 2026, 03:06 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @HQYLTG | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (12–2) |
| @hqyl688 | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (13–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 2 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 18 comparable posts for this entry, running 7 July 2026 to 6 August 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 3, the earliest publisher we hold is @HQYLTG. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 6 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 2 other registered channels, 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 |
|---|---|---|
| 17 Sept 2026, 13:38 | 7,472 | -477 |
| 13 Sept 2026, 09:01 | 7,949 | -774 |
| 9 Sept 2026, 08:40 | 8,723 | -1,184 |
| 3 Sept 2026, 16:37 | 9,907 | +4,266 |
| 31 Aug 2026, 08:02 | 5,641 | -355 |
| 28 Aug 2026, 10:23 | 5,996 | -324 |
| 25 Aug 2026, 08:06 | 6,320 | -753 |
| 22 Aug 2026, 17:56 | 7,073 | -694 |
| 19 Aug 2026, 09:45 | 7,767 | -289 |
| 16 Aug 2026, 18:15 | 8,056 | -663 |
| 13 Aug 2026, 05:07 | 8,719 | -271 |
| 9 Aug 2026, 19:56 | 8,990 | -93 |
| 7 Aug 2026, 00:46 | 9,083 | -40 |
| 6 Aug 2026, 09:21 | 9,123 | first reading |
25 posts held, back to 7 July 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 17 pages 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 25 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
9 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 88.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 88.9% | |
| 👍 | 1 | 11.1% |
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 10 of the 25 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 9 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 7 July 2026 to 19 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.
🙂😛😕🧐🤯🥶😇🤔🙄😑 🧄环球娱乐，始终以信任与信誉为核心 🕯活动内容：电子游艺嘉奖3 完成有效下注并达到指定的中奖倍数，即可获得“加赠彩金”，最高可领取 👋👋👋👋 😆达 28 倍： 加赠 1 倍投注额🫚 😆达 60 倍： 加赠 2 倍投注额🫚 😆达 100 倍：加赠 3 倍投注额🫚 😆达 150 倍：加赠 8 倍投注额🫚 😆达 200 倍：加赠 12 倍投注额🫚 😆达 300 倍：加赠 30 倍投注额🫚 🌭温馨提示 七夕活动火热进行中 🔒 七夕有礼 · 为爱放送 🔒 浪漫七夕 · 为爱加码
🙂😛😕🧐🤯🥶😇🤔🙄😑 👓环球娱乐会员日｜每月逢「👋」必发 🕯每月 8日、18日、28日 ✈️最高可领取 👋👋👋👋 🚶奖励于北京时间18:00自动发放，记得准时登录平台领取您的专属福利哦！ 🐷感谢每一位会员一路相伴，环球娱乐，与您共享精彩时刻，共赢财富未来！ 🩲点击查看会员日彩金派发详情
❤2👍1
🕐🕑😁😀🤩😨🤔🥳🙄🤯 🔒 七夕情人节 · 浪漫相伴 甜蜜相约 · 七夕好礼送不停 🔒 七夕有礼 · 为爱放送 🧄 约会基金 · 登录即领 最高领取 18,888 🔒 浪漫七夕 · 为爱加码 🧄 当天投注 · 豪礼加赠 最高领取 16888 🕯 领取方式 😇 环球娱乐全体会员 🧄 登录即可领取专属宝箱
🕐🕑😁😀🤩😨🤔🥳🙄🤯 🧄夜间专属 · 存款加码礼 😭 01:00–06:00 😆 每一笔入场，都是加倍回报 😮💨 累存即领：👋👋👋👋 🙈 一倍流水 · 即刻提现 🦤 夜深不打烊，财富不停涨
🙂😛😕🧐🤯🥶😇🤔🙄😑 🫚【每日红包 · 全天开抢】 🦜全天开放，简单3步，红包直接拿！ 😐 打开 环球娱乐 APP 🕯 下载地址： 8592XZ.COM 😵💫 任意金额充值即可参与 🤡完成充值 → 立即开抢 🧄 最高红包 8888！ 🥳 每日可参与 · 全天候开放 · 惊喜等你拿！
🙂😛😕🧐🤯🥶😇🤔🙄😑 😬电子喜讯 ✖️ 🪲🪳 🥳 热烈恭喜 ID：【******7】老板于8月11日征战PG电子充值😵💫🤭🤭🤭😍入场，火力全开、持续奋战，一路高歌猛进，成功斩获丰厚盈利，喜提👎😐😐🤦♂️🤦♂️😍 🧄顺势吃路 · 稳定拿分 🥐赢钱就是爽，提现就是稳！实力看得见！ 🍫实力平台，大额无忧，一键申请，火速到账！在环球娱乐我们不仅见证传奇，更保障您的每一分收益。
🙂😛😕🧐🤯🥶😇🤔🙄😑 🙂 环球娱乐・每日签到 天天领钱 🐦🔥 坚持打卡好礼天天领 🌵 🫚每日签到享好礼🫚 😘签到 第一天 😵💫 😘签到 第二天 👋 😘签到 第三天 😐👋 😘签到 第四天 😵💫👋 😘签到 第五天 🤡👋 😘签到 第六天 👏👋 😘签到 第七天 👍👋 🐋活动说明 🦊每日充值、有效投注满足活动条件，即可参与签到领取对应奖金，单日最高 👍👋 🦊仅限棋牌、捕鱼、电子游戏参与签到活动，此活动属连续签到活动，若期间中断，将从第😐天重新开始
🙂😛😕🧐🤯🥶😇🤔🙄😑 🥴 电子狂欢每日首充加赠 10% 😏 ⛄️ 高额回馈 彩金奖励无上限 🥴 每日首笔单笔充值满50+ 🫚 即可申请 10 % 彩金回馈 🚶 第一时间掌握最新福利 🚶 第一时间参与高回馈活动 🙈 别错过 环球娱乐 电子游戏每日10%的机会
🙂😛😕🧐🤯🥶😇🤔🙄😑 🙂环球娱乐 · 实力铸就顶级平台 🔒百亿保障 · 秒提无忧 · 全程透明 🧴赢多少提多少 · 到账快 · 不拖不压 🥴【会员首存彩金】😏 🧐首存≥50赠送👋 🧐首存≥100赠送😵💫👋 🧐首存≥500赠送👎👋 🧐首存≥1000赠送👋👋 🧐首存最高可赠送😐👋👋👋👋 🥴【二存三存彩金】😏 😘二存≥200赠送😐👋 😘二存≥1000赠送👋👋 😘二存≥5000赠送😐👋👋 😘三存≥1000赠送👋👋 😘三存≥5000赠送😐👋👋 😘三存≥20000赠送👋👋👋 😘二存三存最高可赠送👋👋👋👋
🙂😛😕🧐🤯🥶😇🤔🙄😑 😇 CHOICE真人视讯｜玩家实战战绩 🧄 老板火力全开，顺势进长龙，庄闲连续通赢，连续命中！ 🥳 充值👍🤭🤭🤭🤭😍盈利提现：🤡🤭🤭🤦♂️😵💫🤦♂️😍 🍑（约合😵💫🤭🤡万人民币） 🍫【官方播报】别再为小平台买单！很多平台能赢却不能提，真正靠谱的平台，提现速度才是核心。 🍫官方网站：8592.COM 🤩官方频道：@HQYL688 🤩官方客服：@HQKF1 🤩官方招商：@HQZS88 🤩官方飞投：@HQTOPbot 🤩DJ音乐频道：@HQYLDJ 😀😃😄😁🥹😅 @HQYLAV5
🕐🕑😁😀🤩😨🤔🥳🙄🤯 😵 官方网址： 8592.COM 🌈 TG直连 ｜飞投小程序 😇 官方入口：@HQTOPbot 🐕 一站式综合娱乐平台 🙈 视讯 · 电子 · 棋牌 · 捕鱼 · 体育 · 彩票 😱TG内直接开启 · 无需下载APP 😱系统稳定 · 操作流畅 😱充提快捷 · 资金安全 🦤 7×24小时在线客服 🐷 客服专线：@HQKF1 ⛄️ 品牌稳定运营 · 实力平台 🔒 用户真实验证 · 长期口碑 🍜 立即体验小程序：@HQTOPbot 🙈
❤2
😇电子喜讯 ✖️ 🕷🕸 🐕恭喜会员【****6**】充值😐🤭🤭🤭在PP电子，运势爆发，火力全开！倍数层层叠加，一路稳赢，成功提款🤡👆😵💫🤡👍 😘连线不断，输出不停 😘小额切入，重拳兑现 😘这不是运气——这是 PP电子的暴力美学，真正的电子爽感！ 🍫【官方播报】：环球娱乐始终为玩家提供公平、透明、高倍率的极致游戏体验，每一注都可能改写财富故事！ 🍫官方网站：8592.COM 🤩官方频道：@HQYL688 🤩官方客服：@HQKF1 🤩官方招商：@HQZS88 🤩官方飞投：@HQTOPbot 🤩DJ音乐频道：@HQYLDJ 😀😃😄😁🥹😅 @HQYLAV5
Showing the 12 most recent of 25 posts we hold for @hqyl88. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 166 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“环球娱乐-官方频道” (@hqyl88), 7,472 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/hqyl88.
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.