欧洲国家联赛C 白俄罗斯 v 阿尔巴尼亚 足球 角球数 - 大 / 小 大 9 欧洲国家联赛C 芬兰 v 圣马力诺 足球 大 / 小 - 上半场 大 1.5 / 2 欧洲国家联赛A 比利时 v 意大利 足球 大 / 小 大 2.5 / 3 欧洲国家联赛A 法国 v 土耳其 足球 让球 土耳其 +2 / 2.5 欧洲国家联赛A 克罗地亚 v 捷克 足球 大 / 小 大 2.5 / 3 欧洲国家联赛A 西班牙 v 英格兰 足球 大 / 小 大 3
❤1

Channel
@OZBhongdan
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
9,908subscribers
-2,957 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001495499487 |
|---|---|
| Type | Channel |
| Username | @OZBhongdan |
| Description | 赛事早知道:提供欧冠、欧联、五大联赛、中超、NBA、CBA、FIBA、LOL、DOTA2等热门联赛的相关赛程及赛事分析,精彩集锦、新闻资讯等 https://t.me/BDZS888 |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 53 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/OZBhongdan |
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 10 August 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 12 other registered channels. This entry also sits inside a group of 50 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @SJBhongdan/121514 Aug 2026, 14:17 UTC | @OZBhongdan/12091 · this entry14 Aug 2026, 14:18 UTC | 1.00 | under a minute |
| @SJBhongdan/124622 Aug 2026, 10:53 UTC | @OZBhongdan/12108 · this entry22 Aug 2026, 10:53 UTC | 1.00 | under a minute |
| @SJBhongdan/126726 Aug 2026, 16:18 UTC | @OZBhongdan/12126 · this entry26 Aug 2026, 16:18 UTC | 1.00 | under a minute |
| @SJBhongdan/127227 Aug 2026, 15:43 UTC | @OZBhongdan/12129 · this entry27 Aug 2026, 15:43 UTC | 1.00 | under a minute |
| @SJBhongdan/128029 Aug 2026, 12:01 UTC | @OZBhongdan/12137 · this entry29 Aug 2026, 12:02 UTC | 1.00 | under a minute |
| @SJBhongdan/141731 Oct 2026, 13:04 UTC | @OZBhongdan/12271 · this entry31 Oct 2026, 13:04 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @SJBhongdan | 42 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @SJBhongdan (41–1) |
| @ybgf9 | 33 (8/8 hand-verifiable sample passed) | 1.00 | 6 minutes | @ybgf9 (22–11) |
| @tiyu_3 | 24 (8/8 hand-verifiable sample passed) | 1.00 | 16 minutes | @tiyu_3 (24–0) |
| @tiyuquan | 21 (8/8 hand-verifiable sample passed) | 1.00 | 16 minutes | @tiyuquan (21–0) |
| @jnty135 | 16 (8/8 hand-verifiable sample passed) | 1.00 | 27 minutes | this entry (11–5) |
| @tiyutuidan08 | 14 (8/8 hand-verifiable sample passed) | 1.00 | 16 minutes | @tiyutuidan08 (14–0) |
| @chimu888888 | 9 (8/8 hand-verifiable sample passed) | 1.00 | 29 minutes | this entry (8–1) |
| @cx164 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 80 minutes | this entry (4–2) |
| @SJB00001 | 6 (6/6 hand-verifiable sample passed) | 0.95 | 10 minutes | @SJB00001 (6–0) |
| @TiYu9812 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 5 minutes | @TiYu9812 (5–0) |
| @apsp1234 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 1.6 hours | this entry (4–1) |
| @CCTVXW66 | 5 (5/5 hand-verifiable sample passed) | 0.96 | 20 minutes | @CCTVXW66 (5–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 149 of the 150 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 64 comparable posts for this entry, running 18 July 2026 to 14 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 50 channels, the one whose matching posts we hold earliest is @J9yaya. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 15 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 50 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 10:08 | 9,908 | -9 |
| 7 Nov 2026, 15:15 | 9,917 | -24 |
| 4 Nov 2026, 05:57 | 9,941 | -18 |
| 31 Oct 2026, 23:20 | 9,959 | -26 |
| 28 Oct 2026, 23:59 | 9,985 | -14 |
| 25 Oct 2026, 19:58 | 9,999 | -12 |
| 24 Oct 2026, 22:37 | 10,011 | -3 |
| 23 Oct 2026, 22:17 | 10,014 | -5 |
| 23 Oct 2026, 00:57 | 10,019 | -5 |
| 21 Oct 2026, 22:37 | 10,024 | -3 |
| 20 Oct 2026, 18:11 | 10,027 | -4 |
| 19 Oct 2026, 17:20 | 10,031 | -10 |
| 18 Oct 2026, 14:18 | 10,041 | -5 |
| 17 Oct 2026, 17:10 | 10,046 | -7 |
| 16 Oct 2026, 20:07 | 10,053 | -26 |
| 15 Oct 2026, 18:35 | 10,079 | -12 |
| 14 Oct 2026, 17:20 | 10,091 | -14 |
| 13 Oct 2026, 04:41 | 10,105 | -24 |
| 8 Oct 2026, 20:19 | 10,129 | -62 |
| 4 Oct 2026, 10:00 | 10,191 | first reading |
118 posts held, back to 18 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 69 pages of 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 43 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 November 2026 |
|---|---|
| Posts held | 118 (18 July 2026 – 15 November 2026) |
| Views total | 1,343 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 00:07 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 16 November 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.
3 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 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 3 of the 118 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 118 most recent posts we hold, published 18 July 2026 to 15 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.
Telegram’s own ‘edited’ marker: 0 of 43 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
欧洲国家联赛C 白俄罗斯 v 阿尔巴尼亚 足球 角球数 - 大 / 小 大 9 欧洲国家联赛C 芬兰 v 圣马力诺 足球 大 / 小 - 上半场 大 1.5 / 2 欧洲国家联赛A 比利时 v 意大利 足球 大 / 小 大 2.5 / 3 欧洲国家联赛A 法国 v 土耳其 足球 让球 土耳其 +2 / 2.5 欧洲国家联赛A 克罗地亚 v 捷克 足球 大 / 小 大 2.5 / 3 欧洲国家联赛A 西班牙 v 英格兰 足球 大 / 小 大 3
❤1
欧洲国家联赛A 挪威 v 威尔士 足球 角球数 - 大 / 小 大 9 欧洲国家联赛A 葡萄牙 v 丹麦 足球 大 / 小 大 3 欧洲国家联赛B 瑞典 v 波斯尼亚和黑塞哥维那 足球 大 / 小 大 2.5 / 3 欧洲国家联赛B 罗马尼亚 v 波兰 足球 让球 波兰 -0.5 / 1 欧洲国家联赛B 奥地利 v 爱尔兰 足球 让球 奥地利 -0.5 / 1 欧洲国家联赛B 北爱尔兰 v 乌克兰 足球 球队进球数: 乌克兰 - 大 / 小 大 0.5 / 1 6*1
❤1
#LOL 2026 全球总决赛 - 淘汰赛 GEN 对战 BLG(BO5) 全局获胜:BLG 地图比分:2 - 3 地图让分:BLG+1.5 地图大小:大4.5
2026-11-13 22:00 国际友谊赛 科威特 v 叙利亚 足球 双方球队进球 是 2026-11-13 22:10 国际友谊赛 阿联酋 v 洪都拉斯 足球 双方球队进球 是 2026-11-13 22:30 国际友谊赛 沙特阿拉伯 v 韩国 足球 让球 韩国 -0.5 三串一
欧洲国家联赛B 苏格兰 v 北马其顿 足球 让球 苏格兰 -2 欧洲国家联赛B 斯洛文尼亚 v 瑞士 足球 让球 瑞士 -0.5 / 1 欧洲国家联赛C 斯洛伐克 v 法罗群岛 足球 球队进球数: 斯洛伐克 - 大 / 小 - 上半场 大 0.5 / 1 欧洲国家联赛C 保加利亚 v 冰岛 足球 让球 冰岛 -0.5 / 1 欧洲国家联赛A 荷兰 v 希腊 足球 让球 希腊 +1 欧洲国家联赛A 塞尔维亚 v 德国 足球 让球 德国 -1.5 / 2 非洲国家杯2027外围赛 摩洛哥 v 尼日尔 足球 让球 - 上半场 摩洛哥 -1 7串1 7串6
欧洲国家联赛A 土耳其 v 比利时 足球 球队进球数: 比利时 - 大 / 小 大 1.5 / 2 欧洲国家联赛A 捷克 v 西班牙 足球 角球数 - 让球 西班牙 -3.5 / 4 欧洲国家联赛A 意大利 v 法国 足球 大 / 小 大 2.5 / 3 欧洲国家联赛A 英格兰 v 克罗地亚 足球 角球数 - 让球 - 上半场 英格兰 -1.5 / 2 欧洲国家联赛C 阿尔巴尼亚 v 芬兰 足球 让球 阿尔巴尼亚 -0 / 0.5 欧洲国家联赛C 圣马力诺 v 白俄罗斯 足球 让球 白俄罗斯 -2 六串一 四串一 西班牙+意大利+英格兰+阿尔巴尼亚
2026-11-12 01:00 欧洲女子欧霸杯 费内巴切(女) v 皇家苏斯达(女) 足球 双方球队进球 是 2026-11-12 01:30 欧洲女子欧霸杯 法兰克福(女) v PSV(女) 足球 总进球数 2-3 2026-11-12 01:45 欧洲女子冠军联赛 奥哈瓦里(女) v 科治(女) 足球 让球 科治(女) -0.5 / 1 2026-11-12 02:00 欧洲女子欧霸杯 哈马比(女) v 迈加华斯巴达(女) 足球 让球 迈加华斯巴达(女) +3 2026-11-12 04:00 欧洲女子冠军联赛 尤文图斯(女) v 里昂(女) 足球 大 / 小 大 3.5 / 4 五串一 五串四
足球 让球 日本职业联赛杯 川崎前锋 v 柏雷素尔 川崎前锋 +0 / 0.5 足球 大 / 小 日本职业联赛杯 横滨水手 v 鹿岛鹿角 大 2.5 / 3 足球 让球 日本职业联赛杯 神户胜利船 v 町田泽维亚 町田泽维亚 +0 / 0.5 足球 角球数 - 大 / 小 日本职业联赛杯 浦和红钻 v 大阪樱花 大 9.5 4串1
为什么都不上车!!!
足球 让球 欧洲女子冠军联赛 皇家马德里(女) v 巴黎(女) 皇家马德里(女) -1 / 1.5 足球 让球 欧洲女子冠军联赛 赫根(女) v 切尔西(女) 赫根(女) +2 足球 让球 欧洲女子冠军联赛 巴黎圣日耳曼(女) v 拜仁慕尼黑(女) 拜仁慕尼黑(女) -0.5 / 1 足球 让球 - 上半场 欧洲女子冠军联赛 罗马(女) v 塞维特陈奥斯(女) 罗马(女) -0.5 / 1 欧洲女子冠军联赛 國際米蘭(女) v 曼城(女) 足球 球队进球数: 曼城(女) - 大 / 小 大 2 / 2.5 五串一 三串一 皇家马德里+赫根+罗马
2026-11-10 02:00 挪威超级联赛 克里斯恬桑德 v 瓦勒伦加 足球 球队进球数: 瓦勒伦加 - 大 / 小 大 1.5 / 2 2026-11-10 2:00 罗马尼亚甲组联赛 博托沙尼 v 加拉迪 足球 总进球数 2-3 2026-11-10 2:00 丹麦甲组联赛 哈维德夫 v 阿尔胡斯费马 足球 让球 哈维德夫 -0.5 2026-11-10 04:15 葡萄牙甲组联赛 图伦斯 v 利亚拿 足球 让球 图伦斯 -0.5
[足球] 波兰超级联赛 华沙莱吉亚 -0.5 @1.99 赛前全场让球[欧洲盘] 华沙莱吉亚 VS 琴斯托霍瓦 2026-11-09 00:30(GMT+8) [足球] 秘鲁甲级联赛 小 2.5 @1.91 赛前全场大小[欧洲盘] 洛斯香卡斯 VS 利马联盟 2026-11-09 02:00(GMT+8) [足球] 塞尔维亚超级联赛 小 3 @1.90 赛前全场大小[欧洲盘] 伏伊伏丁那 VS 贝尔格莱德红星 2026-11-09 02:00(GMT+8) [足球] 俄罗斯超级联赛 0-1 @2.56 赛前总进球数区间[欧洲盘] 加里宁格勒波罗的海 VS 戴拿模马卡马哈奇卡拉 2026-11-09 01:45(GMT+8) [足球] 西班牙甲级联赛 否 @1.86 赛前两队都进球[欧洲盘] 比利亚雷亚尔 VS 赫塔费 2026-11-09 01:30(GMT+8) [足球] 西班牙甲级联赛 小 2.5 @2.00 赛前全场大小[…
Showing the 12 most recent of 118 posts we hold for @OZBhongdan. 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.
We recorded 2 posts on @OZBhongdan as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“体育电竞赛事滚球红单推单” (@OZBhongdan), 9,908 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/OZBhongdan.
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.