Channel
@hxyc28
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
2,991subscribers
-5,270 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001871544560 |
|---|---|
| Type | Channel |
| Username | @hxyc28 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/hxyc28 |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 14 September 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 13:55 | 2,991 | -493 |
| 13 Sept 2026, 02:15 | 3,484 | -594 |
| 9 Sept 2026, 06:20 | 4,078 | -2,579 |
| 4 Sept 2026, 06:40 | 6,657 | -582 |
| 1 Sept 2026, 00:18 | 7,239 | -250 |
| 29 Aug 2026, 08:18 | 7,489 | -335 |
| 26 Aug 2026, 15:32 | 7,824 | -164 |
| 23 Aug 2026, 06:07 | 7,988 | -272 |
| 20 Aug 2026, 00:32 | 8,260 | -1 |
| 19 Aug 2026, 06:15 | 8,261 | first reading |
12 posts held, back to 12 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 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 12 posts for this entry, the most recent from 21 May 2026. An engagement rate over an empty window would be a number about nothing.
实验室进入页面：预测 → 实验室。可根据自行设置的公式算法进行回溯查看收益。支持常规2.0赔率（大小单双2.0倍，遇13/14降倍或回本）以及1.99满赔率(大小单双1.99倍，小单/大双3.7倍，小双/大单4.315倍，13/14正常赔付),可以直观的看到你的公式算法是否能盈利。如果你有向外购买公式的需求，可以使用这个功能测真伪。如果你是VIP用户，那么还可以点击【历史仿真日历】进行查看近半年的该公式算法的胜负盈利情况！
网站pc28挂机玩家也可以通过首页 → 模式预测，根据设置的模式进行查看模式的盈利情况。还可以看右上角推荐模式的模式列表。每日跟注盈利优先的模式，见好就收，也是可以套利的
迭代更新完成，全体未过期会员用户增加 1h 时间
因为改了机器人的数据结构，需要重新添加一下机器人token，注意查看
机器人的问题改好了。将你的机器人拉到群组后发送 /star 机器人就会弹出命令了。暂时只支持开奖播报、历史查看、遗漏查询。后续开放其它功能！
机器人服务暂时维护一下，晚点开放
哈哈，机器人功能刚上线就被用户反馈问题了啊。命令停止确实存在一些问题。 后面我们会把关闭播报放在用户管理端内进行点击操作，而不是输入：/star stop_get_kj 就停止了 开启播报为用户输入:/start
另外给有想训练预测AI的道友们分享一波加拿大28的开奖历史数据。 大概是从17年到25年一月份的，这些数据足够训练出一个好的AI模型了。 格式自行转换，这边就只放text，包含了开奖数字、类型等，非常的全
File, posted without a caption
API与TG机器人服务
通知：API 数据接口与 TG 机器人服务上线（测试） 为提升接口稳定性与安全性，我们已调整 API 开放策略。需要使用 API 的开发者用户，请按以下路径进入开发者中心： 注册并登录 主页点击 「技术服务」 再点击 「API 数据接口服务」 进入 开发者 API 中心 1) API 调用方式（Token 鉴权） 当前免费开放的 API 将统一采用 Token 方式调用，用于防止恶意滥用与异常请求，降低对服务器的安全风险。 请务必妥善保管 Token，避免泄露或被第三方盗用。 2) 频率与风控策略（普通用户 / 会员用户） 普通用户与会员用户在接口能力上差异不大，主要区别在 防护与频率上限： 普通用户 调用频率：1 秒最多 1 次 当日调用量若明显超过 86,400 次/天，可能触发风控限制（为全接口统一频率策略） 正常使用通常不会受影响，请勿进行高频扫描、爆破式请求等行为 会员用户 调用频率：1 …
技术通知: 数据库服务器新上了100g硬防，开奖已恢复。
Showing the 12 most recent of 12 posts we hold for @hxyc28. 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“加拿大28预测 - 风筝28” (@hxyc28), 2,991 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/hxyc28.
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.