Telegram RegisterThe public register of Telegram
Telegram profile photo for ☁️开云体育官网🏆体育推单欧洲杯

Channel

☁️开云体育官网🏆体育推单欧洲杯

@ybergou

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

10,496subscribers

-122 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001625568424
TypeChannel
Username@ybergou
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live9 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/ybergou

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 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.

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 3 other registered channels. They sit inside a group of 5 channels that share the same post bodies 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ybergou/17976 · this entry1 Aug 2026, 06:37 UTC@J9yaya/4641 Aug 2026, 06:52 UTC1.0016 minutes
@ybergou/17981 · this entry2 Aug 2026, 05:33 UTC@J9yaya/4652 Aug 2026, 08:54 UTC1.003.4 hours
@ybergou/17984 · this entry3 Aug 2026, 05:19 UTC@J9yaya/4663 Aug 2026, 05:43 UTC1.0025 minutes
@ybergou/17986 · this entry4 Aug 2026, 07:20 UTC@J9yaya/4674 Aug 2026, 07:49 UTC1.0029 minutes
@ybergou/17991 · this entry5 Aug 2026, 06:29 UTC@J9yaya/4685 Aug 2026, 06:30 UTC1.00under a minute
@ybergou/17993 · this entry7 Aug 2026, 06:59 UTC@J9yaya/4697 Aug 2026, 06:59 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@J9yaya7 (7/7 hand-verifiable sample passed)1.0025 minutesthis entry (70)
@kaiyun5 (5/5 hand-verifiable sample passed)1.002.1 hoursthis entry (50)
@titankuaibao5 (5/5 hand-verifiable sample passed)1.001.6 hours@titankuaibao (50)

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 5 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 14 comparable posts for this entry, running 30 July 2026 to 7 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.

  • 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 5, the earliest publisher we hold is @J9yaya. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_source, 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 4 other registered channels, 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,49610,61810,5576 August 2026 — 10,618 subscribers7 August 2026 — 10,612 subscribers8 August 2026 — 10,609 subscribers9 August 2026 — 10,598 subscribers10 August 2026 — 10,588 subscribers11 August 2026 — 10,590 subscribers12 August 2026 — 10,579 subscribers13 August 2026 — 10,571 subscribers14 August 2026 — 10,567 subscribers16 August 2026 — 10,566 subscribers17 August 2026 — 10,561 subscribers18 August 2026 — 10,554 subscribers19 August 2026 — 10,552 subscribers20 August 2026 — 10,549 subscribers21 August 2026 — 10,547 subscribers23 August 2026 — 10,548 subscribers25 August 2026 — 10,541 subscribers26 August 2026 — 10,535 subscribers27 August 2026 — 10,533 subscribers28 August 2026 — 10,532 subscribers30 August 2026 — 10,524 subscribers31 August 2026 — 10,521 subscribers1 September 2026 — 10,516 subscribers2 September 2026 — 10,522 subscribers3 September 2026 — 10,518 subscribers5 September 2026 — 10,506 subscribers9 September 2026 — 10,496 subscribers6 August 20269 September 2026
27 measurements spanning 33 days, net -122. 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 10,478–10,636 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
9 Sept 2026, 05:5510,496-10
5 Sept 2026, 21:5710,506-12
3 Sept 2026, 22:2110,518-4
2 Sept 2026, 13:4210,522+6
1 Sept 2026, 12:5410,516-5
31 Aug 2026, 11:0610,521-3
30 Aug 2026, 12:1410,524-8
28 Aug 2026, 08:5610,532-1
27 Aug 2026, 06:0810,533-2
26 Aug 2026, 04:1110,535-6
25 Aug 2026, 01:0810,541-7
23 Aug 2026, 14:0610,548+1
21 Aug 2026, 22:2810,547-2
20 Aug 2026, 20:1210,549-3
19 Aug 2026, 17:0310,552-2
18 Aug 2026, 18:0810,554-7
17 Aug 2026, 19:4610,561-5
16 Aug 2026, 17:3310,566-1
14 Aug 2026, 23:2210,567-4
13 Aug 2026, 18:0610,571first reading

Engagement

70 posts held, back to 30 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 38 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.65%
avg views ÷ 10,496 subscribers
Avg views / post
278
38 posts measured
Reaction rate
0.545%
reactions ÷ views · ER floor
Posts in window
38
of 70 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. It is computed over the 10 of 38 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 August 2026
Posts held70 (30 July 202629 August 2026)
Views total10,556
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 13:24 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

