这波BTC暴跌 /网上全是在骂币安 说是用纸大饼砸出来的,一边做空一边爆仓多单,63 亿的洞来回杀几次就差不多回来了
🔥6💯5❤4❤🔥3👍3🤩3🥰3🎉2

Channel
@dny_xwdsj
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
53,604subscribers
+15,695 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002164341082 |
|---|---|
| Type | Channel |
| Username | @dny_xwdsj |
| Description | #东南亚 #柬埔寨 #菲律宾 #缅甸 #泰国 投稿爆料联系: @sihanyzq 商务合作: @sihanyzq 关注柬埔寨及东南亚新闻资讯,大事小情,全天滚动。 声明:频道只负责投稿发布信息,真假自行甄别,理性吃瓜,恶意投稿,后果自负! Hello @Telegram My channel has not violated the rules and policy of using Telegram. |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/dny_xwdsj |
Gambling & betting — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 6 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 |
|---|---|---|---|
| @DNYXWC/200696 Aug 2026, 12:00 UTC | @dny_xwdsj/16733 · this entry6 Aug 2026, 12:00 UTC | 1.00 | under a minute |
| @dny_xwdsj/16735 · this entry6 Aug 2026, 13:00 UTC | @DNYXWC/200716 Aug 2026, 13:01 UTC | 1.00 | under a minute |
| @DNYXWC/200756 Aug 2026, 14:00 UTC | @dny_xwdsj/16782 · this entry8 Aug 2026, 14:00 UTC | 1.00 | 2 days |
| @dny_xwdsj/16798 · this entry9 Aug 2026, 06:56 UTC | @DNYXWC/201509 Aug 2026, 06:56 UTC | 1.00 | under a minute |
| @DNYXWC/2052728 Aug 2026, 13:00 UTC | @dny_xwdsj/17255 · this entry3 Sept 2026, 13:00 UTC | 1.00 | 6 days |
| @DNYXWC/2096218 Sept 2026, 12:47 UTC | @dny_xwdsj/17583 · this entry18 Sept 2026, 12:47 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @DNYXWC | 12 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | even |
| @llsvip888 | 11 (7/8 hand-verifiable sample passed) | 1.00 | 77 minutes | @llsvip888 (11–0) |
| @ixzgg88 | 10 (6/8 hand-verifiable sample passed) | 1.00 | 10 minutes | @ixzgg88 (10–0) |
| @sii76 | 7 (6/7 hand-verifiable sample passed) | 0.98 | 3.9 hours | this entry (6–1) |
| @adqqjmjj | 6 (6/6 hand-verifiable sample passed) | 0.96 | 18 minutes | @adqqjmjj (6–0) |
| @knmkio | 5 (5/5 hand-verifiable sample passed) | 0.97 | 5.0 hours | @knmkio (3–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. 37 of the 37 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 807 comparable posts for this entry, running 6 August 2026 to 15 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.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 16 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 02:44 | 53,604 | -2,170 |
| 12 Nov 2026, 17:48 | 55,774 | -208 |
| 10 Nov 2026, 11:09 | 55,982 | -49 |
| 9 Nov 2026, 01:58 | 56,031 | -32 |
| 7 Nov 2026, 20:31 | 56,063 | -32 |
| 6 Nov 2026, 14:56 | 56,095 | -25 |
| 5 Nov 2026, 16:19 | 56,120 | -49 |
| 4 Nov 2026, 13:37 | 56,169 | -92 |
| 3 Nov 2026, 16:06 | 56,261 | -633 |
| 2 Nov 2026, 18:38 | 56,894 | -157 |
| 1 Nov 2026, 15:48 | 57,051 | +4,864 |
| 31 Oct 2026, 16:06 | 52,187 | -43 |
| 30 Oct 2026, 13:50 | 52,230 | -952 |
| 29 Oct 2026, 15:09 | 53,182 | -14 |
| 28 Oct 2026, 15:55 | 53,196 | -30 |
| 27 Oct 2026, 12:40 | 53,226 | -21 |
| 26 Oct 2026, 15:38 | 53,247 | -45 |
| 25 Oct 2026, 12:56 | 53,292 | -14 |
| 24 Oct 2026, 14:44 | 53,306 | -750 |
| 23 Oct 2026, 13:40 | 54,056 | first reading |
1,187 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 219 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. It is computed over the 322 of 339 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 November 2026 |
|---|---|
| Posts held | 1,187 (6 August 2026 – 15 November 2026) |
| Views total | 758,773 |
| Reactions total | 10,689 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 02:57 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 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 259 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.
28,300 reactions across 834 posts, in 30 distinct kinds. The most used accounts for 8.10% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💯 | 2,291 | 8.10% | |
| ❤🔥 | 1,348 | 4.76% | |
| 😍 | 1,324 | 4.68% | |
| ❤ | 1,317 | 4.65% | |
| 🎉 | 1,309 | 4.63% | |
| 🔥 | 1,295 | 4.58% | |
| 🤩 | 1,290 | 4.56% | |
| 👍 | 1,270 | 4.49% | |
| 🥰 | 1,268 | 4.48% | |
| 😡 | 999 | 3.53% | |
| 😢 | 971 | 3.43% | |
| 🤮 | 935 | 3.30% | |
| 🍌 | 932 | 3.29% | |
| 😈 | 920 | 3.25% | |
| 👎 | 919 | 3.25% | |
| 🥱 | 887 | 3.13% | |
| 💩 | 886 | 3.13% | |
| 🤬 | 885 | 3.13% | |
| 🖕 | 884 | 3.12% | |
| 💔 | 842 | 2.98% | |
| 10 further kinds | 5,528 | 19.5% |
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 834 of the 1,000 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 28,300 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 20 August 2026 to 15 November 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.
Telegram’s own ‘edited’ marker: 0 of 340 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).
这波BTC暴跌 /网上全是在骂币安 说是用纸大饼砸出来的,一边做空一边爆仓多单,63 亿的洞来回杀几次就差不多回来了
🔥6💯5❤4❤🔥3👍3🤩3🥰3🎉2
柬埔寨计划2027年中启用新海底光缆 柬埔寨计划于2027年年中启用一条新的高速海底光缆,以加强国际互联网连接并推动数字领域发展。邮电大臣谢万德在FrancoTech 2026论坛部长级对话上宣布了这一计划,称数字基础设施建设是支撑柬埔寨数字化转型的关键。他表示,目前柬埔寨4G网络覆盖约95%人口,2026年1月启用的5G服务覆盖率已达34.5%。柬埔寨还推出数字技能路线图,目标未来十年培养至少10万名数字专业人才。
❤7🎉5👍5💯3😍3❤🔥2🔥2🤩2
🇨🇳 浙江绍兴公安成功打掉一“茶叶代销”电诈团伙 11月11日至12日,绍兴越城公安抽调警力,赴福建南平、江西上饶开展收网,打掉一个以“茶叶代销”为名的电信诈骗团伙,抓获嫌疑人12名,捣毁三处窝点,现场查获手机、电脑等作案工具。 据越城公安披露:该团伙主要瞄准中老年受害人,先打造虚假人设,以祈福、关怀拉近关系,再以茶叶代销、高额收益为诱饵实施诈骗。现已查实受害50余人,涉案金额100余万元。 目前,12名嫌疑人已被采取刑事强制措施,案件正在进一步侦办中。
💯6👍5🤩5❤🔥4🥰4❤3😍2🎉1
#频道互推 #相似推荐 ------------------------------ 📢 缅北大事件曝光 📢 东南亚大事件 「新闻曝光」 📢 东南亚大事件|华人新闻|热点爆料 📢 初中生学生 📢 全球:国际新闻、曝光 📢 西安艺妓 📢 事件曝光 新闻爆料 📢 东南亚曝光吃瓜 新闻 📢 News from world 📢 韩国新闻|社会热点大事件 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励
#网友爆料:缅甸妙瓦底“帕胺”山上,号称“Dalei山B区”,都是黑公司,这里的被困人员每天都在遭受虐待,简直是人间地狱般的打人。 很多中国人被困在山上,这些人都是被骗招、绑架来的,他们没有机会回家。每天都遭受电击、被铁棍殴打,有的骨头都被打断。 物业是知情的,知道那些公司虐待员工、打人的事,他们也不在乎,只为了自己的利益,不管不顾。 希望缅甸政府、中国警方,国际援助部队能关注这里,尽快解救这些人。
❤6💯5😍4🎉3🔥3🥰3❤🔥2👍2
#网友爆料:缅甸妙瓦底帕胺山上,号称“Dalei山B区”,都是黑公司,每天都在虐待中国人,简直是人间地狱般的打人。 很多中国人被困在山上,这些人都是被骗、绑架来的,他们没有机会回家。他们每天都遭受酷刑,被电击、被铁棍殴打,骨头都被打断。许多人已经死去,都被埋葬在这里。有时,他们还会被鬼魂缠身。 他们的父母都盼望着他们回家,但有些人却被禁止回家。每天的酷刑都在加剧,有些人已经无法活下去。公司的残暴酷刑和殴打,比牲畜还不如。物业是知情的,知道那些公司虐待、打人的事,他们也不在乎,只为了自己的利益,不管不顾。 希望缅甸政府、国际援助部队能看见这则新闻后,解救这些人。否则,他们都会死在这里,被埋葬在山上。
👍7😍6💯5🎉4❤3🥰3❤🔥1🔥1
45名中国游客泰国机场被拒入境 全部遣返 移民局否认索小费 泰国移民局确认,事件发生在11月12日曼谷素万那普国际机场。45名中国游客被拒绝入境后全部遣返。泰国移民局解释称,这些人未充分说明入境泰国的旅游计划,同时驳斥了有关勒索小费的说法。 引发关注的除拒入本身,还有旅客对候返环境的投诉,以及网上流传的付费过关说法。相关争议有待有关部门进一步说明。
🔥6🤩5👍4🥰4❤3💯3😍3❤🔥1
3名中国人在泰国湄索非法越境被抓 昨天,泰国纳黎萱军区拉差努特遣队下属第1431步兵连在达府湄索县新湄河村一带进行巡逻警戒时,发现可疑人员并随即进行盘查。 经查,现场共有3名中国籍人员(2男1女),且均无法出示任何合法身份证明文件。目前,执法人员已将该3名涉案人员全部控制,并移送至达府移民局,以依法追究其法律责任。
🤩7💯5❤4🎉4🔥3👍2🥰2😍2
迪拜警方打掉跨境投资诈骗团伙 迪拜刑事调查总局今天通报,经过两个多月的长线布控,成功打掉一个盘踞当地的跨境虚假投资诈骗团伙。 团伙主要套路:在社交软件主动添加海外受害人,塑造理财导师、资深交易员人设,诱导受害人进入自制虚假外汇、贵金属交易平台。平台后台人为控制涨跌,前期小额提现博取信任,等受害人大额投入之后直接锁盘、拉黑失联。 团伙成员一共11人,国籍混杂,有南亚、中东籍人员,分工明确:引流客服、直播间讲师、财务结算、资金洗白。赃款收到之后,拆分转入虚拟币钱包、地下钱庄流向多国。 本次抓捕同步突袭3处公寓窝点,当场抓获全部11名嫌疑人,查获大量手机、电脑、直播设备、话术脚本、虚拟币助记词、涉案银行卡。 警方梳理,目前已经核实来自欧洲、西亚、非洲的受害人超过210人,涉案总金额折合美元约720万。 嫌疑人全部羁押,逐一核对聊天记录、资金流水; 冻结涉案虚拟币与银行账户,尝试止损挽损; 同步联系受害所在国警方,开展跨境…
❤5🥰5💯4🔥4❤🔥3👍3🤩3🎉2
3名中国人在泰国湄索非法越境被抓 昨天,泰国纳黎萱军区拉差努特遣队下属第1431步兵连在达府湄索县新湄河村一带进行巡逻警戒时,发现可疑人员并随即进行盘查。 经查,现场共有3名中国籍人员(2男1女),且均无法出示任何合法身份证明文件。目前,执法人员已将该3名涉案人员全部控制,并移送至达府移民局,以依法追究其法律责任。
😍9👍7🎉5💯3🤩3🥰3❤🔥2❤1
来自速搜推荐 @SSOU 📢东南亚大事件/缅甸柬埔寨... 📢西港日报快讯 📢秒合约盘-永续合约- 交... 👥速搜搜索/中文频道/机器... 👥中文索引🔥专业搜 📢短剧|小视频|微电影 👥Telegram❤️资源... 👥速搜中文导航群🇨🇳 📢经典现场|音乐|舞蹈|L... 📢【R%精品】电影解说🎬... 👥中文导航群🔍频道搜索�... 📢女神热舞|直播录屏 📢【R%精品】伪娘|男娘 👥中文索引🔥🔥🔥搜索... 👥索引群聊❤️搜索王 👉流量互推规则介绍💥 以下是广告推荐 📣全网征集/曝光新币担保高管,欢迎大家积极参与📣 📢专业Telegram账号交易平台🔥热门社交媒体账号交易 📢🔥华人圈最火U台 ⫸567U.com⫷ TG飞投 U存U取|新人必赢 📢🥇2G.COM 品牌定位全球 实力超乎想象 📢 X-panel 一站式拉人增粉平台 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelpBot 设置
❤🔥5👍5🥰5😍5❤3🎉3🔥2💯1
冒充快递公司iMessage诈骗持续 约两周内受害者损失至少3.1万元 骗子利用苹果iMessage行骗,冒充快递公司发送钓鱼短信。警方估计,自上个月31日以来,也就在约两周内,这类骗局已造成至少3万1000元的损失。 警方今天(14日)发文告说,骗子会冒充快递公司发送短信,声称包裹的送货资料不完整,或配送出现问题。 警方也发现,有骗子冒充新加坡保健集团综合诊疗所(SingHealth Polyclinics),谎称收件人有还未支付的门诊账单。 警方说,无论冒充哪家机构,骗子都会在短信中附上钓鱼链接,诱使收件人进入虚假网站,以骗取个人资料、银行账户或信用卡信息,或诱导他们付款。 警方提醒公众,不要回复这类可疑短信。如果收到有关包裹配送的短信,应通过ScamShield应用程序或快递公司的官方网站核实信息,并在付款或提供个人资料前,直接向快递公司求证。 警方也呼吁公众更新iMessage设定,确保开启过滤“未知发件人”…
❤🔥7😍6👍5🔥5🎉3💯2🤩2❤1
Showing the 12 most recent of 1,187 posts we hold for @dny_xwdsj. 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.
We recorded 65 posts on @dny_xwdsj as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Named by 27 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 24 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.
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.
@dny_xwdsj named 6 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“西港日报快讯” (@dny_xwdsj), 53,604 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/dny_xwdsj.
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.