Channel
@ybtytd
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
108,229subscribers
-289 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001718222921 |
|---|---|
| Type | Channel |
| Username | @ybtytd |
| Description | 体育赛事推单 |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/ybtytd |
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 14 August 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 |
|---|---|---|
| 15 Aug 2026, 05:17 | 108,229 | -289 |
| 14 Aug 2026, 13:30 | 108,518 | no change |
| 14 Aug 2026, 13:18 | 108,518 | first reading |
31 posts held, back to 13 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 3 pagesof 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. It is computed over the 2 of 31 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 August 2026 |
|---|---|
| Posts held | 31 (13 August 2026 – 15 August 2026) |
| Views total | 86,364 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 13:43 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.
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 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 2 of the 31 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 13 August 2026 to 15 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.
0⃣【开云-8月15日 1点整 丹麦超 维堡 vs 奥胡斯】 0⃣【开云-8月15日 2点整 沙特超 利雅得希拉尔 vs 费萨里哈曼】 0⃣【开云-8月15日 2点30分 西乙 皇家社会B队 vs 卡斯特利翁】 0⃣【开云-8月15日 3点整 英冠 狼队 vs 布莱克本】 0⃣【开云-8月15日 15点整 LPL 深圳NIP vs 苏州LNG】 0⃣【开云-8月15日 17点整 LPL TT vs AL】 0⃣【开云-8月15日 18点整 日职J1联 千叶市原 vs 町田泽维亚】 0⃣【开云-8月15日 19点整 LPL BLG vs 西安WE】 0⃣【开云-8月15日 19点35分 中超 浙江队 vs 成都蓉城】 0⃣【开云-8月15日 19点35分 中超 天津津门虎 vs 北京国安】 0⃣【开云-8月16日 1点30分 西甲 阿拉维斯 vs 赫塔费】 0⃣【开云-8月16日 3点30分 西甲 塞维利亚 vs 巴列卡诺】 0⃣…
0⃣【开云-8月17日 10点30分 美职联 西雅图海湾人 vs 温哥华白帽】 数据方面机构向客队方向倾斜，盘口开出客队让0.5球。两队近期整体表现均不甚理想，状态存在一定起伏，比赛走势较难预料。西雅图海湾人虽然拥有主场优势，但近期攻防两端发挥欠缺稳定性，难以形成持续压制。反观温哥华白帽同样面临一定压力，不过球队整体实力并不逊色，且具备较强的反击能力。综合来看，本场看好温哥华白帽触底反弹，客场成功止颓。 全场让球：温哥华白帽[email protected] 全场大小：小[email protected] 推荐比分：0-2
0⃣【开云-8月17日 6点整 美职联 纽约城 vs 费城联合】 数据方面机构对于主队实力给予一定支持，盘口开出主队让0/0.5球。纽约城主场作战优势较为明显，球队在熟悉的场地更具主动权，攻防发挥也相对稳定。反观费城联合近期状态低迷，异地作战能力欠佳，已经连续5场比赛惨遭败绩，防守端问题尤其突出，期间场均失球高达3粒，后防线漏洞较多。面对主队的进攻冲击，客队恐怕难以招架。综合来看，本场看好纽约城凭借主场优势取胜。 全场让球：纽约城-0/[email protected] 全场大小：大2.5/[email protected] 推荐比分：2-1
0⃣【开云-8月17日 6点30分 巴甲 科林蒂安 vs 克鲁塞罗MG】 数据初盘开出主队-0/0.5，对坐镇主场的科林蒂安给予了微弱的倾斜支持。科林蒂安近期状态相当稳健，近10场比赛斩获4胜4平2负，近期各项赛事已连续三场不败且攻防两端运转流畅，主场借阵型压制往往能占据场上主动。反观克鲁塞罗MG近期战绩同样出色，近10场比赛取得5胜3平2负，目前积分榜暂列第5位，整体攻防落位秩序感极强，反击效率亦十分犀利。在积分榜层面，两队目前仅有1分之差，此战双方战意十足。但科林蒂安坐拥主场之利且近期防线韧性十足，状态较为火热。综合分析，本场看好科林蒂安主场取胜。 全场让球：科林蒂安-0/[email protected] 全场大小：大2/[email protected] 推荐比分：2-1
0⃣【开云-8月17日 5点30分 巴甲 维多利亚BA vs 博塔弗戈RJ】 数据初盘开出主队-0/0.5，说明机构对维多利亚BA实力的认可。维多利亚BA近期状态大起大落，近10场比赛取得4胜1平5负，虽然主场偶尔能爆发出较强的战术韧性，但防线落位频频失误，面对阵地战推进能力强的对手时显得抗压不足。反观博塔弗戈RJ近期表现相对平稳，近10场比赛斩获5胜3平2负，战术执行力与攻防两端的层次感保持得较为顺畅。值得注意的是，两队在今年7月24日的联赛首回合较量中战成0-0平局，彼此阵型对位与爆破点均有了解。但博塔弗戈RJ整体底蕴更深、反击能力更强。综合分析本场更看好博塔弗戈RJ客场小胜。 全场让球：博塔弗戈RJ+0/[email protected] 全场大小：小[email protected] 推荐比分：0-1
0⃣【开云-8月17日 5点30分 巴甲 迈拉索尔SP vs 弗拉门戈】 数据初盘开出客队-0.5，给予了联赛次席的弗拉门戈相当充沛的战力倾斜。迈拉索尔SP近期走势趋于胶着，近10场比赛取得3胜3平4负，虽然主场依靠扎实的阵型落位能保持一定抗压能力，但阵地攻坚与反击穿透力依然偏弱，面对争冠梯队时破局手段不足。反观弗拉门戈整体战力极其顽强，近10场比赛斩获6胜4平保持不败，阵型落位协同与前场多点开花的爆破力兼备，作客依然具备极强的比赛掌控力。且硬实力与阵容深度上占据绝对优势。综合分析，本场看好弗拉门戈客场掌控主动、顺利拿下胜利。 全场让球：弗拉门戈[email protected] 全场大小：大2/[email protected] 推荐比分：1-2
0⃣【开云-8月17日 3点15分 意杯 拉齐奥 vs 曼托瓦】 数据初盘开出全场让球：拉齐奥-1.5，机构倾向主队优势。意大利杯第1轮，主队近期友谊赛四战全胜，球队攻防有序，传控能力强，状态超燃，气势如虹。客队最近一场友谊赛0-1不敌卡尔皮，球队攻击力下降明显，状态有所下滑。两队最近一场交锋拉齐奥4-0大胜曼托瓦，整体实力相对更强，另加主场之利，综合分析本场看好主队轻松取胜。 全场让球：拉齐奥[email protected] 全场大小：大2.5/[email protected] 推荐比分：3-1
0⃣【开云-8月17日 2点45分 意杯 维罗纳 vs 维尔图斯恩泰拉】 数据方面机构开出主队让0.5/1，给予实力的认可。维罗纳与维尔图斯恩泰拉历史交锋中，维罗纳近3次面对对手保持全胜，心理优势较为明显。近期状态方面，维罗纳近10场取得4胜3平3负，整体表现较为稳定，球队在攻防两端具备一定竞争力。维尔图斯恩泰拉近10场取得4胜2平4负，发挥中规中矩，但面对意甲级别球队时，整体实力和比赛经验仍存在一定差距。 本场意大利杯维罗纳坐镇主场，凭借更高联赛级别、阵容深度以及交锋优势，有望掌控比赛节奏。综合分析，本场更看好维罗纳主场取胜。 全场让球：维罗纳-0.5/[email protected] 全场大小：小[email protected] 推荐比分：2-0
0⃣【开云-8月17日 2点45分 法超杯 朗斯 vs 巴黎圣日耳曼】 （本场赛事红包雨🧧敬请周知！） 数据初盘开出全场让球：朗斯+0.5/1，机构倾向客队优势。法国超级杯，主队最近一场友谊赛0-2不敌桑德兰，前场把握进球能力有所下降，表现欠佳，状态回落。客队最近一场欧超杯2-1击败阿斯顿维拉夺冠，球队攻防兼备，韧性十足，实力毋庸置疑。两队近八场交锋巴黎圣日耳曼7胜1平保持不败战绩，近年实力相对更强，近期整体发挥也更为出色，综合分析本场看好巴黎圣日耳曼夺冠。 全场让球：巴黎圣日耳曼-0.5/[email protected] 全场大小：小2.5/[email protected] 推荐比分：0-1
0⃣【开云-8月17日 1点整 西甲 西班牙人 vs 莱万特】 （本场赛事红包雨🧧敬请周知！） 数据方面机构开出主队让0.5，给予实力的认可。西班牙人与莱万特历史交锋中，西班牙人近10场取得5胜4平1负，心理优势较为明显，双方交手多数情况下比赛较为胶着。近期状态方面，西班牙人近10场取得4胜4平2负，整体表现稳定，攻防两端保持不错的平衡；莱万特近10场取得7胜3负，近期取胜能力较强，但客场面对西班牙人时往往难以占据明显优势。结合双方往绩、近期走势以及主场因素来看，西班牙人具备更强的拿分机会。综合分析，本场更看好西班牙人主场取胜。 全场让球：西班牙人[email protected] 全场大小：小2/[email protected] 推荐比分：1-0
0⃣【开云-8月17日 0点整 意杯 弗罗西诺内 vs 尤维斯塔比亚】 数据初盘开出全场让球：弗罗西诺内-0.5/1，机构倾向主队优势。意大利杯第1轮，主队近五场友谊赛2胜2平1负，球队防守较为稳固，整体表现相对稳定。客队最近一场友谊赛0-2不敌坎伯巴索，球队攻击力有所下降，表现欠佳，状态回落。两队近六场交锋弗罗西诺内3胜3平保持不败，整体实力更胜一筹，另加主场优势，综合分析本场看好主队获胜晋级。 全场让球：弗罗西诺内-0.5/[email protected] 全场大小：大[email protected] 推荐比分：3-0
0⃣【开云-8月14日 0点15分 沙特超 艾卜哈 vs 哈森姆】 0⃣【开云-8月14日 2点整 沙特超 德拉伊耶 vs 吉达国民】 0⃣【开云-8月14日 2点整 沙特超 利雅得沙巴布 vs 胡拜尔库迪西亚】 0⃣【开云-8月14日 2点45分 欧联资 哈茨 vs 本菲卡】 0⃣【开云-8月14日 3点整 欧联资 伊格纳迪亚 vs 沙姆洛克流浪】 0⃣【开云-8月14日 15点整 LPL EDG vs LGD】 0⃣【开云-8月14日 17点整 LPL 西安WE vs TES】 0⃣【开云-8月14日 19点35分 中超 武汉三镇 vs 上海海港】 0⃣【开云-8月14日 19点35分 中超 山东泰山 vs 青岛海牛】 0⃣【开云-8月15日 1点整 丹麦超 维堡 vs 奥胡斯】 0⃣【开云-8月15日 2点整 沙特超 利雅得希拉尔 vs 费萨里哈曼】 0⃣【开云-8月15日 2点30分 西乙 皇家社会B队 vs 卡斯特利翁…
Showing the 12 most recent of 31 posts we hold for @ybtytd. 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 — 340,447 of 1,480,688entries 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.
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 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.
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.
Telegram’s own answer, not this register’s.When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 14 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 4 seed channels' Telegram-generated recommendation lists 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“推单体育赛事推荐足球篮球推单” (@ybtytd), 108,229 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/ybtytd.
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.