23 reactions across 15 posts, in 3 distinct kinds. The most used accounts for 87.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2087.0%
🏆28.70%
🍾14.35%

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 19 of the 70 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 23 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 70 most recent posts we hold, published 30 July 2026 to 29 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.

Recent posts

29 Aug 2026, 06:57 UTC133 views1 reactionsread 29 August 2026

中超17:00 青岛海牛 平手 武汉三镇 推荐:青岛海牛+0 日职联 17:00 大阪钢巴 受半/一 广岛三箭 推荐:广岛三箭 ﹣0.5/1 日职联 17:00 水户蜀葵 受半球 町田泽维亚 推荐:町田泽维亚 ﹣0.5 日职联 17:30 清水鼓动 受平/半 柏太阳神 推荐:柏太阳神 ﹣0/0.5 日职联 17:30 长崎成功丸 受半/一 FC东京 推荐:FC东京 ﹣0.5/1 日职联 18:00 川崎前锋 一球 千叶市原 推荐:川崎前锋 ﹣1 日职联18:00 京都不死鸟 平手 福冈黄蜂 推荐:京都不死鸟 ﹣0 日职联 18:00 名古屋鲸八 平手 冈山绿雉 推荐:名古屋鲸八 -0 日职联 18:00 浦和红钻 平/半 横滨水手 推荐:浦和红钻 ﹣0/0.5 日职联 18:00 东京绿茵 受半/一 鹿岛鹿角 推荐:鹿岛鹿角 ﹣0.5/1 日职联 18:00 神户胜利船 半球 大阪樱花 推荐:神户胜利船 ﹣0

1

29 Aug 2026, 05:16 UTC148 viewsread 29 August 2026
Photo

开云大哥 获得218彩金 恭喜恭喜 电子爆爆爆 爆奖的记得找我申请哦。冲冲冲!!!! 温馨提示 :买的免费转的,则无法领取这个活动的彩金!!!

28 Aug 2026, 15:01 UTC186 viewsread 29 August 2026
Photo

开云体育注册送138!世界杯赞助商官网~ 米兰/乐鱼/爱体育/YY体育/九游/mk/华体会/爱游戏 享受一百送一百活动! 👇👇彩金申请👇👇 @kaiyundog @ergou2000 👇👇注册网址👇👇 MK体育官网:http://mktyvip80.com MK TG投注机器人:https://t.me/MK888bot?start=24921304_B ————————————————— 开云官网: kaiyun.io 防劫持网址: http://yun674.vip 防劫持网址:http://yun675.vip 备用网址: http://yun676.vip ————————————————— YY体育官网:http://yy38vip.com 防劫持网址:http://yyty39.com 防劫持网址:http://yyvip21.net ————————————————— 米兰体育官网: https://mi

28 Aug 2026, 07:15 UTC191 viewsread 29 August 2026

韩K2联 18:30 安山小绿人 受一/球半 大邱FC 推荐:大邱 ﹣1/1.5 韩K2联 18:30 全南天龙 平/半 天安城 推荐:全南天龙 ﹣0/0.5 中超 19:35 大连英博 受平/半 北京国安 推荐:北京国安 ﹣0/0.5 中超 19:35 上海申花 半球 山东泰山 推荐:上海申花 ﹣0.5 中超20:00 深圳新鹏城 受半球 上海海港 推荐:上海海港 ﹣0.5 俄超23:00 阿克伦陶里亚蒂受 半/一 莫斯科中央陆军 推荐:莫斯科中央陆军 ﹣0.5/1 德乙 0:30 波鸿 半/一 奥斯纳布鲁克 推荐:波鸿 ﹣0.5/1 德乙 0:30 布伦瑞克 平手 柏林赫塔 推荐:布伦瑞克 ﹣0 西甲 1:00 桑坦德竞技 平/半 埃尔切 推荐:桑坦德竞技 ﹣0/0.5 丹麦超 1:00 霍森斯 受半/一维堡 推荐:维堡 ﹣0.5/1 荷甲 2:00 格罗宁根 一/球半 福图纳锡塔德 推荐:格罗宁根 ﹣1

27 Aug 2026, 15:10 UTC208 viewsread 29 August 2026
Photo

