Telegram RegisterThe public register of Telegram
Telegram profile photo for 体育电竞赛事滚球红单推单

Channel

体育电竞赛事滚球红单推单

@OZBhongdan

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

10,313subscribers

-2,552 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001495499487
TypeChannel
Username@OZBhongdan
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/OZBhongdan

Topic

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 why it has no browse page of its own yet.

Observations

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.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. 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.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@apsp1234/135319 Jul 2026, 08:20 UTC@OZBhongdan/12072 · this entry19 Jul 2026, 09:28 UTC1.0068 minutes
@OZBhongdan/12073 · this entry19 Jul 2026, 10:37 UTC@apsp1234/135519 Jul 2026, 11:00 UTC1.0023 minutes
@OZBhongdan/12074 · this entry19 Jul 2026, 11:00 UTC@apsp1234/135619 Jul 2026, 12:34 UTC1.001.6 hours
@OZBhongdan/12076 · this entry19 Jul 2026, 14:12 UTC@apsp1234/135919 Jul 2026, 16:40 UTC1.002.5 hours
@OZBhongdan/12077 · this entry19 Jul 2026, 15:29 UTC@apsp1234/136019 Jul 2026, 17:05 UTC1.001.6 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@apsp12345 (5/5 hand-verifiable sample passed)1.001.6 hoursthis entry (41)

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. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 10 comparable posts for this entry, running 18 July 2026 to 31 July 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @apsp1234. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 8 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.

Growth

10,31312,86511,5897 August 2026 — 12,865 subscribers8 August 2026 — 12,848 subscribers8 August 2026 — 12,822 subscribers10 August 2026 — 12,757 subscribers11 August 2026 — 12,599 subscribers12 August 2026 — 12,573 subscribers13 August 2026 — 12,346 subscribers14 August 2026 — 12,170 subscribers16 August 2026 — 12,130 subscribers17 August 2026 — 12,052 subscribers18 August 2026 — 11,585 subscribers19 August 2026 — 11,319 subscribers20 August 2026 — 11,292 subscribers22 August 2026 — 11,278 subscribers23 August 2026 — 11,255 subscribers25 August 2026 — 11,241 subscribers26 August 2026 — 11,130 subscribers27 August 2026 — 11,129 subscribers27 August 2026 — 11,124 subscribers28 August 2026 — 11,104 subscribers29 August 2026 — 11,083 subscribers31 August 2026 — 11,061 subscribers1 September 2026 — 10,825 subscribers2 September 2026 — 10,593 subscribers3 September 2026 — 10,554 subscribers5 September 2026 — 10,546 subscribers9 September 2026 — 10,517 subscribers11 September 2026 — 10,454 subscribers13 September 2026 — 10,394 subscribers14 September 2026 — 10,371 subscribers16 September 2026 — 10,336 subscribers19 September 2026 — 10,313 subscribers7 August 202619 September 2026
32 measurements spanning 43 days, net -2,552. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 9,930–13,248 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
19 Sept 2026, 00:0110,313-23
16 Sept 2026, 16:5610,336-35
14 Sept 2026, 21:3910,371-23
13 Sept 2026, 10:2010,394-60
11 Sept 2026, 15:5910,454-63
9 Sept 2026, 03:4110,517-29
5 Sept 2026, 17:1710,546-8
3 Sept 2026, 14:1910,554-39
2 Sept 2026, 04:2510,593-232
1 Sept 2026, 05:2810,825-236
31 Aug 2026, 01:5411,061-22
29 Aug 2026, 22:3711,083-21
28 Aug 2026, 22:1411,104-20
27 Aug 2026, 23:0711,124-5
27 Aug 2026, 01:0611,129-1
26 Aug 2026, 04:1811,130-111
25 Aug 2026, 01:0811,241-14
23 Aug 2026, 13:2411,255-23
22 Aug 2026, 00:1411,278-14
20 Aug 2026, 18:4411,292first reading

Engagement

75 posts held, back to 18 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 43 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.203%
avg views ÷ 10,313 subscribers
Avg views / post
20.9
36 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
36
of 75 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 September 2026
Posts held75 (18 July 20261 September 2026)
Views total754
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Sept 2026, 20:10 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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.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 1 of the 75 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 75 most recent posts we hold, published 18 July 2026 to 1 September 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

1 Sept 2026, 15:41 UTC10 viewsread 1 September 2026

2026-09-02 01:30 奥地利甲组联赛 沃尔夫斯贝格 v 林茨 足球 让球 - 上半场 林茨 -0.5 2026-09-02 02:00 沙特超级联赛 希拉尔 v 阿尔艾利吉达 足球 让球 希拉尔 -1 2026-09-02 02:45 英格兰冠军联赛 斯旺西 v 沃特福德 足球 让球 斯旺西 -0.5 2026-09-02 02:45 英格兰冠军联赛 伯明翰 v 南安普敦 足球 让球 南安普敦 0 2026-09-02 02:45 英格兰冠军联赛 西汉姆联 v 狼队 足球 大 / 小 大 2.5 / 3

1 Sept 2026, 11:00 UTC20 viewsread 1 September 2026
Photo

英格兰职业联赛U21 哈德斯菲尔德U21 VS 女王公园巡 游者U21 09-01 20:00 (GMT+8) 全场让球 [欧洲盘] 哈德斯菲尔德U21 -0.5/1 @ 1.81 搞单开开胃 兄弟们!

31 Aug 2026, 11:59 UTC25 viewsread 1 September 2026

