#新加坡新闻 姐姐下车忘了熟睡妹妹,易塔通工作人员接力帮忙找回 两个小女孩一起坐801号巴士,姐姐到站下车,没发现妹妹在车上睡着没跟上。 姐姐发现妹妹不见了之后急得不行,站台一对热心夫妇帮忙求助巴士车长。车长马上通报控制中心,通知所有跑这条线路的司机留意。 大家一起接力搜寻,最后顺利找到妹妹,姐妹平安团聚。
🎃1

Channel
@dnyhybgxs
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
91,763subscribers
-17,191 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001541402802 |
|---|---|
| Type | Channel |
| Username | @dnyhybgxs |
| Description | 让你看尽海外实事 东南亚一手新闻资讯 揭露所有东南亚黑幕 一切黑公司 黑人事跑路骗局 最新吃瓜 最新悬赏 最新曝光 尽在东南亚新闻吃瓜大曝光 (爆料认准:https://t.me/dnyhybgxs) ☎️投稿爆料: @xiaoxue847 欢迎大家订阅,揭露事实,曝光真相! 内容申明:不负责判别真假~~~~希望广大网友自己能分别是非,可以信,但是不能全信,之所以发出来供大家阅读,主要还是为了防止更多人踩坑! #东南亚 #柬埔寨 #菲律宾 #泰国 #迪拜 #缅甸 #老挝 #马来西 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/dnyhybgxs |
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 10 August 2026 and assigned it the closest of 31 fixed categories, at 81% 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 8 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 |
|---|---|---|---|
| @dnyxw9998/184351 Oct 2026, 12:34 UTC | @dnyhybgxs/16207 · this entry1 Oct 2026, 12:34 UTC | 1.00 | under a minute |
| @dnyxw9998/184792 Oct 2026, 08:31 UTC | @dnyhybgxs/16247 · this entry2 Oct 2026, 08:31 UTC | 1.00 | under a minute |
| @dnyxw9998/1903010 Oct 2026, 14:34 UTC | @dnyhybgxs/16824 · this entry10 Oct 2026, 14:34 UTC | 1.00 | under a minute |
| @dnyxw9998/1966719 Oct 2026, 21:29 UTC | @dnyhybgxs/17544 · this entry19 Oct 2026, 21:29 UTC | 1.00 | under a minute |
| @dnyxw9998/1973320 Oct 2026, 22:05 UTC | @dnyhybgxs/17615 · this entry20 Oct 2026, 22:05 UTC | 1.00 | under a minute |
| @dnyxw9998/1988022 Oct 2026, 15:04 UTC | @dnyhybgxs/17761 · this entry22 Oct 2026, 15:04 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @dnyxw9998 | 353 (6/8 hand-verifiable sample passed) | 1.00 | under a minute | @dnyxw9998 (343–10) |
| @dnyhrxsbg | 18 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | @dnyhrxsbg (10–8) |
| @baoguang_12315 | 16 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @baoguang_12315 (16–0) |
| @dnycgbgshij | 8 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (6–2) |
| @baoguangchn | 7 (7/7 hand-verifiable sample passed) | 0.98 | 5 minutes | this entry (7–0) |
| @ershouflb | 6 (5/6 hand-verifiable sample passed) | 1.00 | 2.1 hours | this entry (6–0) |
| @qiusu664 | 6 (5/6 hand-verifiable sample passed) | 0.97 | 2.0 hours | this entry (6–0) |
| @xinwenriji | 6 (5/6 hand-verifiable sample passed) | 0.97 | 2.3 hours | this entry (6–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. 368 of the 368 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 2,251 comparable posts for this entry, running 7 August 2026 to 16 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 17 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, 03:50 | 91,763 | -225 |
| 12 Nov 2026, 17:46 | 91,988 | +1,886 |
| 10 Nov 2026, 12:59 | 90,102 | -111 |
| 9 Nov 2026, 03:51 | 90,213 | -78 |
| 7 Nov 2026, 19:46 | 90,291 | -385 |
| 6 Nov 2026, 17:09 | 90,676 | -409 |
| 5 Nov 2026, 19:18 | 91,085 | -328 |
| 4 Nov 2026, 21:01 | 91,413 | -49 |
| 3 Nov 2026, 17:35 | 91,462 | -82 |
| 2 Nov 2026, 15:18 | 91,544 | -38 |
| 1 Nov 2026, 13:06 | 91,582 | -133 |
| 31 Oct 2026, 10:41 | 91,715 | -90 |
| 30 Oct 2026, 08:06 | 91,805 | -150 |
| 29 Oct 2026, 11:10 | 91,955 | -193 |
| 28 Oct 2026, 06:36 | 92,148 | -59 |
| 27 Oct 2026, 04:21 | 92,207 | -94 |
| 26 Oct 2026, 05:57 | 92,301 | -219 |
| 25 Oct 2026, 06:01 | 92,520 | -4,771 |
| 24 Oct 2026, 03:47 | 97,291 | -1,278 |
| 23 Oct 2026, 00:38 | 98,569 | first reading |
2,622 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 210 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 206 of 820 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 2,622 (7 August 2026 – 17 November 2026) |
| Views total | 5,372,955 |
| Reactions total | 311 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 09:09 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 17 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 191 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.
370 reactions across 263 posts, in 72 distinct kinds. The most used accounts for 19.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 73 | 19.7% | |
| ❤ | 9 | 2.43% | |
| 🌭 | 8 | 2.16% | |
| 🎅 | 8 | 2.16% | |
| 😡 | 8 | 2.16% | |
| ☃ | 7 | 1.89% | |
| 👏 | 7 | 1.89% | |
| 🖕 | 7 | 1.89% | |
| 😈 | 7 | 1.89% | |
| 🤔 | 7 | 1.89% | |
| 🫡 | 7 | 1.89% | |
| ⚡ | 6 | 1.62% | |
| 🎄 | 6 | 1.62% | |
| 👻 | 6 | 1.62% | |
| 😘 | 6 | 1.62% | |
| 🙊 | 6 | 1.62% | |
| 🤝 | 6 | 1.62% | |
| 🤡 | 6 | 1.62% | |
| 🤬 | 6 | 1.62% | |
| 🤮 | 6 | 1.62% | |
| 52 further kinds | 168 | 45.4% |
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 265 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 370 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 13 October 2026 to 17 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 820 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).
#新加坡新闻 姐姐下车忘了熟睡妹妹,易塔通工作人员接力帮忙找回 两个小女孩一起坐801号巴士,姐姐到站下车,没发现妹妹在车上睡着没跟上。 姐姐发现妹妹不见了之后急得不行,站台一对热心夫妇帮忙求助巴士车长。车长马上通报控制中心,通知所有跑这条线路的司机留意。 大家一起接力搜寻,最后顺利找到妹妹,姐妹平安团聚。
🎃1
#柬埔寨新闻 洪玛奈在马尼拉出席东盟峰会,参与亚洲零排放共同体会议 11月17日上午,柬埔寨首相洪玛奈带队在菲律宾马尼拉参加第49届东盟峰会,开完东盟+3峰会之后,接着出席第四届亚洲零排放共同体(AZEC)首脑会议。 这场会议由菲律宾总统小马科斯和日本首相高市早苗一起主持,大家一起聊清洁能源转型、能源安全、碳市场这些议题。日本还提议打造亚洲版国际能源署,由东盟与东亚经济研究所担任秘书处,统筹应急石油储备。 AZEC一共11个成员,包含9个东盟国家加上日本、澳大利亚,目标是在稳住经济和能源供应的同时,推进区域净零排放。
🤝1
#新加坡新闻 樟宜机场偷耳机直接离境,港男隔两月转机落网被控 38岁香港男子在樟宜机场一号航站楼商店拿走一盒耳机,没结账就出境。 时隔两个多月,他再次过境转机时,机场警方提前布控将他抓获,11月17日被控偷窃。耳机价值347.71新元,店员盘点时发现货品不见,调监控才锁定他。
🤷♀1
🏆🏆🏆🏆🏆🏆 🇻🇳🇻🇪🇻🇳🇻🇳🇻🇪 🩷🩷🩷🩷🩷🩷🩷🩷🩷 🏆 多元游戏 · 一站畅玩 🏆 真人/电子/体育/棋牌/捕鱼/彩票 🏆 每日返水 · 福利不断 🏆 极速出款 · 高效服务 🏆🏆🏆🏆🏆🏆🏆🏆🏆🏆 🏆支持认证:点击可查 🌟😍😍😍😍😍😍😍😍😍😍😍 🩷🩷🩷 🩷🩷🩷 🩷🩷🩷 🩷🩷🩷 🩷🩷🩷 🩷🩷🩷 🌟😍😍😍😍😍😍😍😍😍😍😍 🏆🏆🏆🏆🏆: M8.com 🏆🏆🏆🏆🏆: @m8baby04 🏆🏆🏆🏆🏆: @m8vvip 🩷🩷🩷🩷🩷:@M8COM04_bot
🌭1
#新加坡新闻 海岸乐园四层滑梯滑出意外,男子脚踝骨折要休养半年 30岁的李先生到东海岸海岸乐园玩四层楼高的滑梯,那天阴天滑梯表面潮湿。 他滑下来的时候速度飞快,整个人像炮弹一样冲出去,落在护垫边缘,当场伤到右脚。一开始他以为只是脱臼,到医院检查才确诊三踝骨折,做完手术最少休养半年。 记者实地探访看到,雨后滑梯面上有水,滑下来很难控制速度,不少孩子也说湿滑的时候很危险,不敢玩最高的那条。
❤1
#新加坡新闻 裕廊西骑车女子被蜂群追着蜇,三名保安及时出手帮忙 前天上午11点左右,裕廊西41街靠近湖景豪苑,一名女子骑电单车送餐,突然被十多只蜜蜂围攻追蜇。 女子身上多处红肿,之后还上吐下泻。公寓的三名保安看到后,赶紧招呼她过来用水管冲洗,冲了差不多二十分钟,蜜蜂才慢慢散开,保安还帮忙联系家人、叫救护车送她去医院。 国家公园局后来查到树上20米高的位置有蜂巢,已经安排人把蜂巢拆掉。这是马来亚蜜蜂,一旦巢穴被惊扰就容易发起攻击,大家看到蜂巢别靠近。
🦄1
#马来西亚新闻 柔佛峇株巴辖海域发生3.2级地震,没有海啸风险 周二凌晨零点10分,峇株巴辖西南海域出现3.2级弱震,震源深度10公里。马来西亚气象局确认,这次地震不会引发海啸。 从去年8月到现在,柔佛已经记录到13起地震和余震,峇株巴辖这边就有五起,9月那场4.4级是当地目前最强的一次。 以前马来西亚很少地震,专家表示,苏门答腊一带多年的强震激活了本地断层,所以近些年地震变得更频繁了。
🙏1
#新加坡新闻 东盟家庭报告出炉:大家晚婚少生,超九成家庭扛得住压力 最新的《2026年亚细安家庭状况报告》周二对外公布,调研覆盖东盟十国近1.3万户家庭。 区域里普遍结婚越来越晚、生孩子变少,家庭也越变越小。女性初婚年龄往上走,男性同样推迟,新加坡的初婚年龄在东盟里面是最高的。 生育率方面,只有柬埔寨、印尼和老挝还达标,新加坡0.9、泰国1.0排在低位。有意思的是,虽然大环境这样,超过九成受访家庭韧性很强,不少已婚人士对婚姻生活还算满意。 社会及家庭发展部长马善高提到,很多研究都是参考西方,不太贴合亚洲家庭,所以东盟花两年一起做这份调研,用来帮忙调整家庭相关政策。
🌚1
#泰国新闻 阿努廷呼吁柬埔寨,别把双边矛盾闹上国际平台 泰国首相阿努廷表态,泰柬之间的分歧不该拿到国际上说,双方要多做事情建立互信。 阿努廷11月15日在脸书发文回应相关言论,他说泰国不会把领土、人道这类争端交给无关第三方,会尊重和柬埔寨达成的各项协议,遵守国际法。 泰国打算沿用现有的双边沟通机制,依照国际法和平处理问题,也希望柬埔寨拿出同样态度,一起守住边境和平,惠及两边民众。 泰柬局势联合信息中心主任巴帕斯也补充,泰国会恪守去年底签下的停火声明,希望柬方回归协议,不要在国际场合互相指责,消耗彼此信任。
❤1
#新加坡新闻 文庆路组屋卧房起火,百多人疏散还有宝宝被转移 文庆路第8座组屋23楼的一个卧房,周一傍晚起火了。民防部队收到消息马上派人赶到现场,用水枪把火灭掉。 这场火情让大约140名居民紧急撤离,里面还有两名新生儿。失火单位里有一名住户提前跑出来,不过吸入浓烟,送去中央医院检查。 居民、邻里互相帮忙,一起把小宝宝平安转移,也是这场意外里很暖心的一幕。
❤1
#新加坡新闻 撞见监控慌了!男子潜入寺庙偷功德钱,跑路出境被抓 这名36岁中国男子穿着黑上衣黑裤子,还戴帽子遮掩,甚至做好了自制工具,打算撬开寺庙功德箱拿钱。 他上周四刚进到新加坡,看样子就是专门过来做这事的。这天他摸到景万岸惹兰申萌的寺庙里面,正要动手,一眼看到摄像头对着自己,当场不敢继续,赶紧溜了。 寺庙这边很快报了警,警方多方配合追查,才四个小时就查到他的踪迹。男子还想着直接离境走人,结果在关卡被拦下,星期二被控上法庭。
💘1
🫤😐🫥😶🤥🫠🤫🫡🫢 😑 N9 国际认证 | 信誉平台 支持5倍验资 【验资:@N9KF】 担保域名:N9.TOP 点击查看 ⚡️⚡️⚡️⚡️ 💝 新会员好礼 注册就送28.8U 新人首存/二存/三存最高赠送8️⃣8️⃣8️⃣8️⃣U 💝 老会员好礼 电子狂欢每日存款赠送10% 充值笔笔送3%无上限 夜间充值最高可优惠8888U ⚡️⚡️⚡️⚡️⚡️⚡️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 香港六合彩 4️⃣8️⃣.8️⃣ 倍 加拿大28全网返水最高 ⚡️注册网址:N9.PRO 😇🧐🧐😗🧐😙😄 ⚡️ 官方客服: @N9KF ⚡️ 官方飞投: @N9N9 ⚡️ 彩票客服: @N9CP ⚡️ 彩票飞投: @N9N9N9 ⚡️ 福利频道: @N9pd888 ⚡️ 注册网址: N9.COM【USDT】 ⚡️ 注册网址: N9.C…
🥰1
Showing the 12 most recent of 2,622 posts we hold for @dnyhybgxs. 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 4 posts on @dnyhybgxs 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.
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.
@dnyhybgxs named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
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.
“东南亚新闻华人吃瓜大曝光” (@dnyhybgxs), 91,763 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/dnyhybgxs.
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.