开云体育注册送138!世界杯赞助商官网~ 米兰/乐鱼/爱体育/YY体育/九游/mk/华体会/爱游戏 享受一百送一百活动! 👇👇彩金申请👇👇 @kaiyundog @ergou2000 👇👇注册网址👇👇 MK体育官网:http://mktyvip80.com MK TG投注机器人:https://t.me/MK888bot?start=24921304_B ————————————————— 开云官网: kaiyun.io 防劫持网址: http://yun674.vip 防劫持网址:http://yun675.vip 备用网址: http://yun676.vip ————————————————— YY体育官网:http://yy38vip.com 防劫持网址:http://yyty39.com 防劫持网址:http://yyvip21.net ————————————————— 米兰体育官网: https://mi

27 Aug 2026, 11:38 UTC218 views0 reactionsread 29 August 2026
Photo

米兰大哥 恭喜恭喜,喜提彩金588,每天一爆 ,全是大奖!!!电子双响炮爆奖的记得找我申请,给我冲鸭兄弟们!!!!!

27 Aug 2026, 08:00 UTC220 views1 reactionsread 29 August 2026

2026.8.27 足球早盘推荐 卡塔尔联22:15 加拉法VS艾沙姆 推荐:全场大3球 瑞典23:30 法鲁VS布洛马波卡纳 推荐:全场大3.5球 欧协联00:45 摩纳哥VS扎布热矿工 推荐:全场大3球 欧协联00:45 弗赖堡VS马瑟韦尔 推荐:主队-2 欧罗巴杯01:00 比尔森胜利VS红星 推荐:全场大3球 欧罗巴杯02:00 奥胡斯VS本菲卡 推荐:全场大3球 欧协联02:30 布莱顿VS特罗姆瑟 推荐:主队-2 英联杯02:30 切尔西VS卢顿 推荐:全场大3.5球 英联杯03:00 富勒姆VS温布尔登 推荐:主队-2 西甲03:00 巴塞罗那VS毕尔巴鄂 推荐:全场大3.5球

1

26 Aug 2026, 15:00 UTC239 viewsread 29 August 2026
Photo

开云体育注册送138!世界杯赞助商官网~ 米兰/乐鱼/爱体育/YY体育/九游/mk/华体会/爱游戏 享受一百送一百活动! 👇👇彩金申请👇👇 @kaiyundog @ergou2000 👇👇注册网址👇👇 MK体育官网:http://mktyvip80.com MK TG投注机器人:https://t.me/MK888bot?start=24921304_B ————————————————— 开云官网: kaiyun.io 防劫持网址: http://yun674.vip 防劫持网址:http://yun675.vip 备用网址: http://yun676.vip ————————————————— YY体育官网:http://yy38vip.com 防劫持网址:http://yyty39.com 防劫持网址:http://yyvip21.net ————————————————— 米兰体育官网: https://mi

26 Aug 2026, 07:26 UTC263 viewsread 29 August 2026
Photo

米兰大哥 恭喜恭喜,喜提彩金588,一天一领的爆奖,也算是拉出技巧了 牛逼 电子双响炮爆奖的记得找我申请,给我冲鸭兄弟们!!!!!

26 Aug 2026, 06:59 UTC262 viewsread 29 August 2026

⚽️8月27日足球赛事精选⚽️ 【丹麦杯 00:00】弗雷德里西亚 vs 欧登塞🔥🔥 弗雷德里西亚主场战术执行力极强体能占优! 👉盘口推荐:弗雷德里西亚[email protected] 【欧协资 00:45】维也纳快速 vs 哈茨🔥🔥 维也纳快速主导进攻节奏前场压制力拉满! 👉盘口推荐:维也纳快速[email protected] 【英联杯 02:45】托特纳姆热刺 vs 查尔顿🔥🔥 查尔顿防守收缩极其顽强战术纪律严明! 👉盘口推荐:查尔顿+1.5/[email protected] 【欧冠资 03:00】里昂 vs 费内巴切🔥🔥 费内巴切攻防转换高效有序韧性十足! 👉盘口推荐:费内巴切[email protected] 【南球杯 08:30】河床 vs 圣塔菲独立🔥🔥 河床主场底蕴极其深厚中前场传控流畅! 👉盘口推荐:河床[email protected] 【欧协资 23:00】古比斯 vs 沙姆洛克流浪🔥🔥 古比斯主场阵形保持紧凑反击极具威胁! 👉盘口推荐:古比斯[email protected]

