Channel
@mbhl1
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
2,608subscribers
+97 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001571945006 |
|---|---|
| Type | Channel |
| Username | @mbhl1 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/mbhl1 |
Other / unclassifiable — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 the other topics.
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 in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 17 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @Banma_xinwen/1077788 Aug 2026, 12:56 UTC | @mbhl1/42257 · this entry8 Aug 2026, 12:56 UTC | 1.00 | under a minute |
| @Banma_xinwen/1077828 Aug 2026, 12:58 UTC | @mbhl1/42261 · this entry8 Aug 2026, 12:58 UTC | 1.00 | under a minute |
| @Banma_xinwen/1077838 Aug 2026, 13:35 UTC | @mbhl1/42265 · this entry8 Aug 2026, 13:35 UTC | 1.00 | under a minute |
| @Banma_xinwen/1077848 Aug 2026, 13:51 UTC | @mbhl1/42269 · this entry8 Aug 2026, 13:51 UTC | 1.00 | under a minute |
| @Banma_xinwen/1077878 Aug 2026, 14:04 UTC | @mbhl1/42270 · this entry8 Aug 2026, 14:04 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Banma_xinwen | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | @Banma_xinwen (5–0) |
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. 5 of the 5 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 10 comparable posts for this entry, running 8 August 2026 to 8 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.
Of the group of 17 channels, the one whose matching posts we hold earliest is @miandianhuarenzixun. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 11 November 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 is in a group of 17 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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 |
|---|---|---|
| 10 Nov 2026, 00:35 | 2,608 | +7 |
| 6 Nov 2026, 23:27 | 2,601 | +11 |
| 3 Nov 2026, 17:39 | 2,590 | +10 |
| 1 Nov 2026, 01:10 | 2,580 | +23 |
| 29 Oct 2026, 09:28 | 2,557 | +18 |
| 26 Oct 2026, 02:17 | 2,539 | -1 |
| 23 Oct 2026, 00:57 | 2,540 | +4 |
| 20 Oct 2026, 00:46 | 2,536 | +17 |
| 16 Oct 2026, 23:36 | 2,519 | +8 |
| 14 Oct 2026, 08:16 | 2,511 | +5 |
| 10 Oct 2026, 18:22 | 2,506 | +11 |
| 5 Oct 2026, 00:56 | 2,495 | -10 |
| 25 Sept 2026, 16:58 | 2,505 | -8 |
| 17 Sept 2026, 01:01 | 2,513 | +5 |
| 13 Sept 2026, 11:59 | 2,508 | -1 |
| 9 Sept 2026, 14:39 | 2,509 | -8 |
| 4 Sept 2026, 01:20 | 2,517 | +4 |
| 31 Aug 2026, 19:53 | 2,513 | -4 |
| 28 Aug 2026, 12:04 | 2,517 | -1 |
| 25 Aug 2026, 01:45 | 2,518 | first reading |
10 posts held, back to 8 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 1 page 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 10 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
#群友投稿：没想到最终我也成了人家的笑话，以前我还嘲笑别人没找到真爱，现在才明白其实是我自己太傻 最开始跟她在一起时，发现了很多令人吃惊的事情：她同时交往多个男人，我知道的就有四个；她有偷渡到中国给人生娃然后被抓遣返的黑历史，孩子现在都几岁了，还有和人发生关系被拍视频，也是怪自己心软，听她说的，我选择了原谅和理解，但她狗改不了吃屎，后来还是被发现了，她给我跪着哭，说家里有各种困难，我最后又心软了。 我们一起三年多了，家里也不知道去过多少次，刚好今年又是大检查，收入明显减少，我以为是钱的问题，结果发现她早就用她妹妹的手机偷偷跟别人聊天，因为知道我喜欢看手机。这两个月来家里多次发现她不在，前几天回家，她告诉我她老爸吸毒进了监狱，回去卖地，还找人要钱，种种借口说是有事要处理，实际上是去见别的男人。她还喜欢吵架闹离开，实际上却是去见别的男人。有好几次我去她家找她，人都找不到。 她总说家里有事要处理，所以见不了我，实际上都是在和别的…
#网友投稿：东方明珠KTV，啊瑞，今天把事情说清楚。本来不想曝光，但你这个态度，真的让我忍不了。 本人于2026年4月26日，经朋友介绍入职东方明珠KTV，位置就在海滨一号正对面、华泽国际赌场5楼。入职后一直在外面跑客户、发名片、订房，业绩也做得不错。 但工作期间，公司经常出现客人到了却没有陪酒人员、人迟迟不到位的情况。营销一直在外面跑客户，最后因为内部服务和人员安排导致客人流失，却经常变成营销的问题。 重点说6月28号这件事。 当天，我接了一个团建房，客人点了20多个妹子，后来打K转场。店长当时已经和客人沟通过，越南女孩子打K需要另外收费，客人也同意了。 结果主客进去打一条K后睡着，醒来后不认可打K费用。当天我一直陪着客人处理到下午4点左右，最后客人把唱歌、喝酒和陪酒人员费用全部结清，打K部分只愿意买1200元。 我当时担心后续处理不清楚，所以找啊瑞沟通。他让我尽力争取，之后明确告诉我：收到的1200元交前台，剩下…
#imToken：爆设计缺陷，黑客仅需数小时即可暴力破解用户助记词、盗取资产 摘要：imToken 作为全球用户量领先的去中心化加密钱包，其助记词生成机制存在两处致命设计缺陷——底层伪随机数生成器（PRNG）种子空间仅 48 位、BIP39 单词表仅 2048 个词汇。两者叠加后，攻击者可在数小时内从哈希反推出原始助记词，完全控制钱包资产。 事件概述：imToken创立于 2016 年，截至 2025 年全球累计注册用户已超 3000 万，是亚太地区用户量最大的去中心化钱包之一。其核心卖点"私钥由用户本地管理、平台无法代持"意味着：只要助记词（Mnemonic Seed）确定，钱包地址和资产归属就完全确定。 然而我们发现，imToken 在 Android 平台上生成助记词时使用了 java.util.Random 作为伪随机数生成器。该类的内部种子仅为 48 位（6 字节），且其算法是确定性的线性同余生成器（LCG）。这…
警方端掉两处电诈窝点二十多人落网 严打电诈这事终于又有进展了。警方集中精锐力量直接重拳出击，成功端掉两处电信网络诈骗窝点，一口气抓了二十多名涉案人员。 这帮家伙搞网络引流坑害普通人，现在诈骗链条被彻底斩断，违法犯罪被狠狠收拾，群众的钱袋子也总算能安心点了。 反诈就得零容忍，任何电信诈骗到头来都得被严惩。大家平时提高警惕，别贪小便宜，看到可疑的赶紧举报，一起把这些骗子往死里打，守护自己的平安。
潜逃5年电诈金主被押回国 科左后旗公安局8月6日通报，7月25日，在公安部、内蒙古自治区公安厅统一指挥下，当地警方成功把潜逃境外整整五年的特大跨境电信诈骗团伙二号主犯郑某发押解回国。这是科左后旗首起电诈红色通报案件，也是“拔钉”专项行动的重要战果。 2021年4月，科左后旗警方破获一起特大跨境电诈案，打掉一条完整犯罪链条，先后抓了25名主要嫌疑人，串并全国30多起同类案件。当时团伙二号人物郑某发和另外两名成员直接畏罪跑到了境外。 为了把这些境外骨干彻底铲掉，2022年7月公安部对郑某发申请了国际刑警红色通报，8月又把他和另外两人列为“拔钉”重点缉捕对象。办案单位一直死盯线索，另外两名逃犯先后被抓回来，就剩郑某发还在外面死扛，死活不投案。 靠着国际警务协作，境外执法部门终于把他逮住并移交我方。现在郑某发已被依法刑事拘留，后续审讯和深挖工作正在推进。这家伙躲了五年还是没跑掉，该来的迟早会来。
报告称逾1.36万名各国公民仍被困泰缅边境电诈园区 人权组织“打击人口贩运受害者援助民营网络”8月6日报告显示，目前仍有超过13,670人被困于泰缅边境的网络诈骗园区中。 报告指出，克伦边防军（BGF/KNA）控制区约拘禁超8,370人；民主克伦仁爱军（DKBA）控制区约拘禁5,300人。受害者来自中国大陆、中国台湾地区、东南亚、南亚、欧洲及非洲等几十个国家和地区。 据透露，部分菲律宾籍受害者在转运期间秘密收集了园区照片、定位及人员名单，积极协助调取证据及救援行动，但仍有大量人员被困或失联。 ✅ 中文搜索：@mbhl6 ☎️ 投稿爆料：@mcy158 💬 失联导航: @ddc1588
越南女子以续贷为名骗超140亿越盾 8月8日，越南广义省公安通报，警方已经对39岁的Nguyễn Thị Hằng（阮氏姮）依法立案，并执行逮捕、临时羁押措施，调查她涉嫌“诈骗侵占财产”的案子。 初步调查显示，因为要还债和满足自己花销，阮氏姮对外声称自己在筹集资金，帮客户办银行贷款续贷、资金周转。为了让人信，她承诺给高利息，还保证短期内把本金和利息还回来。 一开始她按约定给出资人付本金和利息，慢慢取得了信任，不少人继续把钱交给她。 可是筹集的金额越来越多后，她并没有把后续的钱用在所谓的银行续贷上，而是拿新收到的钱去还之前的债，同时自己花掉。债务越滚越大，最后还不上了。 警方调查认定，她已经从多名受害人那里骗走超过140亿越盾，大约人民币390万元。 警方说，调查过程中阮氏姮不承认犯罪。不过根据收集到的资料和证据，调查机关认为已经有充分依据，以“诈骗侵占财产罪”对她提起刑事诉讼并采取羁押措施。 目前案件还在进一步调查…
泰国军方公开边境缴获证据：诈骗园区搭建多国仿冒警局、银行模拟场景 泰国军方对外公开展示从柬泰边境O’Smach园区缴获的海量物证。诈骗窝点内部专门搭建仿冒多国警察局、银行办公场景，伪造证件、话术脚本、上万张匿名SIM卡一应俱全。 诈骗分子伪装各国执法人员实施恐吓诈骗，专门针对全球各国受害者。该园区曾关押数千被胁迫务工人员，相关物证已经移交多国警方做案件取证。 ✅ 中文搜索：@mbhl6 ☎️ 投稿爆料：@mcy158 💬 失联导航: @ddc1588
园区清空后犯罪问题开始向外扩散 最近刷新闻看到不少绑架、抢劫、盗U这类事儿，仔细一想，这些现象好像也反映出一个现实变化。 各地持续打击涉诈和非法园区，大量人员被抓、遣返，部分相关产业链被迫散了。但与此同时，一些隐藏的问题也慢慢冒了出来。 他们跑出来后面临拖欠工资、没人管的情况；为了活下去就铤而走险，转向绑架、抢劫这些违法犯罪；还有一些所谓“技术人员”钻漏洞搞盗U、黑产攻击。 以前园区还在的时候，虽然本身就是非法的，但某种程度上形成了一种封闭管理的环境，很多矛盾和风险被压在内部。现在园区被清理了，原本藏着的问题开始往外扩散。 正所谓上有政策下有对策，犯罪模式也会跟着环境变来变去。这种变化让人忍不住联想到香港电影里的情节：以前某些灰色势力虽然违法，但内部有所谓的“规则”和“秩序”，有人管事，有人分利益，上下之间维持着一种畸形的平衡。一旦这套体系突然垮了，原本被压住的问题就可能迅速失控，各种矛盾集中爆发。 打击行动把他们的…
跟随公司三年还是把我提成黑了 本人跟着公司干了三年，从大其力到特区，再到KK园区。后来KK被冲了，又转到669园区。 那时候天天顶着子弹炮弹敲键盘，实在受不了，就偷渡到柬埔寨菩萨。今年3月，在菩萨又偷渡到三佛塔。 公司安排的路线早就暴了，我们在拜林被泰国警察抓住，关在移民局整整三个月，公司一分钱都没出。后来被遣送回国，本来回去也没啥大事，结果被公司的人给指认了。 我请律师又找关系，花了大概10万人民币才出来。找公司领导要2到3月份的工资，大约8000U，结果死活不给。 我个人和带组业绩都超过100万U了。东南亚这地方真他妈没人情味，既然你们这么无情，就别怪我无义。 兄弟们，好好干，多赚点吧。回来以后，用钱的地方多着了。
Showing the 10 most recent of 10 posts we hold for @mbhl1. 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.
Named by 2 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.
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.
This channel appears in 40 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.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“东南亚今日头条.” (@mbhl1), 2,608 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/mbhl1.
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.