#网友曝光 #米兰体育 9月份吧,在TG找了个开云体育大群,里面人挺多的,几千个。然后按链接注册了米兰体育,之前就听说过这个平台,但是没想到这种平台连几万都黑。9月25号充了几千块钱进去,吃国补篮球欧篮杯红了3个,打到26号凌晨,提了一笔1w的,系统秒风控。应该盯我挺久的了,因为这个月算下来加上没提现的差不多5w左右吧。然后就让我提供KYC手持身份证,让我等3天到7天。今天29号,刚刚起床点开看看好了没有,直接显示账号封禁。客服经理让我联系平台客服,平台客服说我投注违规,我让说哪条违规,他说不出来,来来回回重复投注违规。 我现在是懂了,经济那么差了吗?几万块都明着黑。在这我劝大家在米兰有号的抓紧提现出来别玩了,挺恶心人的。输钱的时候不会让你停,一赢点直接限制你提款。你们开云系也是老牌子了,没想到那么恶心人的,几万都黑,没想到还没人处理。如果没人愿意处理,我有空我就去找足球群、米兰群,发布我被黑的经历,因为太恶心人了。

Channel
曝光黑平台&黑佣金
@BG886
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
54,584subscribers
-2,396 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001835254716 |
|---|---|
| Type | Channel |
| Username | @BG886 |
| Description | 🍉吃瓜: @BG888 💬东南亚交流 @ty888 ☎️投稿/曝光: @T3333 发财助手 © 2018-2026 祝商祺 🎉 #曝光 #吃瓜 #黑平台 #黑佣金 #不出款 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/BG886 |
Topic
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 16:58 | 54,584 | -251 |
| 19 Sept 2026, 15:57 | 54,835 | -104 |
| 17 Sept 2026, 02:00 | 54,939 | -48 |
| 15 Sept 2026, 05:21 | 54,987 | -29 |
| 13 Sept 2026, 14:01 | 55,016 | -93 |
| 11 Sept 2026, 18:41 | 55,109 | -148 |
| 9 Sept 2026, 07:19 | 55,257 | -244 |
| 6 Sept 2026, 02:58 | 55,501 | -111 |
| 3 Sept 2026, 19:17 | 55,612 | -46 |
| 2 Sept 2026, 11:37 | 55,658 | -47 |
| 1 Sept 2026, 09:54 | 55,705 | -105 |
| 31 Aug 2026, 07:12 | 55,810 | -67 |
| 30 Aug 2026, 09:14 | 55,877 | -61 |
| 29 Aug 2026, 07:16 | 55,938 | -41 |
| 28 Aug 2026, 06:54 | 55,979 | -30 |
| 27 Aug 2026, 04:13 | 56,009 | -38 |
| 26 Aug 2026, 05:28 | 56,047 | -56 |
| 25 Aug 2026, 04:54 | 56,103 | -49 |
| 24 Aug 2026, 03:18 | 56,152 | -93 |
| 22 Aug 2026, 13:44 | 56,245 | first reading |
Engagement
78 posts held, back to 5 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 107 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.331%
- avg views ÷ 54,584 subscribers
- Avg views / post
- 181
- 45 posts measured
- Reaction rate
- 0.588%
- reactions ÷ views · ER floor
- Posts in window
- 45
- of 78 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 5 of 45 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 September 2026 |
|---|---|
| Posts held | 78 (5 August 2026 – 29 September 2026) |
| Views total | 8,140 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Sept 2026, 05:00 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.
What this channel posts
- Photos
- ≈14,400
- Videos
- ≈169
- Links
- ≈583
Lifetime counters from Telegram’s own channel header, read 29 September 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.
- Video runtime
- 2m 41s
- Average length
- 18s
Measured directly from 9 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
4 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 75.0% | |
| 👏 | 1 | 25.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 7 of the 78 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 78 most recent posts we hold, published 5 August 2026 to 29 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
#网友投稿 #米兰体育 本人前前后后在米兰体育输了三十多万,一直都是正常投注。输了这么多的时候,从来没人告诉我违规,也没人说账户有问题。关键福利彩金都没领过。结果9月12日,账户突然被告知“违操作”,余额直接被清空。 最可笑的是什么?输了几十万的时候,一切正常;刚续赢了两单,就开始说我违规。 本月本人又输了8万多,好不容易赢回1万多,结果这1万多的余额也直接被清零。那我就想问一句:到底什么叫违规?不要一句轻飘飘的“违规操作”,就把用户账户里的余额全部清掉。 更离谱的是,这个账号还是我当时在米兰体育工作期间,通过你们自己的线下渠道注册的。 出了问题以后,我第一时间找之前的同事处理,本来想着大家把事情说清楚就算了,结果呢?不处理、不解释,最后直接拉黑。三十多万的输款我都认,愿赌服输。但凭什么我刚赢回来的一万多,也可以一句“违规”就全部拿走?有人愿意处理,我就正常沟通;没人处理,我就通过曝光你们照片来处理了今天先发点马赛克的没人…
👏1
#网友曝光 本人在 #假365 昨天注册了个号玩电子,充了1万,盈利到2万5后发起提款,结果半小时没到账。我去问客服,客服当时说早上9点再来咨询。我等到9点,客服说他们稳定运营多年,从来不会不出款。之后我等到9点提示出款成功,但并没有收到这笔钱。再次询问客服,客服像机器人一样回答说自动出款卡单了,客服无法干涉。从提款到现在已经过去30个小时了,没有收到一分钱。这种黑平台,在监管壁垒下只进不出,连3000u都出不起的小作坊,却号称自己资金雄厚。奉劝各位朋友远离这种不知名的黑平台。
#51u娱乐 纯杀猪黑网,网址是 51u.com。今天放假,我准备去试试手气。看到这个网很多频道有广告,以为有实力,就入了 1000U 去游戏。玩 PG 电子时,结果在玩游戏不到 5 分钟,账号突然被冻结了。这跟入款直接黑没区别。客服直接说什么同 IP 同设备冻结账号。这个网本来就是要用国外的 IP 才可以登录网址的。这垃圾黑网黑钱也不找个好点的理由,怎么可能入款到玩游戏不到 5 分钟就直接冻结账号黑了?大家千万要避雷,注意这个杀猪盘!
#曝光杀猪盘 #云顶集团 #黑款88万 事情是这样的,两天前凌晨,因为喝酒后冲动想玩游戏,我在云顶平台注册并充值了12万余U,按照当时平台的汇率折合人民币大约88万元。 由于我以前也接触过该平台,对平台有一定信任,因此充值时没有过多顾虑。 但充值完成后,我的账户却一直没有到账。联系客服后,对方先是说我的资金存在问题,要求我提供手持身份证以及个人身份资料进行核实。 因为身处东南亚,本身对个人身份信息就比较敏感,所以我没有同意提供这些资料。况且我选择使用U充值,本身也是考虑到资金转账的便利性以及个人隐私问题。 之后客服表示需要交给财务核查,让我等两天,并承诺时间到了会给我处理。 现在两天时间到了,我再次联系客服,对方的说法:一会说我的资金“来路不明”,一会又要求我提供本人身份信息进行核实。 更关键的是,我查询了这笔U的链上地址记录。从链上交易记录来看,我充值的U已经成功进入对方提供的收款地址,之后这笔资金又从该地址…
❤1
#网友投稿 #凤凰体育 我开云账户都是v10 正常用户 。电话受邀到凤凰体育 玩了几个月打到v10 存款大概几百万上千万 总体并未赢钱 在8月份最后一次存款五十多万左右 然后打百家乐到70万账户直接被封不给登陆 要求提供一堆资料 三条代理也直接不回复,所有凤凰体育的千万不要在相信他们说的,高层看到联系我协商处理不要因为一些代理抹黑公司。我是绝对正常且优质客户只玩百家乐 没有过其他下注且总体都是输钱 本月在开云也是输了三百多万,开云集团如果一直给这些黑钱代理这样运营也迟早出问题 资料泄漏 且一模一样的平台背书 请给个说法 ,凤凰的高层看到请小编联系我方式出来解决
https://yl8888.cc #永利国际 小平台客服就那两个领40块钱反水 提现不了别充值这种平台 比玩家还穷。纯黑。
#网友曝光 首先我是看到6g在飞机很多群都有投放广告 我才去做的代理。 期间推广了半个月没有问题,直到大哥输钱了之后,平台突然跟我说我的玩家禁止参加活动。我跑去问招商,招商跟我说没问题还能继续推广,我真的是信了邪,结果第二天玩家玩pg就被黑了。 我玩家全部都输钱的 然后玩家玩电子也黑款 跟我说套利 玩电子都能套利? 然后佣金也不打算给我了 说我套佣金? 玩家输了一万多u 你们还给不起佣金,说白了说实力别出来开平台。
#黑平台 9月13日,我在 #英博体育 平台注册账号,充值30000元,成为平台会员。 9月14日,我申请提款33000元,提款失败。联系平台客服后,客服让我联系平台推广人员:xiaoluya888(小鹿)、yy120119(左右)。小鹿回复沟通,另一名推广“左右”一直未回复。小鹿告知我账户存在异常,要求我继续在平台刷流水才能提现,我当时没有防备,继续在该平台参与球类、百家乐投注。 9月15日下午,我收到账户异常短信,登录英博体育APP发现:有人私自修改我的账户密码,登录我的账号进行百家乐大额投注;投注选择高赔率、大概率亏损的选项(闲对、和等),短短几分钟内,账户内3万余元余额被全部亏空。 9.17号 我发曝光频道后有人称自己是英博平台的来处理这个事情,(怀疑这个人就是傻逼上级狗推)沟通两三天,对方没有解决资金问题,反而要求我先删除曝光帖子。这个人是不是做推广把脑子推坏了?这种傻逼话也说的出来,本来我曝光就是希望大家避坑,此…
❤1
#网友曝光 #728平台 曝光728平台代理未经过别人同意,把别人的钱转给他人,对我造成巨大的经济损失,本来就输了几十万了,下个一千块钱都黑 网址:728.cc
#网友爆料 #乐高体育 #财神娱乐 ⚠️ 避坑提醒:乐高体育 / 财神娱乐 U1.TOP 博彩诈骗 今天在飞机上先后收到两个人发来的博彩网址,分别进入两个平台。 第一个平台充值 1000元,盈利后申请提现 1300元;第二个平台充值 500元,申请提现 600元。两个平台提现时都被告知需要等待,之后迟迟不到账。 更可疑的是,两个平台的飞机客服几乎同时离线,而且长时间不上线。官网客服则以“没有实名,需要风控”为由拒绝处理提现,在我提出质疑后,直接将我拉黑。 两个平台从页面、操作方式到客服模式都高度相似,存在明显关联,大家务必提高警惕。 尤其是飞机群、私聊发来的博彩网址,不要因为可以正常充值、前期甚至能够盈利,就认为平台可靠。真正需要警惕的是提现时拖延、客服失联、找理由拒绝提现甚至直接拉黑。
#网友投稿 #鼎盛娱乐 今天我把自己在鼎盛娱乐的真实经历公开出来,不是为了夸大,也不是为了带节奏,只是想让大家知道我到底经历了什么。 我今年6月份注册鼎盛娱乐,之后一直有在玩。到了8月份,因为手气不好,我暂时停了一段时间。后来重新登录,领取了一个18元代理红包,然后开始玩“赏金大对决”。 让我完全没想到的是,我当时甚至没有进入免费游戏环节,却意外爆出了1800多元的奖金,系统显示最高给到了2200倍。 说实话,那一刻我真的非常开心。 但是,真正让我意外的事情还在后面。 中奖之后,我第一时间退出游戏,马上申请提现。 一个小时……两个小时…… 钱始终没有到账。 于是我联系客服,客服告诉我的理由是: “出款异常,交由第三方处理。” 我继续等。 24小时过去了,平台依然没有给出一个合理、明确的解释。 直到18号晚上9点18分,平台才告诉我,自动出款失败的原因是: “同设备。” 并且平台称,我和我的下级使用了…
Showing the 12 most recent of 78 posts we hold for @BG886. 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.
Forward network
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.
Mentions
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.
Channels Telegram recommends alongside this one
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.
@vip35r · 47,471#1
@anwei2 · 34,725#2
@iiiik · 49,140#3
@heicaibaog · 82,554 (as read 23 August 2026)#4
@Banma_xinwen · 91,805#5
@feilvbinghuarenriji · 16,655#6
@aza520 · 3,283#7
@dny1577 · 5,343#8
@tghuarenba · 44,364#9
@svipzz · 89,708#10
@dxdb001 · 6,917#11
@toutiao_4 · 1,166#12
@cctv_dy · 36,686#13
@bodu08 · 58,821#14
@baoguang821 · 51,566#15
@HR8877 · 313,706#16
@xinhuaribao · 939#17
@bbb1b · 348,524#18
@xinwen118 · 114,190#19
@tg04277 · 33,845#20
@vipn8888 · 67,457#21
@baoguang_bc · 39,172#22
@quanqiubaoliao · 172,311#23
@feilvbinhuarenzixun · 72,699#24
@gouzaibaoliao · 2,124#25
@feixingzhe0 · 58,575#26
@DNYBG234 · 86,663#27
@baoguangba088 · 236,958#28
@svip40 · 110,383#29
@bg888 · 343,655#30
@baoguangqun110 · 37,625#31
@jiuboo · 20,848#32
@SB919 · 128,290#33
@tg89aa · 137,688#34
@bvl222 · 45,237#35
@phnews · 14,671#36
@huohu158 · 205,209#37
@BG_BG8 · 38,746#38
@dny099 · 75,081#39
@DNYXW008 · 79,700#40
@dsj0161 · 2,023#41
@baoguangqun999 · 37,189#42
@hrs166 · 50,473#43
@baoguangee · 179,272#44
@makatinews · 34,540#45
@jsj62 · 22,648#46
@baoguang032 · 21,224#47
@baoguang85 · 31,656#48
@rjjjj · 42,292#49
@v3903 · 52,159#50
@mbhl1 · 2,505#51
@Dubaihuarenzixun · 65,366#52
@TGPG999 · 4,714#53
@gejige · 185,132#54
@baoguang008 · 3,279#55
@bg833 · 322,837#56
@Dzx199 · 23,311#57
@cctvPH · 190,942#58
@kaleminews · 207,918#59
@BG2288 · 81,773#60
Read from Telegram’s recommendation API, most recently 23 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.
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.
@feixingzhe0 · 58,575
Telegram ranks this channel #4 of 83 here — alongside 82 others — read 19 August 2026
@bvl222 · 45,237
Telegram ranks this channel #5 of 65 here — alongside 64 others — read 23 August 2026
@DNYBG234 · 86,663
Telegram ranks this channel #6 of 77 here — alongside 76 others — read 16 August 2026
@TGBG8888 · 85,601
Telegram ranks this channel #10 of 82 here — alongside 81 others — read 21 August 2026
@BG2288 · 81,773
Telegram ranks this channel #10 of 72 here — alongside 71 others — read 15 August 2026
@Banma_xinwen · 91,805
Telegram ranks this channel #11 of 77 here — alongside 76 others — read 16 August 2026
@bodu08 · 58,821
Telegram ranks this channel #14 of 73 here — alongside 72 others — read 22 August 2026
@bocaishen8 · 150,059
Telegram ranks this channel #16 of 71 here — alongside 70 others — read 22 August 2026
@xinwen118 · 114,190
Telegram ranks this channel #17 of 78 here — alongside 77 others — read 15 August 2026
@cctv_dy · 36,686
Telegram ranks this channel #18 of 70 here — alongside 69 others — read 22 August 2026
@huohu158 · 205,209
Telegram ranks this channel #19 of 74 here — alongside 73 others — read 15 August 2026
@tg89aa · 137,688
Telegram ranks this channel #20 of 71 here — alongside 70 others — read 22 August 2026
@baoguang2022 · 148,798
Telegram ranks this channel #20 of 76 here — alongside 75 others — read 15 August 2026
@dny099 · 75,081
Telegram ranks this channel #21 of 67 here — alongside 66 others — read 22 August 2026
@CG887 · 108,701
Telegram ranks this channel #23 of 72 here — alongside 71 others — read 15 August 2026
@ttkb0 · 121,519
Telegram ranks this channel #23 of 77 here — alongside 76 others — read 14 August 2026
@baoguang821 · 51,566
Telegram ranks this channel #24 of 71 here — alongside 70 others — read 22 August 2026
@vipn8888 · 67,457
Telegram ranks this channel #24 of 79 here — alongside 78 others — read 18 August 2026
@baoguang_123 · 119,228
Telegram ranks this channel #24 of 73 here — alongside 72 others — read 14 August 2026
@vjtyd · 72,407
Telegram ranks this channel #25 of 59 here — alongside 58 others — read 23 August 2026
@uuuuuf · 282,422
Telegram ranks this channel #25 of 82 here — alongside 81 others — read 17 August 2026
@DNY88880 · 91,312
Telegram ranks this channel #27 of 53 here — alongside 52 others — read 19 August 2026
@feilvbin198 · 97,008
Telegram ranks this channel #27 of 70 here — alongside 69 others — read 19 August 2026
@dny88 · 65,507
Telegram ranks this channel #28 of 73 here — alongside 72 others — read 21 August 2026
This channel appears in 54 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“曝光黑平台&黑佣金” (@BG886), 54,584 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/BG886.
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.