25 Aug 2026, 15:00 UTC255 viewsread 29 August 2026
Photo

开云体育注册送138!世界杯赞助商官网~ 米兰/乐鱼/爱体育/YY体育/九游/mk/华体会/爱游戏 享受一百送一百活动! 👇👇彩金申请👇👇 @kaiyundog @ergou2000 👇👇注册网址👇👇 MK体育官网:http://mktyvip80.com MK TG投注机器人:https://t.me/MK888bot?start=24921304_B ————————————————— 开云官网: kaiyun.io 防劫持网址: http://yun674.vip 防劫持网址:http://yun675.vip 备用网址: http://yun676.vip ————————————————— YY体育官网:http://yy38vip.com 防劫持网址:http://yyty39.com 防劫持网址:http://yyvip21.net ————————————————— 米兰体育官网: https://mi

25 Aug 2026, 06:36 UTC277 views1 reactionsread 29 August 2026

⚽️8月26日足球赛事精选⚽️ 【欧冠资 00:45】沙巴巴库 vs 贝尔谢巴工人🔥🔥 沙巴巴库主场防线落位极快反击高效! 👉盘口推荐:沙巴巴库[email protected] 【沙特超 02:00】达曼协作 vs 利雅得胜利🔥🔥 利雅得胜利中前场推进有序火力网全面覆盖! 👉盘口推荐:利雅得胜利-1.5/[email protected] 【英联杯 02:45】南安普顿 vs 西汉姆联🔥🔥 西汉姆联中后场拦截覆盖面广攻防均衡! 👉盘口推荐:西汉姆联[email protected] 【西甲 03:00】瓦伦西亚 vs 皇家贝蒂斯🔥🔥 皇家贝蒂斯地面传控战术细腻韧性十足! 👉盘口推荐:皇家贝蒂斯[email protected] 【巴西杯 08:00】克鲁塞罗MG vs 米内罗竞技🔥🔥 克鲁塞罗MG气势如虹中前场冲击力强! 👉盘口推荐:克鲁塞罗[email protected] 【韩K1联 18:30】大田韩亚市民 vs 蔚山HD🔥🔥 蔚山HD战术纪律严明防守补位迅速! 👉盘口推荐:蔚山HD+0/0.5@1.

1

Showing the 12 most recent of 70 posts we hold for @ybergou. 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 4 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.

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.

Appears in Telegram’s recommendations for other channels

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.

🥇NO1推单【红单推荐频道】体育 电竞 百家乐 彩票 电子 足球 篮球 赚钱 博彩 欧冠 五大联赛 NBA每日更新
@ybgf9 · 34,806
Telegram ranks this channel #8 of 39 here — alongside 38 others — read 2 September 2026
推单体育赛事推荐足球篮球推单
@ybtytd · 138,910
Telegram ranks this channel #10 of 81 here — alongside 80 others — read 14 August 2026
电竞体育 LPL中文推单🫥
@dianjingtuidan1 · 95,231
Telegram ranks this channel #13 of 68 here — alongside 67 others — read 15 August 2026
五大联赛世界杯足球竞彩推荐
@ccty005 · 31,566
Telegram ranks this channel #20 of 57 here — alongside 56 others — read 5 September 2026
足球体育圈 中文推单频道(NBA·五大联赛每日竞彩红单推荐)
@tiyuquan · 107,605
Telegram ranks this channel #20 of 81 here — alongside 80 others — read 15 August 2026
足球推单 | 电竞推单
@mltytxdy · 56,508
Telegram ranks this channel #24 of 75 here — alongside 74 others — read 18 August 2026
⚽️暴击体育社区
@JNTY999 · 60,062
Telegram ranks this channel #25 of 77 here — alongside 76 others — read 22 August 2026
EBpay官方运营频道
@ebpay · 209,561
Telegram ranks this channel #27 of 34 here — alongside 33 others — read 2 September 2026
体育电竞推单交流 欧洲杯中文赞助(接广告合作)🫥
@tiyu_3 · 94,228
Telegram ranks this channel #29 of 53 here — alongside 52 others — read 14 August 2026
电竞体育推单 LPL中文赞助🫥
@duanzib · 94,781
Telegram ranks this channel #35 of 55 here — alongside 54 others — read 15 August 2026

This channel appears in 10 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“☁️开云体育官网🏆体育推单欧洲杯” (@ybergou), 10,496 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/ybergou.

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.