Channel
@AiTuiDan
On this record: Growth · Engagement · Posts · Citations · Cite this entry
318subscribers
+7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003244635463 |
|---|---|
| Type | Channel |
| Username | @AiTuiDan |
| Created | Between 1 October 2025 and 31 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/AiTuiDan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 01:37 | 318 | +1 |
| 15 Aug 2026, 18:06 | 317 | +5 |
| 8 Aug 2026, 09:02 | 312 | +1 |
| 8 Aug 2026, 07:46 | 311 | no change |
| 7 Aug 2026, 18:26 | 311 | first reading |
20 posts held, back to 7 August 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (7 August 2026 – 8 August 2026) |
| Views total | 436 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 07:46 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.
#阿甲 08:45 门多萨独立 VS 里奥夸尔托学生队 让球盘推荐: 门多萨独立 (-1.0 @0.80) 理由: 主队在实力、状态、主场优势和战术对位上全面占优，且客队核心伤病严重。市场盘口也持续加强对主队赢球的信心，看好主队净胜一球及以上。 大小球推荐: 小球 (2.25 @0.88) 理由: 模型预测总进球数偏低，阿甲联赛整体进球效率不高。客队进攻乏力，主队在稳固领先时可能趋于保守，难以打出大比分。 提前获得分析报告: https://vextips.com/live
#阿甲 06:30 罗萨里奥中央 VS 阿尔多斯维 让球盘推荐: 罗沙里奧中央 (-0.5 @[赔率]) 理由: 基于基本面分析，罗沙里奧中央具备主场优势和整体实力优势，尽管平局概率不低，但面对客队门将缺阵的严重弱点，罗沙里奧中央获胜的倾向性更强。选择-0.5球让球，以确保在罗沙里奧中央净胜1球时获得全额回报。 大小球推荐: 小球 (2.0 @[赔率]) 理由: 模型和两队近期进攻效率量化数据均强烈指向低进球数。罗沙里奧中央的进攻乏力与艾度思维的整体弱势，使得比赛总进球数很难超过2球。 提前获得分析报告: https://vextips.com/live
#葡超 03:15 埃斯托里尔 VS 法马利康 让球盘推荐: 费马利卡奥 (0 @0.78) 理由: 费马利卡奥在整体实力、近期状态和历史交锋中均占优，盘口虽为平手盘但客队给出超低水，表明市场对其不败甚至取胜信心极高。 大小球推荐: 小球 (2.25 @1.08) 理由: 两队进攻效率均受限，费马利卡奥防守稳固，模型预期总进球2.3，且市场已将大小球盘口下调至2.25球并提高小球赔率，符合低比分判断。 提前获得分析报告: https://vextips.com/live
#英联杯 03:00 米德尔斯堡 VS 雷克瑟姆 让球盘推荐: 威斯汉姆 (+0.75 @0.97) 理由: 米德尔斯堡严重的伤病情况，尤其是进攻核心的缺失，将使其难以在主场打穿0.75的让球盘口。模型显示平局概率最高，客胜也有机会，威斯汉姆受让0.75球具有较高价值。 大小球推荐: 小球 (2.75 @0.83) 理由: 综合两队伤病、近期状态和模型预测，比赛预计总进球数将非常有限。米德尔斯堡进攻受阻，威斯汉姆客场保守，小球是符合数据和逻辑的最佳选择。 提前获得分析报告: https://vextips.com/live
#爱超 02:45 戈尔韦联 VS 德罗赫达联 让球盘推荐: 戈尔韦联 (-0.5 @1.07) 理由: 戈尔韦联主场作战，核心球员表现更佳，且历史交锋占优。德罗赫达联防线不整，客场战绩不佳。模型显示主胜概率接近五成，净胜一球的概率最大。 大小球推荐: 小球 (2.25 @1.04) 理由: 模型预期总进球2.2，市场即时盘口下调至2.25，倾向于低进球。两队近期进攻效率有限，尤其是德罗赫达联客场进球能力不足。 提前获得分析报告: https://vextips.com/live
#爱超 02:45 德利城 VS 斯莱戈流浪者 让球盘推荐: 德利城 (-1.5 @1.03) 理由: 德利城在基本面（球队实力、阵容完整度、近期主场状态、战术对位）上全面占据优势，模型预测主胜概率高达74.9%，且多个高概率比分都指向净胜2球及以上。市场盘口也从-1.25升至-1.5，与分析结果一致。 大小球推荐: 大球 (2.75 @1.00) 理由: 模型预测总进球2.77，略高于盘口线2.75。德利城主场进攻效率高，面对斯莱戈流浪孱弱的防线有望取得多个进球，即使客队进球不多，主队单方面进球也可能推动总进球数达到或超过盘口。 提前获得分析报告: https://vextips.com/live
#比甲 02:45 布鲁日 VS 科特赖克 让球盘推荐: 布鲁日 (-2.0 @0.92) 理由: 布鲁日实力明显占优，主场作战，预计净胜球数可达2球或以上。模型显示布鲁日赢2球及以上的概率约为54.8%，且市场对布鲁日信心较强，盘口走势支持其大胜。 大小球推荐: 小球 (3.5 @0.91) 理由: 模型预测总进球数3.3球，Under 3.5的概率为56.7%。虽然市场倾向大球，但模型更倾向于略微保守的总进球数。 提前获得分析报告: https://vextips.com/live
#英联杯 2026-08-08 02:45 狼队 VS 让球盘推荐: 狼队 (-1.5/2 @0.91) 理由: 狼队实力优势明显，预期净胜球为1.7球。盘口升至1.5/2球，且主队赔率下降，市场对狼队大胜信心增强。结合模型主胜概率82.5%，净胜2球及以上概率约为55%，让球盘推荐具有较高价值。 大小球推荐: 大球 (3 @0.91) 理由: 狼队进攻状态出色，场均预期进球超过2球。维尔港防守能力有限，难以保持零封。历史交锋大球率80%，且盘口3球并未高开，大球方向值得推荐。 提前获得分析报告: https://vextips.com/live
#英联杯 2026-08-08 02:45 韦康比流浪者 VS 让球盘推荐: 韦康比流浪者 (-0.25 @0.92) 理由: 主队主场优势明显，历史交锋主场占优，模型预测主胜概率42.8%高于客胜29.9%。盘口维持主让0.25球，主队水位适中，具备投资价值。 大小球推荐: 小球 (2.25 @1.00) 理由: 双方季前赛进攻端表现均不突出，杯赛首轮可能偏向保守。模型总进球期望值2.40球虽略高于盘口，但市场下调盘口信号明确，小球方向具备更高安全边际。 提前获得分析报告: https://vextips.com/live
#德乙 02:30 波鸿 VS 柏林赫塔 让球盘推荐: 柏林赫塔 (+0.25 @0.93) 理由: 修正后的模型显示波鸿的优势微弱，平局和客胜的概率较高。盘口市场对波鸿让0.25球给出了较高的主队赔率，结合波鸿关键球员伤缺，市场对其主场优势信心不足。柏林赫塔阵容完整，在客场具备抗衡能力，且受让0.25球时，打平即可全赢一半。 大小球推荐: 小球 (2.75 @0.97) 理由: 市场大小球盘口从3球降至2.75球，且大球赔率上升，明确指示市场对总进球数预期降低。结合波鸿的伤病影响以及新赛季首轮两队可能更为谨慎的策略，总进球数预计在2-3球之间，小2.75球更具价值。 提前获得分析报告: https://vextips.com/live
#波兰超 02:30 克拉科夫 VS 华沙普洛克 让球盘推荐: 华沙普洛克 (+0.75 @0.92) 理由: 模型预测主胜概率44.2%，平局和客胜合计55.8%，显示比赛结果比市场让球盘所暗示的更为接近。华沙普洛克在整体实力、防守稳定性及阵容完整度上均有优势，主队门将缺阵是重大隐患。在市场过度高估主队让球的情况下，客队受让+0.75盘口有较高价值。 大小球推荐: 小球 (2.5 @0.99) 理由: 模型预测总预期进球为2.00，远低于2.5球盘口。华沙普洛克防守稳健，克拉科夫虽然防线不稳但其进攻转化率也并非顶级，难以形成高比分。市场大小球盘口升至2.75，进一步凸显了小球的价值。 提前获得分析报告: https://vextips.com/live
#保甲 02:15 索非亚列夫斯基 VS 普罗夫迪夫火车头 让球盘推荐: 索菲亚利夫斯基 (-1.25 @0.90) 理由: 索菲亚利夫斯基在整体实力、竞技状态、主场优势及战术对位上均占据压倒性优势。尽管存在主力伤病和体能挑战，但普罗夫迪夫火车头客场攻防俱弱，难以阻挡主队取得一场净胜2球或以上的胜利。模型显示主胜概率极高，让球盘存在被市场低估的可能。 大小球推荐: 大球 (2.5 @0.88) 理由: 索菲亚利夫斯基强大的主场进攻是主要的进球保障，他们有能力打入2-3球。普罗夫迪夫火车头客场防守主力缺阵，难以有效抵挡。 提前获得分析报告: https://vextips.com/live
Showing the 12 most recent of 20 posts we hold for @AiTuiDan. 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.
Citation-graph rank — 1,028,932 of 1,627,068entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“AI足球⚡️ 实时推送” (@AiTuiDan), 318 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/AiTuiDan.
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.