2026.11.3 足球早盘推荐 亚冠精英15:45 纽卡斯尔喷气机VS上海海港 推荐:主队+0.5 亚冠精英20:15 河内公安VS京都不死鸟 推荐:全场大2.75球 亚冠联2 00:00 侯塞因VS巴格达警察 推荐:全场大2.25球 丹麦杯01:00 宁比VS兰讷斯 推荐:全场大3球 欧冠杯01:45 顿涅茨克矿工VS葡萄牙体育 推荐:主队+0.5 欧冠杯01:45 拉塔萨雷VS斯图加特 推荐:全场大3.5球 埃及联杯02:00 恩彼VS佩特雷姆 推荐:全场大2球 欧冠杯04:00 马德里竞技VS拜仁 推荐:全场小3.25球 欧冠杯04:00 巴塞罗那VS阿斯顿维拉 推荐:全场大4球 欧冠杯04:00 林茨VS布拉迪斯拉发 推荐:全场大3.5球

Channel
体育电竞赛事推单
@ATYTD88
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
23,979subscribers
-1,754 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002137414728 |
|---|---|
| Type | Channel |
| Username | @ATYTD88 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 August 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 47 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/ATYTD88 |
Topic
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 07:31 | 23,979 | -29 |
| 2 Nov 2026, 07:26 | 24,008 | -45 |
| 1 Nov 2026, 08:20 | 24,053 | -177 |
| 31 Oct 2026, 10:18 | 24,230 | -185 |
| 30 Oct 2026, 10:39 | 24,415 | -233 |
| 29 Oct 2026, 08:19 | 24,648 | -108 |
| 28 Oct 2026, 03:58 | 24,756 | -204 |
| 27 Oct 2026, 03:04 | 24,960 | -207 |
| 26 Oct 2026, 03:47 | 25,167 | -231 |
| 25 Oct 2026, 01:08 | 25,398 | -194 |
| 24 Oct 2026, 01:10 | 25,592 | -284 |
| 23 Oct 2026, 00:28 | 25,876 | -270 |
| 21 Oct 2026, 20:37 | 26,146 | -214 |
| 20 Oct 2026, 12:37 | 26,360 | -276 |
| 19 Oct 2026, 10:48 | 26,636 | -152 |
| 18 Oct 2026, 14:06 | 26,788 | -119 |
| 17 Oct 2026, 17:39 | 26,907 | -405 |
| 16 Oct 2026, 15:31 | 27,312 | -170 |
| 15 Oct 2026, 12:28 | 27,482 | -235 |
| 14 Oct 2026, 13:38 | 27,717 | first reading |
Engagement
144 posts held, back to 31 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 124 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.61%
- avg views ÷ 23,979 subscribers
- Avg views / post
- 1,580
- 38 posts measured
- Reaction rate
- 0.054%
- reactions ÷ views · ER floor
- Posts in window
- 38
- of 144 held
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 7 of 38 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 November 2026 |
|---|---|
| Posts held | 144 (31 July 2026 – 3 November 2026) |
| Views total | 60,213 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Nov 2026, 05:25 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.
What this channel posts
- Video runtime
- 4s
- Average length
- 4s
Measured directly from 1 video 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.
Reaction mix
17 reactions across 15 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 17 | 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 21 of the 144 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 17 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 144 most recent posts we hold, published 31 July 2026 to 3 November 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.
Recent posts
2026.11.1 足球早盘推荐 马来超16:45 檳城VS马六甲 推荐:全场大2.75球 俄超18:00 奥伦堡VS莫斯科中央陆军 推荐:客队-0.25 意甲19:30 科莫VS威尼斯 推荐:全场大3.5球 西甲21:00 赫塔菲VS塞维利亚 推荐:客队-0.25 意甲22:00 弗洛西诺尼VS都灵 推荐:全场大3.5球 西甲23:15 桑坦德竞技VS皇马 推荐:客队-2 法甲00:15 里昂VS昂热 推荐:全场大3球 比甲01:30 洛默尔VS根特 推荐:全场大2.5球 挪超02:15 瓦勒伦加VS特罗姆瑟 推荐:全场大3球 法甲03:45 马赛VS图卢兹 推荐:全场大3球
2026.10.31 足球早盘推荐 英超20:30 切尔西VS曼彻斯特联 推荐:客队+0.5 西甲21:00 莱万特VS马德里竞技 推荐:全场大3球 德甲22:30 勒沃库森VS斯图加特 推荐:全场大3.5球 德甲22:30 云达不莱梅VS霍芬海姆 推荐:客队0 英超23:00 曼彻斯特城VS布莱顿 推荐:全场大3.5球 意甲01:00 乌迪内斯VS罗马 推荐:全场大3球 德甲01:30 拜仁慕尼黑VS多特蒙德 推荐:全场大3.5球 奥甲02:30 林茨VS蒂罗尔 推荐:全场大3.5球
2026.10.30 足球早盘推荐 马来超16:00 汶莱VS森美兰州 推荐:全场大3球 澳超17:00 布里斯班VS奥克兰 推荐:客队-0 捷U1917:15 杜克拉布拉格VS布拉格斯巴达 推荐:全场大3.5球 越南联19:00 北宁交通VS黄安嘉莱 推荐:主队-0.5 巴林超23:00 阿尔里法VS拿杰玛 推荐:全场大3球 俄青联00:00 莫斯科迪纳摩VS圣彼得堡 推荐:全场大4球 卡塔尔联00:30 萨德VS艾沙姆 推荐:全场大3.5球 法甲02:00 勒阿弗尔VS巴黎圣日耳曼 推荐:全场大3.5球 挪超02:00 波杜基林特VS维京 推荐:全场大3.75球 德甲03:30 埃弗斯堡VS美因茨 推荐:全场大3球
❤1
2026.10.29 足球早盘推荐 亚冠联2 18:00 淡滨尼流浪者VS柴桢 推荐:全场大3球 亚冠联2 20:15 金边VS杰志 推荐:全场大3球 丹麦杯20:30 奥胡斯VS哥本哈根 推荐:客队-1.5 沙特联22:35 塞哈特海湾VS哈森姆 推荐:全场大2.5球 埃及超01:00 金字塔VS瓦迪格拉 推荐:全场大2.5球 芬超01:00 古比斯VS格尼斯坦 推荐:全场大3球 瑞典超01:30 哈马比VS天狼星 推荐:全场大3球 意甲01:30 弗洛西诺尼VS莱切 推荐:全场大3.5球 荷兰杯01:45 高沙根男生VS乌德勒支 推荐:客队-1.25 意甲03:45 佛罗伦萨VS亚特兰大 推荐:全场大3球
— 创作者中心 · 发视频赚USDT — 将超级引擎 @CJYQ 设置成管理员可收录您的频道/群组/让您的视频内容展现在小程序曝光获得流量 👇点击按钮体验视频号MiniApp吧👇
2026.10.28 足球早盘推荐 亚冠18:00 鹿岛鹿角VS浦项制铁 推荐:全场大3球 土杯18:00 卡斯36士邦VS安塔利亚 推荐:全场大3.75球 白俄超19:00 伊斯克VS明斯克迪纳摩 推荐:客队-1.5 丹麦杯20:30 巴布安特VS霍森斯 推荐:主队+1 科威特22:30 阿拉比VS法哈西尔 推荐:全场大3球 爱沙甲00:00 派尔努瓦普斯VS库雷撒勒 推荐:全场大3球 意甲01:30 威尼斯VS国际米兰 推荐:全场大3.5球 荷兰杯01:45 鹿特丹斯巴达VS锡塔德命运 推荐:全场大3球 意甲03:45 热那亚VS尤文图斯 推荐:客队-0.75 英联杯04:00 利物浦VS切尔西 推荐:全场大3球
老赵✨晚场足球精选10/27 意甲 ⏰01:30 队伍:萨索洛 vs 拉齐奥 推荐:拉齐奥 -0/0.5 重心:❤️❤️❤️❤️❤️ 瑞典超 ⏰02:00 队伍:AIK索尔纳 vs 埃尔夫斯堡 推荐:AIK索尔纳 +0.5 德国杯 ⏰03:45 队伍:多特蒙德 vs 云达不莱梅 推荐:多特蒙德 上半场 -0.5 德国杯 ⏰03:45 队伍:科隆 vs 柏林联合 推荐:柏林联合 +0.5 意甲 ⏰03:45 队伍:都灵 vs 科莫 推荐:科莫 -0.5/1 足球二串:拉齐奥 -0/0.5⚡️科莫 -0.5/1
2026.10.27 足球早盘推荐 亚冠精英18:00 柔佛VS狮子港 推荐:全场大3.5球 亚冠精英18:00 上海海港VS河内公安 推荐:全场大3球 亚冠精英20:15 北京国安VS全北现代 推荐:主队-0 爱沙甲00:00 塔林利VS潭美卡 推荐:全场大3.75球 波兰杯00:30 莫托路宾VS琴斯托霍瓦 推荐:全场大2.75球 德国杯01:00 汉堡VS法兰克福 推荐:客队-0.25 意甲01:30 萨索洛VS拉齐奥 推荐:全场大3球 荷兰杯03:00 克卢廷厄VS坎布尔 推荐:全场大3.75球 意甲03:45 罗马VS卡利亚里 推荐:全场大3球 英甲03:45 米尔顿凯恩斯VS布罗雷 推荐:全场大3球
2026.10.26 足球早盘推荐 阿美超23:00 阿拉特亚美尼亚VS诺亚 推荐:客队-0.75 亚冠精英00:00 吉达国民VS加拉法 推荐:全场大3球 保甲01:30 索菲亚中央陆军VS卢多戈雷茨 推荐:主队-0.25 丹麦超02:00 哥本哈根VS欧登塞 推荐:全场大3球 罗甲02:00 圣格奥尔VS克拉约瓦大学 推荐:全场大2.5球 亚冠精英02:15 巴格达空军VS帕克塔科 推荐:主队+0.5 土超02:30 加拉塔萨雷VS费内巴切 推荐:客队+0.5 法甲03:30 巴黎圣日耳曼 VS里昂 推荐:全场大3.5球 西甲04:00 塞维利亚VS奥萨苏纳 推荐:主队-0.5
老赵✨晚场足球精选10/25 英超 ⏰22:00 队伍:赫尔城 vs 布伦特福德 主任:012 让平/让负 欧盘:布伦特福德 -0.5/1 法甲 ⏰22:00 队伍:摩纳哥 vs 里尔 主任:017 胜 推荐:摩纳哥 -0.5 德甲 ⏰22:30 队伍:霍芬海姆 vs 勒沃库森 主任:018 负 推荐:勒沃库森 -0.5 西甲 ⏰23:15 队伍:塞尔塔 vs 皇家贝蒂斯 主任:019 2-3球 推荐:2-3球 法甲 ⏰00:15 队伍:雷恩 vs 斯特拉斯堡 主任:020 胜 推荐:雷恩 -0.5/1 德甲 ⏰00:30 队伍:弗赖堡 vs 拜仁慕尼黑 主任:022 让胜 推荐:弗赖堡 +1/1.5 重心:❤️❤️❤️❤️❤️ 足球二串:弗赖堡 +1/1.5⚡️雷恩 -0.5/1
老赵✨晚场足球精选10/24 英超 ⏰22:00 队伍:阿森纳 vs 埃弗顿 主任:016 2-3球 推荐:2-3球 比分:2-0 2-1 英超 ⏰22:00 队伍:考文垂 vs 富勒姆 主任:017 胜/平 推荐:考文垂 +0/0.5 比分:2-1 3-1 葡超 ⏰22;30 队伍:阿马多拉 vs 卡萨皮亚 主任:021 胜 推荐:阿马多拉 -0.5/1 比分:2-0 2-1 英超 ⏰00:30 队伍:切尔西 vs 热刺 主任:023 胜 推荐:切尔西 -0.5 比分:2-1 3-2 重心:❤️❤️❤️❤️❤️ 西甲 ⏰03:00 队伍:马德里竞技 vs 拉科鲁尼亚 主任:028 让负 推荐:拉科鲁尼亚 +1.5 比分:1-0 1-1 足球二串:切尔西 -0.5⚡️拉科鲁尼亚 +1.5
Showing the 12 most recent of 144 posts we hold for @ATYTD88. 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.
Forward network
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.
Mentions
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.
Cite this entry
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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“体育电竞赛事推单” (@ATYTD88), 23,979 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/ATYTD88.
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.