欧罗巴杯23:00 古比斯VS克拉约瓦 推荐:客队-0 欧罗巴杯01:00 波兹VS克拉克 推荐:全场大3.5球 2026.8.6 欧协联02:00 阿贾克斯VS谢尔伯恩 推荐:全场大3.75球 欧协联02:30 卢加诺VS鲁纳维克 推荐:全场大3.5球 欧罗巴杯03:00 本菲卡VS哈茨 推荐:全场大3.75球
❤1

Channel
@hongdan999
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,225subscribers
-124 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002062336925 |
|---|---|
| Type | Channel |
| Username | @hongdan999 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/hongdan999 |
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 62% 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 |
|---|---|---|
| 19 Sept 2026, 03:58 | 3,225 | +19 |
| 14 Sept 2026, 11:58 | 3,206 | +5 |
| 11 Sept 2026, 07:21 | 3,201 | +19 |
| 6 Sept 2026, 03:01 | 3,182 | +4 |
| 1 Sept 2026, 23:45 | 3,178 | +15 |
| 30 Aug 2026, 06:57 | 3,163 | +1 |
| 27 Aug 2026, 05:54 | 3,162 | -80 |
| 24 Aug 2026, 15:29 | 3,242 | -148 |
| 20 Aug 2026, 22:54 | 3,390 | -15 |
| 17 Aug 2026, 23:18 | 3,405 | +25 |
| 14 Aug 2026, 21:05 | 3,380 | +23 |
| 11 Aug 2026, 01:41 | 3,357 | +8 |
| 7 Aug 2026, 18:17 | 3,349 | no change |
| 7 Aug 2026, 18:06 | 3,349 | first reading |
20 posts held, back to 14 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 1 page 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
60 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 31.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 19 | 31.7% | |
| 👍 | 16 | 26.7% | |
| 💩 | 16 | 26.7% | |
| 👎 | 7 | 11.7% | |
| 👏 | 1 | 1.67% | |
| 🔥 | 1 | 1.67% |
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 13 of the 20 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 60 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 14 July 2026 to 6 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.
欧罗巴杯23:00 古比斯VS克拉约瓦 推荐:客队-0 欧罗巴杯01:00 波兹VS克拉克 推荐:全场大3.5球 2026.8.6 欧协联02:00 阿贾克斯VS谢尔伯恩 推荐:全场大3.75球 欧协联02:30 卢加诺VS鲁纳维克 推荐:全场大3.5球 欧罗巴杯03:00 本菲卡VS哈茨 推荐:全场大3.75球
❤1
波兰杯23:30 瓦塔波VS雷索维亚 推荐:全场大3球 2026.8.5 欧冠杯00:30 奥胡斯VS萨巴赫 推荐:主队-0.75 波兰杯01:45 斯凯尔VS索克尔克 推荐:主队-1 欧冠杯02:00 费内巴切VS格拉茨 推荐:全场大3球 冰岛03:15 哈夫纳夫VS雷克雅未克 推荐:全场大4球
东南锦18:00 缅甸VS老挝 推荐:全场大4球 2026.8.4 球会友谊19:00 济州VS拜仁慕尼黑 推荐:主队+3 东南锦21:00 菲律宾VS泰国 推荐:全场大3球 欧冠杯02:00 萨格勒布VS考诺萨 推荐:全场大3球 欧冠杯02:00 圣吉罗斯VS博德闪耀 推荐:全场大3球 玻利甲03:00 学术VS奥鲁罗 推荐:全场大3.5球
❤5
东南锦18:30 柬埔寨VS东帝汶 推荐:全场大3球 2026.8.3 东南锦21:30 印度尼西亚VS越南 推荐:客队-0 乌克超23:00 矿工VS库德里夫卡 推荐:全场大3球 罗甲23:30 克卢日VS博托沙尼 推荐:主队-0.5 芬超00:00 塞伊奈VS赫尔辛基 推荐:全场大3球 挪甲01:00 兰黑姆VS海于格松 推荐:全场大4球
韩K联18:30 蔚山VS安养 推荐:全场大2.5球 2026.8.2 中超19:35 辽宁铁人VS上海申花 推荐:全场大3.5球 丹麦超20:00 中日德兰VS霍森斯 推荐:全场大3球 瑞典甲21:00 北欧联VS卢恩斯基尔 推荐:全场大3球 挪甲23:00 利恩VS松达尔 推荐:全场大3.75球 挪超01:15 布兰VS罗森博格 推荐:全场大3球
❤2
韩K联18:30 全北现代VS首尔 推荐:全场大2.5球 2026.8.1 中超19:35 上海海港VS山东泰山 推荐:全场大3.5球 中超19:35 北京国安VS浙江绿城 推荐:全场大3.5球 瑞典超21:00 赫根VS卡尔马 推荐:全场大3球 瑞典甲23:00 北雪平VS赫尔辛堡 推荐:全场大3球 美职业07:30 纽约红牛VS奥兰多城 推荐:全场大3.75球
东南锦18:00 东帝汶VS印度尼西亚 推荐:全场大5.5球 2026.7.31 中超19:35 河南队VS大连英博 推荐:全场大3球 东南锦21:00 越南VS新加坡 推荐:全场大3.5球 芬甲23:30 埃克纳斯VS克鲁比 推荐:全场大3球 丹麦甲01:00 格莱萨克瑟VS弗雷德 推荐:全场大3球 挪超03:00 博德闪耀VS利勒斯特 推荐:全场大3.75球
💩2
澳足总17:30 悉尼VS布里斯班狮吼 推荐:全场大3球 2026.7.30 欧协联22:00 杜堡尔VS帕纳瓦兹 推荐:主队-1.5 欧罗巴杯00:00 特拉维夫VS谢里夫 推荐:全场大3球 欧协00:30 塔林利瓦迪亚VS哥德堡 推荐:全场大3球 欧协联01:00 吉奥里VS阿特比森 推荐:全场大3.5球 欧协02:00 阿贾克斯VS伏伊伏丁那 推荐:全场大3.5球
球会18:00 大阪樱花VS多特蒙德 推荐:全场大3.75球 2026.7.29 韩国杯18:00 蔚山市民VS蔚山 推荐:全场大3球 芬甲23:30 米克力VS卡亚尼卡帕 推荐:全场大2.75球 欧冠杯01:00 波兹南莱赫VS奥胡斯 推荐:主队-0.75 欧冠杯02:00 红星VS拉恩 推荐:全场大3.75球
印尼总16:30 淡滨尼流浪者VS马兰 推荐:全场大3球 欧冠杯23:00 古比斯VS萨巴赫 推荐:主队+0.25 欧冠杯00:00 林肯红魔VS米亚尔比 推荐:全场大2.75球 瑞典甲01:00 赫尔辛堡VS北欧联 推荐:主队-0 欧冠杯02:00 萨格勒布VS图恩 推荐:全场大3球 欧冠杯02:45 哈茨VS格拉茨风暴 推荐:全场大3球
💩4
中超19:00 云南玉昆VS深圳新鹏城 推荐:全场大3.5球 2026.7.26 中超19:35 山东泰山VS河南队 推荐:主队-0.5 瑞典20:00 布洛马波卡纳VS哈马比 推荐:全场大3球 丹麦20:00 桑德捷斯基VS中日德兰 推荐:全场大3球 挪甲23:00 松达尔VS兰黑姆 推荐:全场大3.75球 塞尔超01:00 红星VS伏伊伏丁那 推荐:全场大3.5球
❤3
澳维超17:30 黑德堡VS乔治十字 推荐:全场大3球 2026.7.24 东南锦20:00 柬埔寨VS新加坡 推荐:全场大3球 芬超00:00 雅罗VS塞伊奈约基 推荐:客队-0 瑞典超01:00 瓦斯特拉斯VS奥尔 推荐:全场大3球 瑞士甲01:30 纳沙泰尔VS克里恩斯 推荐:全场大3.5球 瑞士甲02:15 温特图尔VS伊韦尔东 推荐:全场大3球
Showing the 12 most recent of 20 posts we hold for @hongdan999. 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 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“红单推荐(给老子红)” (@hongdan999), 3,225 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/hongdan999.
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.