Channel
@ML465
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
10,103subscribers
+5 since we began measuring on 10 November 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003981742942 |
|---|---|
| Type | Channel |
| Username | @ML465 |
| Description | 📢 聚焦缅甸各地区，关注最新新闻动态。 📰 缅甸新闻｜地区资讯｜热点事件 📍 缅北地区｜老街｜小勐拉｜佤邦 🌆 仰光｜曼德勒｜内比都及周边地区 🔎 关注社会动态，追踪热点事件，分享值得关注的地区资讯。 坚持客观、真实、及时的信息发布，让更多人了解缅甸各地最新消息。 👑在线客服： @YY674 ————————————- ✈️：投稿 @HQ898 |
| Created | Between 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 November 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/ML465 |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 November 2026 and assigned it the closest of 31 fixed categories, at 72% 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 2 other registered channels. This entry also sits inside a group of 3 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 |
|---|---|---|---|
| @ML465/121 · this entry9 Nov 2026, 14:36 UTC | @RG898/585410 Nov 2026, 07:58 UTC | 1.00 | 17 hours |
| @ML465/130 · this entry10 Nov 2026, 03:25 UTC | @RG898/586411 Nov 2026, 04:58 UTC | 1.00 | 26 hours |
| @ML465/147 · this entry10 Nov 2026, 11:25 UTC | @RG898/587611 Nov 2026, 10:58 UTC | 1.00 | 24 hours |
| @ML465/175 · this entry11 Nov 2026, 07:19 UTC | @RG898/589212 Nov 2026, 02:58 UTC | 1.00 | 20 hours |
| @ML465/186 · this entry11 Nov 2026, 16:06 UTC | @RG898/591713 Nov 2026, 05:58 UTC | 1.00 | 38 hours |
| @ML465/199 · this entry12 Nov 2026, 05:54 UTC | @RG898/592113 Nov 2026, 08:58 UTC | 1.00 | 27 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @RG898 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 25 hours | this entry (6–0) |
| @qbj7777 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 2.3 hours | @qbj7777 (4–1) |
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. 4 of the 4 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 27 comparable posts for this entry, running 9 November 2026 to 13 November 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 3 channels, the one whose matching posts we hold earliest is @ML465 — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_source, last confirmed 14 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 3 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 |
|---|---|---|
| 13 Nov 2026, 12:46 | 10,103 | +3 |
| 10 Nov 2026, 21:51 | 10,100 | +2 |
| 10 Nov 2026, 07:22 | 10,098 | first reading |
38 posts held, back to 9 November 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 10 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 38 (9 November 2026 – 14 November 2026) |
| Views total | 335 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 23:45 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.
Lifetime counters from Telegram’s own channel header, read 14 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 6 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.
Telegram’s own ‘edited’ marker: 0 of 38 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
⚡️⚡️⚡️⚡️ 好运加持太强了！命中之后盈利直接落袋✨✨✨ 心情直接拉满，先开心一下，别忘了合理安排节奏！ 主营：😀🇻🇳🇻🇳🇻🇳🇻🇳😀🇻🇳🇻🇳🇻🇳😀🇻🇳🇻🇳🇻🇳 支持：😋USDT| 😋支付宝 | 😋微信 | 😀银行卡|😋 KBZ 😀😀😀😀 官方网址: www.22201522.com 官方网址: www.33201533.com 诚信第一 赔付效率第一 资金干净 安全有保障 ！ 平台100%靠谱 - 不贪小便宜 ！ 😀😀😀😀 🥰客服飞机：@YY674 🔈官方频道：@YY420 ➡️点击观看中文导航 ⬅️ 首次充值有赠送10%彩金哦 电脑可以直接点击链接， 手机请复制到浏览器中打开注册登录下载APP ❗️❗️❗️❗️❗️❗️❗️❗️❗️ 充值 🟠🔴🔴🔴到账 🟠🟠🔴🔴 充值 🟠🔴🔴🔴到账 🟠🟠🔴🔴 充值 🟠🔴🔴🔴🔴到账 🟠🟠🔴🔴🔴永久有效 #缅甸小勐拉 #环球娱乐 #实体平台 #保证资金安全放心娱乐
#网友投稿 安溪蓬莱镇“黑盘总”现位于马来西亚，员工二三十人中半数无护照。 公司洗脑代理，报表造假，普遍亏损，月入两三亿日元，专骗代理，以福利为诱饵后拒不认账，并威胁代理。被控员工多为南安人，部分照片已报泉州公安。 该公司先在西港“老皇乐绿巨人”招人，后迁至柬埔寨“七星海”。借安全名义搬迁时，利用洗脑诱导员工发展代理，半年招百余人。当时公司尚未臭名昭著，员工多被洗脑跟随。 客服经理思琪（安溪官桥善坛村人，姓钟XX）尖酸刻薄，刁难新人，去年曾有人持菜刀上门警告。歌手"18"为公司管理，抽烟者“摩羯”（张XX）为老板。内部管理及员工照片已送交警方。 目前该团伙在马来西亚继续猖狂诈骗，还声称回家花钱就能解决！
#频道互推 #相似推荐 ------------------------------ 📢 妈妈 母子 乱伦 新闻 📢 合肥女奴库 📢 吃瓜/大曝光 📢 吃瓜小队🍉日更 📢 缅北吃瓜社 📢 缅北老街吃瓜中心 📢 娱乐新闻|吃瓜黑料 📢 东南亚大黑料吃瓜 📢 东南亚华人大事件 📢 东南亚海外新闻曝光 ------------------------------ 🤝 加入互推 · 获得曝光，赚邀请奖励
#网友曝光 此女子本人23年在特区认识她，她跟我说她弟弟赌博输了好几十万要我借5万给她，把她弟弟救出来，出于好心就借给她了，后面我回国了给了一个微信号给她，她说她会加我微信并且尽快还给我，直到26年10月也没有加我。可是缘分就是这么的造人，让我们10月又在特区碰到了，我就问他为什么不加我微信，她又是一顿卖惨，后面我知道她是故意不想还我，我随便找了一个借口试探一下她，让她先还1万，谁知道她这么没格局把我拉黑了。她本人现在在特区水街《夜来香会所》做小姐兼职做扶手，估计上班是假，套客人是真，请大家不要上当受骗
#网友投稿 有看见这女的帮我扇她几个耳光 被御龙湾物业赶出来 就把头发剪成男的怕被认出来，她骗御龙湾那边3万多人民币，6号地2.5万 大家注意了这女的，不是知道是那里人，小小年纪心狠手辣，只要是个公🐶都睡，以前在御龙湾一起工作，她从老街来御龙湾路费是3万人民币，班都不好好上天天出去找这个男的那个男的，后来被公司开除，她没钱赔付，去找御龙湾物业说是自己被卖进去的 聊天记录都有，连我包里放的6万缅币她都偷走，后来御龙湾知道她是骗子把她的照片贴在大门口，我们是搬出去才知道的，明知道别人有老婆有女朋友也敢去骚扰，后来她从御龙湾被赶出去，又去妙瓦底跟了个男的，说那男的有老婆害怕他老婆打她，跟我说有多可怜说自己没钱吃饭，每天不敢睡觉 还说那个男的是个当官的给她多少钱多少钱，我跟几个同事去妙瓦底，她还让我帮她路费说去找我们玩，当时我们几个也不同意，就没让她来，天天跟我诉苦她有多可怜，然后看她说害怕他男朋友的老婆打她 就叫她来我这里上…
#网友爆料 此人叫赵顺澎 朋友在柬埔寨戈公被警方抓捕， 对方声称有渠道可以帮忙处理，双方谈妥3万美元， 承诺负责把人弄出来，办不成就按约定退款， 我们基于信任支付了费用 对方多次作出保证，如今事情没有解决，退款也没有兑现，人反而联系不上了，机会已经给你无数次，最后再提醒你，跑得了和尚，跑不了庙
从容出牌，静待反转！局势领先时稳住节奏，遇到变化时及时调整思路。每一场牌局都是一次新的考验，带上你的专注与勇气，迎接充满悬念的精彩对决。 💪🦾🖕✍🙏🫵🦶🦵🦿💄 永胜国际高爆大奖：多款热门PG电子全线高爆，巨奖连环不断。 支持微信 支付宝 USDT KBZ 银行卡充提。 日赢出款无上限，保证您的资金安全 。 😋😋😋😋😋 🇧🇱上下分联系: @YY674 🔍双向客服: @YY674_bot 邀请码：8BE8CZZ 官方网址： yongsheng2026.com APP下载： app.yongsheng2026.com #麻将胡了 #pg #体育 #赏金大决定
#网友投稿 渣女， 缅甸名字叫 နန်းခင်နုနွယ်，公司名字叫 #安娜。 她本人现在在776/771山上园区上班，做刷群。跟我谈了三年恋爱，之前她长得好胖，我都不嫌弃，一直给她幸福快乐的。要金子、要手机，我都给她买的。 还有去年亚太跑路的时候，也看着可怜她，还带她一起回去的。 然后去柬埔寨上班，遇到中国老幺，肯定是被中国人放进去了吧？还继续骗我感情和我的钱。 她自己跟中国人玩了后，传到爱死病，说什么我传给她的。你他妈的，跟老子不在一起一年了，要是我有病，应该早就死了吧？动不动就说让我赔偿她的生命。你自己骚了，被老幺玩死的人。 本来不想曝光的，想让网友的朋友们多注意这个s货。要是还来一直烦我，我就发你的做爱视频给大家看。 最后警告你一次，不想再丢脸就不要来烦你爹，我是不会客气谁的，cnm！ PS：聊天记录已经发给小编，确认有证据，
#频道互推 #相似推荐 ------------------------------ 📢 柬埔寨新闻曝光（吃瓜） 📢 东南亚吃瓜事件🍉 🅥 📢 一线吃瓜网 📢 全网新闻曝光-吃瓜 📢 世界曝光悬赏爆料 吃瓜 东南亚 📢 东南亚曝光新闻【78.com独家冠名】 📢 全球吃瓜内容杂志社 📢 东南亚华人事件曝光 📢 东南亚曝光全网 📢 line🟢TK🟣IG 🟠FB【推特】 ------------------------------ 🤝 加入互推 · 获得曝光，赚邀请奖励
#网友投稿 视频中绑匪为缅甸木姐人林飞，长期诱骗绑架勒索敲诈中国人，至少50人以上的家属均被他敲诈过。图片中为他目前扣押中国人及虐待证明 现场关人的电话：09674887017、09662547214 经常用的车子是3M-5719黑色皇冠、5058牌照尾号黑色皇冠、8899牌照白色皇冠 被他勒索交过赎金的名字有向海江、谢德祥、王昱皓、代朝燕、王鹏超、林嘉艺、王武、艾子豪、罗广鑫、黄凯祥、李佳恒、张春浩、王大鹏、陈建林、郝志杰、陈郑、李俊咖、苗武庆、吴凤波、李厚超、吴鹏程、吴润峰、秦栎茗、陆凯，童宽、鹏源义、席进财等等共计50人以上。以上人员已经全部在联系家属并提供绑匪真人视频，受害者家属请联名向中国警方施压，务必严惩境外绑匪 注：绑匪同谋和操作者也是木姐人真实名字叫：岳永开，小名压柱。飞机号小柒。同谋堂哥飞机名好好钓鱼 ➡️点击观看中文导航 ⬅️
#网友爆料 #欠钱不还 名字 （何志祥，小何 ，飞机名字，飞 ） 之前因为都是朋友让他欠着，后面是一直在找理由拖着不还 ，我也没有要求他一次性还完，一个月能给多少先给着，但他就是不还 每次问他，都找各种理由，还说生病，上不了班，结果后面我发现，他不是生病，也不是没有钱，就是不想还，现在直接不回消息 这次是给你一个警告 ，在不还钱就直接曝光你照片
#网友投稿 本人与老乡吃饭时，认识了柬埔寨西港独立大道长沙杨裕兴饭店老板，化名强别（许文强） 一个地方的老乡，经常照顾他的生意，去店里吃饭，还经常帮他打打广告、介绍生意。 发表这篇文章之前，朋友告诉我，还在给他的店送餐。当时聊起这件事，正在他店里请客吃饭，身边的朋友都听到了。他说认识老板，和老板是兄弟，有面子，还说菲律宾那里好赚钱，可以过去看看。 当时听信了他的一面之言，考虑到他是做生意的，有自己的店，而且又是一个地方的老乡，所以并没有怀疑。 到了菲律宾后，对方安排人接待，然后说帮忙办理签证，随后收走了护照，开车直接把本人带到了园区，进了盘口。想出去时，保安也不肯放行，说要得到Boss同意。这时才发现，很多事情都不一样了。 （同时，中间发生了很多倒霉、气人的事情，就省略吧。）也导致手机、行李什么都没有了。所以，等处理好换洗衣服与手机，重新登录所有社交账号、联系朋友后，结果签证也逾期了。 后面联系他本人，说自己要走，如果…
Showing the 12 most recent of 38 posts we hold for @ML465. 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.
Named by 1 registered channel — 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.
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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“缅甸地区曝光｜缅甸事件追踪｜热点新闻” (@ML465), 10,103 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/ML465.
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.