瑞典超级联赛 天狼星 v 马尔默 足球 让球 马尔默 +0.5 / 1 瑞典超级联赛 加尔斯 v 布洛马波卡纳 足球 大 / 小 大 2.5 / 3 土耳其超级联赛 阿美德 v 特拉布宗 足球 大 / 小 大 2.5 / 3 意大利甲组联赛 亚特兰大 v 博洛尼亚 足球 让球 亚特兰大 -0.5 土耳其超级联赛 贝西克塔斯 v 科鲁姆 足球 球队进球数: 贝西克塔斯 - 大 / 小 - 上半场 大 0.5 / 1 英格兰超级联赛 阿斯顿维拉 v 阿森纳 足球 让球 阿森纳 -1 葡萄牙超级联赛 布拉加 v 甘马雷斯 足球 让球 布拉加 -0.5 / 1 葡萄牙超级联赛 本菲卡 v 伊斯托里尔 足球 让球 - 上半场 本菲卡 -1 西班牙甲组联赛 巴塞罗那 v 巴列卡诺 足球 大 / 小 小 4 九串八

31 Aug 2026, 11:39 UTC27 viewsread 1 September 2026

---同路上车 跟反自由--- ---赛事无神 红黑勿怪--- 亚足联U20 20:00 队伍:新加坡 U20-不丹 U20 推荐:全场小(3) 亚足联U20 20:00 队伍:越南 U20-朝鲜 U20 推荐:全场大(2.5) 亚足联U20 20:00 队伍:也门 U20-柬埔寨 U20 推荐:全场大(3/3.5)

31 Aug 2026, 11:06 UTC24 viewsread 1 September 2026
Photo

亚足联冠军联赛二资格赛 万隆泊西布 VS 马尼拉迪格尔 08-31 20:00 (GMT+8) 全场大小 [欧洲盘] 小 3.5 @ 1.80 玩儿一下!

30 Aug 2026, 12:29 UTC27 viewsread 1 September 2026

英格兰超级联赛 切尔西 v 布莱顿 足球 让球 切尔西 -0.5 英格兰超级联赛 利兹联 v 布伦特福德 足球 让球 布伦特福德 0 英格兰超级联赛 桑德兰 v 富勒姆 足球 让球 桑德兰 -0 / 0.5 三串一

30 Aug 2026, 10:13 UTC26 viewsread 1 September 2026
Photo

荷兰甲级联赛 乌德勒支 VS PSV埃因霍温 08-30 18:15 (GMT+8) 总进球数区间 [欧洲盘] 4-6 @ 1.93 搞场荷甲玩儿一下

30 Aug 2026, 06:33 UTC27 viewsread 1 September 2026
Photo

澳大利亚昆士兰州国家超级联赛 - 附加赛 昆士兰狮队 VS 潘尼苏拉 08-30 15:00 (GMT+8) 全场让球 [欧洲盘] 昆士兰狮队 -0.5/1 @ 1.96 重注回血 剁屌担保!

29 Aug 2026, 12:43 UTC29 viewsread 1 September 2026
Photo

---同路上车 跟反自由--- ---赛事无神 红黑勿怪--- 德甲 21:30 队伍:艾禾斯堡-勒沃库森 推荐:艾禾斯堡(+1) 德甲 21:30 队伍:科隆-霍芬海姆 推荐:科隆(+0/0.5) 德甲 21:30 队伍:美因茨05-帕德博恩 推荐:美因茨05(-1) 德甲 21:30 队伍:RB莱比锡-门兴格拉德巴赫 推荐:RB莱比锡(-1) 德甲 21:30 队伍:柏林联-法兰克福 推荐:法兰克福 (0) 英超 22:00 队伍:考文垂-赫尔城 推荐:双进(是)

29 Aug 2026, 12:02 UTC24 viewsread 1 September 2026
Photo

---同路上车 跟反自由--- ---赛事无神 红黑勿怪--- 英超 19:30 队伍:利物浦-诺丁汉森林 推荐:诺丁汉森林(+1/1.5) 英冠 19:30 队伍:米德尔斯堡-西布朗 推荐:全场大(2.5/3) 英冠 19:30 队伍:狼队-斯托克城 推荐:斯托克城(+0.5/1) 英冠 19:30 队伍:德比郡-斯旺西 推荐:总进球(2/3球) 中超 19:30 队伍:成都蓉城-辽宁铁人 推荐:辽宁铁人(+1/1.5) 中超 20:00 队伍:河南-重庆铜梁龙 推荐:河南(-1.5)

29 Aug 2026, 08:23 UTC23 viewsread 1 September 2026

日本J1联赛 清水心跳 VS 柏太阳神 08-29 17:30 (GMT+8) 全场让球 [欧洲盘] 柏太阳神 -0.5 @ 1.90 日本J2联赛 大宫松鼠 VS 湘南海洋 08-29 18:00 (GMT+8) 全场让球 [欧洲盘] 湘南海洋 +0/0.5 @ 1.87 烤肉串走起!

28 Aug 2026, 14:18 UTC25 viewsread 1 September 2026

德国乙级联赛 布伦瑞克 VS 柏林赫塔 08-29 00:30 (GMT+8) 全场让球 [欧洲盘] 布伦瑞克 +0/0.5 @ 1.83 法国甲级联赛 里尔 VS 巴黎圣日耳曼 08-29 02:45 (GMT+8) 全场让球 [欧洲盘] 巴黎圣日耳曼 -1 @ 2.12 吃肉2串1 干! 剁屌担保!

Showing the 12 most recent of 75 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.

Mentions

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.

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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“体育电竞赛事滚球红单推单” (@OZBhongdan), 10,313 subscribers as measured 19 September 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.