Channel
@OB200000
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
1,326subscribers
+6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001205959241 |
|---|---|
| Type | Channel |
| Username | @OB200000 |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/OB200000 |
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 11 August 2026 and assigned it the closest of 31 fixed categories, at 85% 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.
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 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @sjb0101/85718 Jul 2026, 06:04 UTC | @OB200000/4323 · this entry18 Jul 2026, 06:04 UTC | 0.97 | under a minute |
| @OB200000/4321 · this entry17 Jul 2026, 06:05 UTC | @sjb0101/85517 Jul 2026, 06:05 UTC | 0.96 | under a minute |
| @sjb0101/85311 Jul 2026, 06:03 UTC | @OB200000/4319 · this entry11 Jul 2026, 06:03 UTC | 0.96 | under a minute |
| @sjb0101/86529 Jul 2026, 07:26 UTC | @OB200000/4331 · this entry29 Jul 2026, 07:26 UTC | 0.96 | under a minute |
| @sjb0101/86122 Jul 2026, 08:54 UTC | @OB200000/4327 · this entry22 Jul 2026, 08:54 UTC | 0.86 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @sjb0101 | 5 (5/5 hand-verifiable sample passed) | 0.94 | under a minute | @sjb0101 (4–1) |
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 4 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 11 July 2026 to 4 August 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.
Across the whole group of 2, the earliest publisher we hold is @sjb0101. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 7 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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 16:53 | 1,326 | +8 |
| 6 Aug 2026, 11:30 | 1,318 | -2 |
| 6 Aug 2026, 08:04 | 1,320 | no change |
| 6 Aug 2026, 03:46 | 1,320 | first reading |
10 posts held, back to 11 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 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. It is computed over the 5 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 10 (11 July 2026 – 4 August 2026) |
| Views total | 3,688 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 08:04 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.
⚽️8月5日足球赛事精选⚽️ 【欧冠资 00:00】米亚尔比 vs 布拉迪斯拉发🔥🔥 米亚尔比主场阵形严密中前场衔接流畅！ 👉盘口推荐：米亚尔比-0.5@2.03 【欧冠资 01:30】索菲亚列夫斯基 vs 海拉提🔥🔥 海拉提后防收缩果断防守反击犀利韧性十足！ 👉盘口推荐：海拉提+0.5/1@1.99 【欧冠资 02:00】圣吉罗斯 vs 博多格林特🔥🔥 博多格林特客场高位压制掌控比赛节奏！ 👉盘口推荐：博多格林特+0/0.5@1.98 【欧联资 03:00】拉恩 vs 伊比利亚1999🔥🔥 拉恩坐镇主场战意高涨中后场防守稳扎稳打！ 👉盘口推荐：拉恩+0/0.5@1.83 【哥伦甲 09:20】百万富翁 vs 帕斯托体育🔥🔥 百万富翁主场气势如虹火力全开攻势犀利！ 👉盘口推荐：百万富翁-1@2.00 【俄罗斯杯 23:30】莫斯科斯巴达 vs 奥伦堡🔥🔥 莫斯科斯巴达主场统治力强锋线多点开花！ 👉盘口推荐：莫斯科斯巴…
俄甲 22:00 乌法 平/半 卡马斯 推荐:乌法-0/0.5 罗甲 23:30 克卢日大学 半球 博托沙尼 推荐:克卢日大学-0.5 芬超 00:00 塞伊奈约基 受平/半 赫尔辛基 推荐:赫尔辛基-0/0.5 匈甲 00:30 萨拉格斯基 受平/半 保克什 推荐:保克什-0/0.5 瑞典超 01:00 尤尔加登 一/球半 瓦斯特拉斯 推荐:尤尔加登-1/1.5 瑞典超 01:00 哈尔姆斯塔德 受一/球半 天狼星 推荐:天狼星 -1/1.5 挪甲 01:00 兰黑姆 受平/半 海于格松 推荐:海于格松-0/0.5 丹麦超 01:00 欧登塞 半球 桑德捷斯基 推荐:欧登塞-0.5 波兰超 01:00 克拉科维亚 平/半 什切…
中超 19:35 河南队 半球 大连英博 推荐:大连英博+0.5 罗甲 23:30 阿格斯 半/一 FK米耶尔库雷亚丘克 推荐:阿格斯 -0.5/1 芬甲 23:30 EIF埃克纳斯 平/半 克鲁比04 推荐:EIF埃克纳斯-0/0.5 芬甲 23:30 科特卡 球半 SJK学院 推荐:科特卡-1.5 芬甲 00:00 PK-35海辛基 平手 哈卡 推荐:PK-35海辛基+0 丹麦甲 00:00 奧胡斯费马 平/半 奧尔堡 推荐:奧胡斯费马-0/0.5 波兰超 00:00 华沙普洛克 受平/半 维德祖罗兹 推荐:维德祖罗兹-0/0.5 俄超 01:00 罗迪纳莫斯科 受平/半 罗斯托夫 推荐:罗斯托夫-0/0.5 挪超 01:00 …
欧协联 22:30 杜卡吉尼 受一球 卢加诺 推荐：卢加诺 -1 欧冠杯 23:00 阿拉木图凯拉特 平／半 奥莫尼亚 推荐：阿拉木图凯拉特 -0/0.5 芬甲 23:30 MP米克力 平／半 卡亚尼卡帕 推荐：MP米克力 -0/0.5 欧冠杯 00:00 考诺萨基列斯 半／一 克拉克斯维克 推荐：考诺萨基列斯 -0.5/1 欧冠杯 01:00 波兹南莱赫 半／一 奥胡斯 推荐：波兹南莱赫 -0.5/1 欧协联 01:00 哥本哈根 半／一 普莱西亚 推荐：哥本哈根 -0.5/1 欧冠杯 01:30 贝尔谢巴夏普尔 半／一 维京古尔 推荐：贝尔谢巴夏普尔 -0.5/1 欧冠杯 01:30 克拉约瓦大学 半球 索非亚列夫斯基 推荐：克拉约瓦大学 -0.5 阿甲 01:30 巴拉卡斯中央队 平／半 阿尔多斯维 推荐：巴拉卡斯中央队 -0/0.5 欧冠杯 02:00 扎布热矿工 受一球 费内巴切 推荐：费内巴切 -1…
韩K联 18:30 FC安养 受平/半 江原FC 推荐:江原FC-0/0.5 韩K联 18:30 光州FC 受半球 济州SK 推荐:济州SK-0.5 韩K联 18:30 仁川联队 半/一 富川FC 推荐:仁川联队-0.5/1 韩K联 18:30 FC首尔 半球 蔚山HD 推荐:FC首尔-0.5 韩K2联 18:30 金浦市民 半球 龙仁FC 推荐:金浦市民-0.5 韩K2联 18:30 坡州市民 半球 安山小绿人 推荐:坡州市民-0.5 中超 19:00 云南玉昆 半/一 深圳新鹏城 推荐:云南玉昆-0.5/1 瑞典甲 19:00 松兹瓦尔 受平/半 法尔肯堡 推荐:法尔肯堡-0/0.5 俄超 19:30 奥伦堡加索维克 平手 罗斯托夫 …
首存彩金日存彩金！电子流水彩金！体育流水彩金！百家乐流水彩金！签到彩金！应有尽有 欧冠杯 02:00 队伍：图恩-萨格勒布迪纳摩 推荐：全场大（3） 欧冠杯 02:00 队伍：费内巴切-扎布热矿工 推荐：全场大（3.5） 欧冠杯 02:30 队伍：格拉茨风暴-哈茨 推荐：全场大（2.5/3） 欧冠杯 02:45 队伍：克拉克斯维克-考诺萨基列斯 推荐：考诺萨基列斯（+0/0.5） 欧冠杯 03:00 队伍：维京古-贝尔谢巴工人 推荐：全场大（3） 欧冠杯 03:00 队伍：拉恩-贝尔格莱德红星 推荐：贝尔格莱德红星（-2）
韩K联 18:30 FC安养 一球 光州FC 推荐:FC安养-1 韩K联 18:30 富川FC 受半/一 FC首尔 推荐:FC首尔 -0.5/1 韩K2联 18:30 忠北清州 平手 天安城 推荐:忠北清州+0 韩K2联 18:30 庆南FC 半/一 安山小绿人 推荐:庆南FC-0.5/1 韩K2联 18:30 水原三星 一/球半 坡州市民 推荐:水原三星-1/1.5 韩K2联 18:30 龙仁FC 受平/半 华城FC 推荐:华城FC-0/0.5 瑞典甲 19:00 北雪平 一球 桑德维根斯 推荐:北雪平-1 瑞典甲 21:00 北欧联FC 半/一 臭雷布洛 推荐:北欧联FC-0.5/1 瑞典甲 21:00 韦纳穆 平手 卢恩斯基尔…
韩K联 18:30 大田市民 平/半 蔚山HD 推荐:蔚山HD +0/0.5 韩K联 18:30 江原FC 半球 金泉尚武 推荐:江原FC -0.5 韩K联 18:30 仁川联队 受平/半 全北现代 推荐:全北现代-0/0.5 韩K联 18:30 济州SK 平手 浦项制铁 推荐:浦项制铁+0 韩K2联 18:30 金浦市民 受平/半 大邱FC 推荐:大邱FC-0/0.5 韩K2联 18:30 全南天龙 平手 忠南牙山 推荐:全南天龙+0 韩K2联 18:30 城南FC 平手 釜山偶像 推荐:釜山偶像+0 韩K2联 18:30 水原FC 受平/半 首尔衣恋 推荐:水原FC-0/0.5 中超 19:00 重庆铜梁龙 …
中超 19:00 青岛西海岸 受半/一 成都蓉城 推荐:成都蓉城-0.5/1 中超 19:35 河南队 一球 青岛海牛 推荐:青岛海牛+1 中超 19:35 北京国安 一-/球半 辽宁铁人 推荐:辽宁铁人+1/1.5 中超 20:00 云南玉昆 平手 上海海港 推荐:云南玉昆+0 罗甲 23:30 沃伦塔利 平手 博托沙尼 推荐:博托沙尼+0 芬甲 00:00 卡亚尼卡帕 平/半 SJK学院 推荐:卡亚尼卡帕-0/0.5 芬甲 00:00 克鲁比04 受一球 哈卡 推荐:哈卡-1 保甲 00:00 华纳斯巴达 受半/一 索非亚1948中央陆军 推荐:索非亚1948中央陆军-0.5/1 瑞典超 01:00 哥德堡 半球…
韩K联 18:30 金泉尚武 半球 富川FC 推荐:富川FC +0.5 韩K联 18:30 光州FC 受一球 浦项制铁 推荐:浦项制铁-1 韩K联 18:30 蔚山HD 平手 全北现代 推荐:蔚山HD +0 韩K2联 18:30 安山小绿人 受一/球半 水原三星 推荐:水原三星-1/1.5 韩K2联 18:30 大邱FC 半球 城南FC 推荐:大邱FC-0.5 韩K2联 18:30 华城FC 半球 坡州市民 推荐:华城FC-0.5 韩K2联 18:30 龙仁FC 平/半 忠北清州 推荐:龙仁FC-0/0.5 中超 19:00 武汉三镇 受平/半 河南队 推荐:河南队-0/0.5 中超 19:00 浙江俱乐部绿城 …
Showing the 10 most recent of 10 posts we hold for @OB200000. 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 — 125,650 of 1,151,006entries 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 22 registered channels — 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“182体育 足球推单 🫥 足球比赛 体育电竞” (@OB200000), 1,326 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/OB200000.
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.