Channel
@ML_188
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
681subscribers
-248 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003044032136 |
|---|---|
| Type | Channel |
| Username | @ML_188 |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/ML_188 |
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 11 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|---|
| @yinni977/45626 Aug 2026, 09:43 UTC | @ML_188/4743 · this entry6 Aug 2026, 10:01 UTC | 1.00 | 17 minutes |
| @yinni977/45746 Aug 2026, 10:00 UTC | @ML_188/4755 · this entry6 Aug 2026, 10:01 UTC | 1.00 | under a minute |
| @yinni977/45756 Aug 2026, 10:00 UTC | @ML_188/4756 · this entry6 Aug 2026, 10:01 UTC | 1.00 | under a minute |
| @yinni977/45766 Aug 2026, 10:00 UTC | @ML_188/4757 · this entry6 Aug 2026, 10:01 UTC | 1.00 | under a minute |
| @yinni977/45806 Aug 2026, 10:00 UTC | @ML_188/4761 · this entry6 Aug 2026, 10:01 UTC | 1.00 | under a minute |
| @yinni977/45816 Aug 2026, 10:00 UTC | @ML_188/4762 · this entry6 Aug 2026, 10:01 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @yinni977 | 20 (6/8 hand-verifiable sample passed) | 1.00 | under a minute | @yinni977 (20–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. 20 of the 20 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 20 comparable posts for this entry, running 6 August 2026 to 6 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 @yinni977. 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 |
|---|---|---|
| 25 Sept 2026, 09:20 | 681 | -132 |
| 12 Sept 2026, 23:18 | 813 | -77 |
| 4 Sept 2026, 15:40 | 890 | -100 |
| 29 Aug 2026, 01:04 | 990 | -3 |
| 22 Aug 2026, 07:29 | 993 | +38 |
| 14 Aug 2026, 03:38 | 955 | +26 |
| 6 Aug 2026, 19:50 | 929 | no change |
| 6 Aug 2026, 19:49 | 929 | first reading |
20 posts held, back to 6 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
印尼雅加达女商贩遭盗包 丢失巨款押金 8月4日晚间，印尼雅加达西区岑卡伦地区发生一起盗窃案件，香烟销售员苏西财物被盗，损失高达数百万印尼盾，相关监控画面在社交平台快速传播引发热议。 据受害者侄女普特里介绍，当晚8时左右，苏西前往商铺收款，将摩托车停在店门口，短暂离开期间，车上挎包遭人偷走。包内装有多包香烟及300万印尼盾营业押金，发现财物失窃后，家境拮据的苏西悲痛落泪。据悉，受害者家中有初中生子女需要照料，丈夫靠打零工维生，本就窘迫的家庭经济雪上加霜。 现场监控清晰记录作案过程，嫌疑人身穿连帽衫、头戴帽子，趁无人留意迅速盗走挎包后逃离。目前受害者一方已正式报警。当地警局刑事调查部门负责人帕尔曼仍在审核报案材料，核实案件细节，后续将依法开展调查取证工作。
雪州女教师校内上吊身亡 马来西亚雪州乌鲁雪兰莪一所学校传出不幸消息，一名印裔女教师被发现在教师办公室内上吊，送医抢救后宣告不治。警方今天上午7时15分接到报案，马上赶到现场展开调查。 乌雪警区主任玛尼马兰警监证实，死者被紧急送往新古毛医院，但到达急诊室时已经没有生命迹象。经法医解剖，死因确认为上吊，警方目前将案件列为猝死案处理。 这起悲剧让当地教育界很震惊，校方和家属都暂时没有公开表态，案件细节还在进一步厘清中。
印尼破获非法劳务贩运案,105名女工被输送至利比亚遭剥削 警方通报，8月4日侦破一起跨国人口贩运案，两名嫌疑人在2023至2026年间，非法输送至少105名印尼女工前往利比亚从事家政工作。历经多批次输送，部分人员提前遣返回国，均已接受核查并配合取证。 目前仍有41名务工人员滞留利比亚，警方正联动各方协调接返。经调查暂未发现相关性暴力案件，后续警方将持续跟进滞留人员安置与案件侦办工作。
公路现离谱六连减速带！官方造假辟谣败露后火速停职官员 8月4日，印度拉贾斯坦邦25号公路的六连巨型减速带视频走红，密集排布如同路障陷阱，所有车辆只能低速缓慢通行，引发网友热议。印度国家公路管理局起初辩称，减速带是应村民诉求修建，用于保障道路安全。 该局为洗白争议，配发虚假路况照片糊弄舆论，被媒体揭穿照片取景地不符、涉嫌篡改事实。舆论哗然后，官方紧急改口，火速暂停涉事项目经理职务，以此平息风波。
马来惯犯持刀袭警被击毙 马来西亚霹雳州警方最近在巴都古劳搞抓捕，一名有一堆前科的涉毒惯犯持刀袭警，最后被警方开枪制服，送医后不治身亡。 事发当天早上8点20分，警方接到线报，知道这货藏在当地一个果园小屋里，马上派人过去抓。到了现场亮明身份准备动手时，这家伙突然掏出砍刀就往警员身上冲。 警方为了自保只能开枪，打中他腿部。人倒地了还不老实，继续拼命反抗搏斗，警方好不容易才把刀夺下来。 嫌疑人随后被送去医院抢救，上午9点20分宣告死亡。一查发现这货身上背着10项前科，全是刑事和毒品案子，6月还持刀砍伤过两名警员后一直潜逃。尸检结果还没出来。
印尼南加里曼丹警方查获大量毒品 疑关联知名逃犯犯罪网络 2026 年 8 月 4 日周二，南加里曼丹省警方在班贾尔巴鲁召开新闻发布会，省警察总监罗西扬托・尤达・赫尔马万对外通报，警方成功缴获数百公斤冰毒以及数百粒摇头丸，查获数量巨大。 据警方介绍，这批涉案毒品来源可疑，经初步核查，相关证据线索被怀疑与在逃人员弗雷迪・普拉塔马的犯罪网络存在关联。弗雷迪・普拉塔马是当地臭名昭著的逃犯，长期涉及毒品相关违法犯罪活动。 目前，警方正对这批毒品的来源、流向以及背后涉案网络展开深入调查，重点追查与该逃犯相关的犯罪链条，后续将根据调查进展依法推进相关案件办理，全力打击涉毒违法犯罪行为。
马来警方锁定机场安检涉运毒 马来西亚警方日前证实，已经锁定一名30岁的吉隆坡国际机场安检人员，怀疑这家伙跟马航副机长涉嫌跨国运毒案有关，现在正进一步调查，不排除直接抓人。 涉案副机长莫哈末·绍菲·奥斯曼之前开着马航MH727从吉隆坡飞雅加达，落地苏加诺-哈达国际机场后被印尼海关查出行李里藏了约25公斤摇头丸（MDMA），尿检也呈阳性。 马来西亚武吉阿曼肃毒局局长侯赛因·奥马尔·汗说，警方确认这名机场安检人员涉嫌帮忙，接下来会传唤他协助调查，一旦证据够了就依法逮捕。 警方指出，吉隆坡国际机场有四级安检机制，正常情况下旅客过扫描系统，没异常就直接放行；要是发现可疑东西，才会进更严的二级、三级检查。现在警方在查这些毒品到底怎么绕过安检的，是不是有内部人开绿灯。 目前马来西亚警方正跟印尼警方密切合作，追查毒品来源和背后的跨国贩毒网络，还打算在拿到印尼许可后派人过去，对副机长再好好问问。
#马来西亚资讯：柔佛河中惊现被捆绑浮尸 39岁华裔商人遭弃尸河道 3名嫌疑人被捕 援引马媒报道：8月3日12时30分，柔佛州峇株巴辖巴力拉惹镇，当地渔民在丹绒森宝隆河发现河面上有一团不明漂浮物，远看无法辨识具体物体，起初误以为是动物尸体，靠近查看后才确认是一具男性浮尸，随即向警方报案。 接报后，当地警方迅速赶赴现场，开展现场勘验、区域封锁等处置工作。随着调查推进，柔佛州副警察总长胡传发对外通报了该案初步详情：遇难者遗体被渔网层层包裹，手脚遭胶带捆绑，躯体多处存在伤痕。 7月29日，遇难者的妻子曾前往新山慕蒂亚拉里尼警局报案，报称丈夫失踪，该案彼时按失踪人口案件处理。此次浮尸事件发生后，家属到场，结合遗体的衣着及随身物品进行辨认，确认死者正是此前失踪的男子。据悉，遇难者是当地一名39岁华裔商人。 案件侦办过程中，警方锁定3名年龄介于26至40岁的本地男子，并将其全部抓获归案。经查，三名嫌疑人当中有两人存有犯罪及吸Du前科，…
公职人员虚报住房补贴致国家损失36亿印尼盾 8月5日，印尼波诺罗戈地区检察官办公室官宣侦破一起重大贪腐案件。当地人民民主革命委员会秘书处财务部门负责人被列为涉案嫌疑人，涉嫌在2023至2026年间违规操作议员住房补贴项目，恶意篡改补贴核算标准，套取公共资金。 该案最终造成国家财政损失高达36亿印尼盾。目前嫌疑人已被控制，办案团队正深挖资金流向、彻查全链条涉案人员，持续推进案件侦办工作。
#马来西亚新闻：第三届教科文组织创意城市网络美食之都年会4日在古晋开幕，恰逢砂拉越总理阿邦佐哈里76岁生日，现场两度响起生日歌送上祝福。 本届大会汇集25国近200名代表，围绕美食文旅与城市可持续发展展开研讨交流。作为古晋获评美食之都后的重磅国际活动，此次年会借美食文化搭建跨国合作平台，展示当地多元饮食特色，助力提升砂拉越国际知名度，为城市间的文化交流与可持续发展注入新活力。
#企图运87公斤冰毒到大马3大马人在合艾火车站被捕 3名大马公民在行李箱和背包内藏匿87公斤冰毒，试图将毒品运送进入马来西亚，昨日在泰国合艾被当地警方逮捕。 这三名嫌犯是在乘坐火车从泰国曼谷前往合艾，在三个拉杆行李箱和三个双肩背包中，发现了87公斤的晶体脱氧麻黄碱（俗称冰毒），价值约430万令吉。 初步调查显示，这三人受雇将冰毒运送给马来西亚贩毒集团，每人分别获得8000令吉，作为将毒品运送至指定地点的报酬。
#吉隆坡国际机场1号航站楼升级电召车设施 主要引入了车牌辨识系统、自助服务终端机以及专属乘客候车区。每辆进入主航站楼接客的电召车须缴付3令吉服务费，停留超过10分钟将面临罚款。 1.设施升级重点 车牌辨识系统：与乘客资讯显示系统全面整合。 自助服务终端机：方便乘客快速办理相关乘车手续。 专属候车区：提供更有序的接载空间。 2.收费与规则 入场服务费：每辆授权电召车须缴付 3令吉。 3.时间限制：车辆停留超过 10分钟 将被罚款。
Showing the 12 most recent of 20 posts we hold for @ML_188. 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 28 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. The 21 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“马来新闻 🪻” (@ML_188), 681 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/ML_188.
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.