Channel
@dibai7
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
10,238subscribers
+611 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002499168306 |
|---|---|
| Type | Channel |
| Username | @dibai7 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/dibai7 |
National news — 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 55% 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 7 other registered channels. 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 |
|---|---|---|---|
| @yatai2/194257 Aug 2026, 10:24 UTC | @dibai7/20281 · this entry7 Aug 2026, 10:24 UTC | 1.00 | under a minute |
| @yatai2/194317 Aug 2026, 11:27 UTC | @dibai7/20287 · this entry7 Aug 2026, 11:27 UTC | 1.00 | under a minute |
| @yatai2/194387 Aug 2026, 11:52 UTC | @dibai7/20294 · this entry7 Aug 2026, 11:52 UTC | 1.00 | under a minute |
| @dibai7/20296 · this entry7 Aug 2026, 12:30 UTC | @yatai2/194407 Aug 2026, 12:30 UTC | 1.00 | under a minute |
| @yatai2/194757 Aug 2026, 15:17 UTC | @dibai7/20331 · this entry7 Aug 2026, 15:17 UTC | 1.00 | under a minute |
| @dibai7/20281 · this entry7 Aug 2026, 10:24 UTC | @yatai1/193987 Aug 2026, 10:24 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @yatai2 | 17 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (13–4) |
| @yatai1 | 17 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @yatai1 (15–2) |
| @feilong | 17 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @feilong (16–1) |
| @ytxw | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @ytxw (13–1) |
| @xigang8I8 | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @xigang8I8 (13–1) |
| @guancha | 8 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @guancha (8–0) |
| @mlxy | 7 (7/7 hand-verifiable sample passed) | 1.00 | under a minute | @mlxy (5–2) |
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. 70 of the 70 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 17 comparable posts for this entry, running 7 August 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.
Across the whole group of 8, the earliest publisher we hold is @yatai2. 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.
This channel’s posts match, word for word or near enough, posts on 7 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Oct 2026, 10:16 | 10,238 | -153 |
| 22 Oct 2026, 11:54 | 10,391 | -390 |
| 21 Oct 2026, 06:36 | 10,781 | -263 |
| 20 Oct 2026, 02:57 | 11,044 | -427 |
| 19 Oct 2026, 01:45 | 11,471 | -200 |
| 18 Oct 2026, 01:38 | 11,671 | -386 |
| 17 Oct 2026, 00:26 | 12,057 | -190 |
| 16 Oct 2026, 00:08 | 12,247 | -215 |
| 14 Oct 2026, 22:35 | 12,462 | -394 |
| 13 Oct 2026, 18:30 | 12,856 | -1,080 |
| 10 Oct 2026, 00:22 | 13,936 | -434 |
| 5 Oct 2026, 22:39 | 14,370 | -239 |
| 30 Sept 2026, 12:38 | 14,609 | -798 |
| 18 Sept 2026, 05:39 | 15,407 | -166 |
| 15 Sept 2026, 22:02 | 15,573 | -287 |
| 14 Sept 2026, 02:57 | 15,860 | -227 |
| 12 Sept 2026, 07:55 | 16,087 | -295 |
| 10 Sept 2026, 06:37 | 16,382 | -301 |
| 6 Sept 2026, 23:37 | 16,683 | +9,643 |
| 2 Sept 2026, 16:37 | 7,040 | first reading |
196 posts held, back to 7 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 24 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 196 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 59 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.
#小姐姐爆料：此人叫峰哥，木牌财通，有一个公司，200来人，做军包的。 2025年4月3号，我是通过妈咪认识的他，在天空之城。5月7号说包养我，说的15万人民币一个月，我就去找他了。 去木牌—西港—吉隆坡—新加坡—日本，跟他一年多。偶然一次，他玩这手机睡着了，没关，有条消息提示我看了一下，一个叫阿亮的人发来的，汇报工作，人口贩卖，骗招去他们公司，还有一些他们看不上的，贩卖到七星海、奥斯马、妙瓦底，就一天支出10多万U，也就等于卖出去十多个人。 直到两个月前，我感觉身体不适，没有按期来姨妈，去检查怀孕了。说娶我、对我好什么的，然后过两天不辞而别跑路了，把我一个人丢日本。还好之前有拍照他的，还有身份证。 你不仁，别怪我不义。我要35万U，给我的孩子和下半生做个保障。他同意了，给了15万U。现在消息不回、推脱、联系不上，直接注销飞机。通过朋友找到了他现在用的飞机。 如果你再不给我剩下的，我曝光，让你回不去国。你自己开公司做军…
#网友投稿：根据提供的信息，近期伊斯兰堡老巴的操作如下： 1.F6 F7 F8地区FIA警察巡逻车多，信号车多，看到中国人拦下来就要5000卢比。 2.别墅没有扫荡，但是会上门登记检查是否有无护照人员居住，已有多个网友告知已被登记检查，遇到老巴刁难适当给点小费即可处理，底线是无设备人员均有护照。 3.电脑手机要藏严实一些，远离办公区域。 4.尽量不得罪老巴服务人员，保洁保安等，被他们无中生有举报了得不偿失。 5.注意看监控是否有老巴来门口拍照，也要防止老巴服务人员拍照。 6.有群友打车遇到老巴对比照片，大概率在寻找冲园区无护照人员，这些兄弟尽量避免出门。 ———————————————— 📣欢迎加入东南亚华人交流群 🔗 https://t.me/dnyhr0 📣西港日记/柬埔寨新闻资讯 🔗：https://t.me/xigang8I8 ✅广告招商投稿澄清爆料： @jpz8i8
#国内资讯：武汉江夏警方及时拦截56万元涉诈现金 8月25日，武汉市江夏区公安分局反诈中心接到紧急预警：一名群众疑似遭遇电信诈骗，准备在线下商场交付大额现金。民警迅速赶赴现场布控，成功抓获前来取款的诈骗团伙成员，当场查获涉案现金56万元，并于当日将钱款全额返还受害人。 当天10时许，江夏公安反诈中心接到预警，得知有群众可能被诱导在线下交付现金。民警杜杨、何园立即带队赶赴相关地点开展排查。 在现场蹲守过程中，一名戴口罩、背双肩包的男子引起民警注意。该男子长时间在商场周边徘徊观望，反复查看手机，却迟迟没有进入商场。民警结合前期线索进行比对后，确认其为诈骗团伙安排的“取手”，而按照对方要求将车辆停至指定地点的车主，正是受骗群众徐女士。 12时14分，嫌疑人从徐女士手中接过现金包裹，准备转身离开。埋伏在周边的便衣民警迅速展开抓捕，将其当场控制，并查获涉案现金56万元。 经查，徐女士此前在网上炒股时，被陌生网友诱导进入虚假投资平…
#星球支付 #亚信集团 #亚信支付 #唐僧 #小鑫 #亚信娱乐 西港和天下烟酒行（开实体店是为了黑产掩人耳目，逃避中国警方追查）老板唐僧因周围人陆续被抓现改名叫小鑫，福建人，在福建当地带了很多人来西港发展黑产，获利巨额资产，用赚来的黑金在香港等地购置房产等一些列奢靡消费，这些都是中国老百姓累死累活的血汗钱，旗下有众多员工及洗钱渠道，为柬埔寨西港金边波贝等地洗钱元老与多名坑害无数国人的诈骗盘总有深度合作，现长期在吉隆坡规避柬埔寨大扫除黑灰产风波，为盘口洗钱等，自己做大股东退居幕后作为资金盘等黑产金主，旗下产业有亚信娱乐：@YXGameRobot ，u86.com 等赌博链条，支付通道等一条龙式服务为国内及国外诈骗盘口洗钱，这些可是多少人的血汗钱发生了多少条人命！员工自称只要有电脑去哪里都能干，不能再让他们这样放飞自我任自害人，请中国及美国，韩国、欧洲等国际警方追查、彻查一系列行为，追缴违法所得等，这条大鱼只要一被抓很多人都会被一…
#西湖度假酒店和西湖娱乐场澄清声明： 近期，网络及市场上出现较多使用“西湖”相关名称的赌博网站、博彩平台及线上综合平台，部分名称与西湖度假酒店和西湖娱乐场相同或相似，容易造成公众误解和混淆。 #在此郑重声明： “西湖”名称相同或相似，并不代表属于西湖官方。 任何第三方赌博网站、博彩平台及线上业务，未经正式确认，均不能代表西湖度假酒店和西湖娱乐场，也不代表双方存在授权、合作或经营关系。 请广大公众注意辨别，认准官方信息，谨防名称混淆。 本声明仅用于澄清事实，不针对任何特定平台、机构或个人。 特此声明 西湖度假酒店和西湖娱乐场 2026年8月28日 ———————————————— 📣欢迎加入东南亚华人交流群 🔗 https://t.me/dnyhr0 📣西港日记/柬埔寨新闻资讯 🔗：https://t.me/xigang8I8 ✅广告招商投稿澄清爆料： @jpz8i8
#温馨提示：喜欢用ChatGPT的狗推注意了！！！ ChatGPT临时聊天可直接保存，还能读取已有记忆，但临时聊天并不一定意味着所有内容都不会被保存或使用。根据当前功能设置，聊天内容可能支持直接保存，系统也可能读取账户中已有的记忆信息，以便提供更加连贯、个性化的回答。 因此，在开始对话前，建议先查看相关提示、隐私政策和功能设置，确认聊天记录、记忆功能及数据使用范围。涉及身份证号、账号密码、联系方式、财务信息、工作机密和他人隐私等敏感内容时，应尽量避免直接输入。若不希望系统读取或记录已有信息，请及时检查并关闭相应的记忆、历史记录或个性化选项 使用完成后，也应根据需要删除聊天内容，并定期管理账户中的记忆和隐私权限。使用任何人工智能工具前，都要保持谨慎，先确认功能规则，再决定是否输入重要信息。 ———————————————— 📣欢迎加入东南亚华人交流群 🔗 https://t.me/dnyhr0 📣西港日记/柬埔寨新闻资讯 …
⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ⚡️全球直登 ⚡️BBIN 联合迪威娱乐城 联手打造优质娱乐平台！ ⚡️支持 微信 支付宝 银行卡 充值 ⚡️支持 USDT ABA 充值 ⚡️支持 波币 NO钱包 购宝 多种钱包 充值 ⚡️24小时存取不打烊 ⚡️充值提现实时到账 🧂⚽️🏀🏈⚾️🥎🎾🏐 ⚡️官方频道: @diwei4 ⚡️官方客服: @diwei2 ⚡️官方代理：@diwei3 ⚡️官方网址: diwei.app ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️
#老挝资讯：公安部部长视察网络犯罪专项整治工作情况 8月26日，老挝党中央书记处书记、公安部部长万通·孔玛尼中将一行前往万象市斯科达邦县 Lak Hin 村和 Huay Hom 村两处目标地点，现场督导视察公安部网络犯罪及网络赌博专项执法行动组的打击抓捕工作。 此 前，专项行动组联合相关部门执法人员迅速出击，成功对上述两处网络犯罪窝点实施突击搜查，当场抓获2名犯罪嫌疑人，并查获大量作案工具，包括笔记本电脑、手机SIM卡、猫池（SIM box）、网络收发设备、蓄电池及其他相关配件。此次行动彰显了执法部门打击清剿网络犯罪、维护社会治安稳定的坚决态度。 视察期间，公安部部长对专项行动组及全体参与执法的警员给予了高度赞扬，肯定了他们在情报排查、目标锁定及侦破撤查过程中的高度责任感与专业素养。同时，部长特别要求行动组及相关执法人员依法依规妥善保管查扣的全部证物，确保司法程序的严密性，为后续依法诉讼提供确凿证据。 此外，公安部部长指…
#马来西亚资讯：雪兰莪警方捣毁5个诈骗呼叫中心 ，逮捕40人，专门诈骗中港台及日本受害者 8月27日，马来西亚雪兰莪警方于8月18日至25日期间展开一连串突击行动，捣毁5个藏身住宅内的诈骗呼叫中心，逮捕40名嫌疑人，包括3名马来西亚男子、32名外国男子及5名外国女子。 警方表示，5个诈骗窝点分别位于双溪毛糯、沙亚南武吉里茂、加影及梳邦再也，其中双溪毛糯有两个窝点。诈骗集团租用独立洋房、半独立式住宅、双层排屋及公寓作为掩护，并将普通住宅改造成呼叫中心。这些团伙相信自2026年年中起陆续运作。 初步调查显示，各窝点使用不同诈骗手法，目标涵盖中国大陆、香港、台湾及日本受害者，涉及冒充警察电话诈骗、虚假成人影片订阅及爱情诈骗等模式。 警方于8月18日首先突击双溪毛糯一处呼叫中心，逮捕10名外国男子。该团伙主要以日本人为目标，操作员冒充警察致电受害者，并使用外国警察证件及警员照片增强可信度。警方目前正核查相关证件真伪，并将冒充外…
金边一警局副局长幽会情妇被抓包 撬天花板爬屋顶光膀出逃 据柬媒报道，昨天中午，金边贡武区发生一起抓奸丑闻。当地一名负责安全事务的警局副局长与约20岁情妇幽会时，被其35岁妻子率亲属当场堵截。 慌乱中，该副局长竟撬开天花板铁皮光膀逃上屋顶流窜，抛下情妇独自面对。据悉，两人一个月前就曾被抓包并签署过断绝往来协议。 目前，该情妇已被带回警局签下保证书，警方将传唤涉事副局长夫妇进行调解。 做大的，要懂事 每月有钱收就行了～～ ———————————————— 📣欢迎加入东南亚华人交流群 🔗 https://t.me/dnyhr0 📣西港日记/柬埔寨新闻资讯 🔗：https://t.me/xigang8I8 ✅广告招商投稿澄清爆料： @jpz8i8
#第二届各国议会发言人会议通过《金边宣言》 今日，为期3天的第二届各国议会发言人会议落下帷幕，参会代表正式通过《金边宣言》。 宣言明确反对贸易、技术、供应链武器化，要求依据国际法和平化解冲突，强化多边合作、共同对抗全球危机，推进联合国可持续发展目标落地。 会议还确定印尼承办2027年第三届同类型大会，共有21个国家议会代表参与本次会议。 ———————————————— 📣欢迎加入东南亚华人交流群 🔗 https://t.me/dnyhr0 📣西港日记/柬埔寨新闻资讯 🔗：https://t.me/xigang8I8 ✅广告招商投稿澄清爆料： @jpz8i8
金边一按摩店调包外籍游客2.25万美元 警方锁定涉案嫌犯 近日，金边隆边区发生一起调包盗窃案。8月19日晚，一名外籍游客在一按摩店内被偷走22,500美元现金，并被换成冥币。受害者于次日凌晨报警。 警方接报后赶赴现场，发现涉事店铺已关门停业。经联系房屋出租人调查，警方现已成功锁定租户及按摩店员工等犯罪嫌疑人。 目前警方正全力追捕，承诺将依法严惩、决不姑息。 人最终会抓到， 但很可能钱已经没了～～ ———————————————— 📣欢迎加入东南亚华人交流群 🔗 https://t.me/dnyhr0 📣西港日记/柬埔寨新闻资讯 🔗：https://t.me/xigang8I8 ✅广告招商投稿澄清爆料： @jpz8i8
Showing the 12 most recent of 196 posts we hold for @dibai7. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“💐东南亚爆料@dibai💐” (@dibai7), 10,238 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/dibai7.
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.