Channel
@DNYXWWBG
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
7,349subscribers
+1,067 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1004415360711 |
|---|---|
| Type | Channel |
| Username | @DNYXWWBG |
| Description | 东南亚新闻网-东南亚大小事-曝光骗子-吃瓜群众投稿,欢迎投稿，感谢广告赞助！赞助唯一联系方式 @DNYTG68 |
| Created | Between 1 June 2026 and 7 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/DNYXWWBG |
Other / unclassifiable — 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 49% 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 |
|---|---|---|---|
| @DNYXWWBG/450 · this entry7 Aug 2026, 15:30 UTC | @wqbysc98/593647 Aug 2026, 15:51 UTC | 1.00 | 20 minutes |
| @DNYXWWBG/451 · this entry7 Aug 2026, 15:30 UTC | @wqbysc98/593657 Aug 2026, 15:51 UTC | 1.00 | 20 minutes |
| @DNYXWWBG/454 · this entry7 Aug 2026, 15:30 UTC | @wqbysc98/593687 Aug 2026, 15:51 UTC | 1.00 | 20 minutes |
| @DNYXWWBG/456 · this entry7 Aug 2026, 15:30 UTC | @wqbysc98/593707 Aug 2026, 15:51 UTC | 1.00 | 20 minutes |
| @DNYXWWBG/459 · this entry7 Aug 2026, 15:30 UTC | @wqbysc98/593737 Aug 2026, 15:51 UTC | 1.00 | 20 minutes |
| @DNYXWWBG/460 · this entry7 Aug 2026, 15:30 UTC | @wqbysc98/593747 Aug 2026, 15:51 UTC | 1.00 | 20 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @wqbysc98 | 7 (7/7 hand-verifiable sample passed) | 1.00 | 20 minutes | this entry (7–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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 16 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 2, the earliest publisher we hold is @DNYXWWBG — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key 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 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 |
|---|---|---|
| 10 Aug 2026, 23:16 | 7,349 | +1,065 |
| 7 Aug 2026, 19:11 | 6,284 | +2 |
| 7 Aug 2026, 10:15 | 6,282 | first reading |
78 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 10 pagesof 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. It is computed over the 1 of 78 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 78 (7 August 2026 – 12 August 2026) |
| Views total | 385 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 17:41 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 12 August 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 8 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 1 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 1reactions 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 7 August 2026 to 12 August 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.
#网友曝光 我是一名退伍军人，我叫 #江秦飞。刚开始在 #柬埔寨 赌场给老板看赌场做保镖。 今天我就说说怎么被一个四川狗骗到妙瓦迪的。刚开始你说你一个人不敢去缅甸妙瓦迪，叫我和你一起，两个人有伴过去，有工作机会，工资和待遇都说得特别好。我当时跟你说，我不会敲键盘也不想敲键盘。 到了那边以后，情况完全不是你之前说的那样。过来公司也不错，你做了组长，我给你做组员，做出的业绩你也拿了提成。结果我开出来的客户你让我给本地人开，还从我这里要钱，没给你钱还甩脸子。 我想问问你，没有你，难道我就开不了客户吗？你自己想想，开始过来的时候你用的买东西的钱什么不是我出的？你还和别人说我怎么忘恩负义。我今天就直接实名曝光，要死我们就一起死！
#巴基斯坦：狗推被端后续，昨天中午 12 通知说今天必须把所有人都放出来，下午6点又来了一波警察还有一个大巴车，又开始查，说 7 点就能出来，到现在也没一个人出去。 大楼法人是 #马来西亚 华人，也被控制在楼里面。目前大楼里面最少有500-1000名狗推。
#妙瓦底 #遣返6名涉电诈外国公民 日期： 2026年8月11日 8月11日，#缅甸 通过缅泰第二友谊大桥，将涉嫌参与妙瓦底-水沟谷地区网络诈骗和犯罪活动的 6名外国公民 遣返回国。 人员构成： 埃塞俄比亚2人、利比里亚1人、布隆迪1人、乌干达1人、多哥1人。整体数据（2025年1月30日至2026年8月11日）： 累计查获非法入境外国人：14,740人 已累计遣返：13,820人 待遣返总计：920人（其中713人正接受缅方法律制裁，207人正准备遣返）。
⚠️ #防骗提醒公示 #在此提醒各位在东南亚从事业务的朋友：#即使是通过熟人介绍的“#靠谱”资源，也务必保持高度警惕，做好风险控制。 事情经过简述： 2026年7月12日，本人通过朋友小白介绍，与对方（飞机名：佛跳墙，账号：@ftq168168，自称“老家哥哥”）对接测试蓝标号业务。 对方声称资源稳定、可按期交付，本人基于对介绍人小白的信任，预付了10个蓝标号的款项2800U给他老家哥哥，约定7月20日前完成交付。 实际情况： 7月20日未按时交付，对方以“风控”为由要求延期； 7月25日仍无任何进展； 本人提出若无法交付则退还剩余款项，对方同意也约定第二天退回后随即失联； 介绍人（小白）前期一直跟进联系他老家这个哥哥，但是也是没有任何退款进展，目前小白也开始回避，应该是清楚他这个哥哥吃定这个预付款钱了，也没有再回复我消息。 截至今日（8月11日），对方和介绍人小白已完全消失，款项未能追回。 因处于对朋友信任，一直再等回复，但是…
#在园区用私人手机连过WiFi的要注意了！！！大可能会被抓
#群友爆料：#柬埔寨 黑心代理（#小陈），#温州苍南县南宋镇人。 刚开始是在 #西港 做业务员，后面到金边一家六合彩公司做代理。代理期间，因本人爱玩包厢、吸DU，多次让公司买单，后面导致整条线的人赔付拉满。 又哄骗底下的人员，说老板不仁义、故意搞事情，又把所有人卖到八号园区三期，在里面做欧美精聊。每天不是体罚就是挨打，每天被折磨着，也不出去管。 这些可都是你自己老家人，你怎么能狠得下心呢？ 后面因为柬埔寨大扫荡，公司决定去老挝那边，又对人员进行洗脑。人员也是出于老家人的情分，才答应你过去。 可是你负责了吗？从一开始的敷衍了事，到现在的不回复。我一个亲戚家的孩子一直没有消息。 人心都是肉长的，你也有老婆孩子，而且你的孩子才刚出生没多久，你不想想她们吗？ 此人特别爱装大款，到处装自己是个有钱的大老板、大盘总。几百块人民币都要借几个人，可想而知这种人的人品有多差。 到处骗团队，到现在人在越南胡志明做盘，不知道又是谁的团…
#群友投稿 #突发紧急通知！#万象 #全城KTV、#酒吧 #紧急停业 5天！饭店严禁放歌！违者将遭军警严惩 各位在老挝万象生活、做生意的华人朋友注意了！近期如果在万象有聚会、聚餐或者娱乐计划，请务必及时调整安排。 根据万象市文化与旅游厅最新发布的官方通知，为沉痛哀悼老挝党中央政治局委员、国会主席赛宋蓬·丰威汉（Dr. Xaysomphone Phomvihane）同志逝世，万象市九大县区文旅部门以及全市餐饮、娱乐场所经营者，均需严格遵守最新临时停业规定。 通知期间，万象市KTV、酒吧等娱乐场所将暂停营业5天；餐厅、饭店等场所禁止播放音乐及开展娱乐活动。 相关经营场所务必严格执行规定，避免违规营业。近期准备在万象聚会、娱乐的朋友，也请提前做好安排，以免受到影响。 #老挝新闻 ps：娱乐场所要停业，出去玩的避免跑空 ㅤ
#群友投稿：#公司准备提桶跑路 #巴基斯坦 了，说实话前几天看了大事件，我真以为有遣散费这个说法，没想到公司搬了，工资都要吃手下员工的。 有个兄弟亏大咯，上个月提成3w+美金，没护照。果然在东南亚这个地方，良心最不值钱。 ㅤ
#柬埔寨知名大学校刊揭露网赌电诈头目陈志 8月11日 #柬埔寨 #高考次日，柬埔寨知名高校诺顿大学（Norton University）推出厚达百页的吸引眼球的全新校刊《The Herald》，面向即将升入大学的高校生。 该刊物除展现校友风采及国际国内大事外，重点引入了电诈治理等关键社会议题。令人关注的是，校刊专门揭露了太子集团掌门人陈志及其网赌电诈犯罪案，详述其如何从打着慈善旗号的所谓年轻企业家沦为跨国犯罪头目。 据悉，经过中柬两国警方数月联合调查，陈志已于2026年1月6日与两名同伙在柬埔寨被捕并押解回中国。校方借此呼吁青年学生认清网络犯罪危害，同时欢迎广大学子报考诺顿大学。 不知道当年文森特赞助过这所学校没有～～ ㅤ
🇵🇰 #巴基斯坦“#伊斯兰堡”前天被端狗推反应：目前中国大使馆已介入，这下真的神仙难救了…
#柬埔寨严打盗割电缆 ，#最高可判10年 #柬埔寨 #金边市 及多地近期频繁发生基站（BTS）电缆及设备被盗案，为此，有关部门正加大侦查力度，严厉打击此类违法犯罪行为，目前已锁定并逮捕多名嫌疑人。 当局强调，不仅直接盗窃及破坏设备者将面临刑事处罚，涉嫌隐瞒、收购或转售盗窃物品者也将受到法律严惩。 根据柬埔寨现行法律，盗窃及破坏财物罪可判处2至10年监禁；而涉嫌收赃者则将面临5至10年监禁及最高1000万瑞尔罚金，并须全额赔偿经济损失。
#博睿集团 #拖欠工资 #跑路狗 #司马公司，找个理由把团队解散了，然后拖欠工资不发，然后又找理由绩效加班工资不发，现在直接跑路。还找个骗子hr来继续行骗。大家注意必坑 还在职的长点心，老板福建人，人事老板狗腿子，平时不看消息，半夜偷偷清空记录，真的是死妈玩意。
❤1
Showing the 12 most recent of 78 posts we hold for @DNYXWWBG. 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.
Citation-graph rank — 76,170 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 23 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“东南亚新闻网-东南亚大小事-曝光骗子-群众投稿” (@DNYXWWBG), 7,349 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/DNYXWWBG.
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.