Channel
@SEAUPD
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
10,926subscribers
-24,645 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003583578625 |
|---|---|
| Type | Channel |
| Username | @SEAUPD |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 October 2026 |
| Measurements held | 39 |
| Confirmed unchanged | 1 time, most recently 14 October 2026 |
| On Telegram | t.me/SEAUPD |
National news — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Oct 2026, 22:47 | 10,926 | -64 |
| 13 Oct 2026, 16:59 | 10,990 | -73 |
| 9 Oct 2026, 22:57 | 11,063 | -212 |
| 5 Oct 2026, 13:56 | 11,275 | -122 |
| 29 Sept 2026, 17:42 | 11,397 | -14,848 |
| 18 Sept 2026, 02:40 | 26,245 | -65 |
| 15 Sept 2026, 22:41 | 26,310 | -215 |
| 14 Sept 2026, 08:00 | 26,525 | -133 |
| 12 Sept 2026, 17:38 | 26,658 | -360 |
| 10 Sept 2026, 16:17 | 27,018 | -1,113 |
| 7 Sept 2026, 14:19 | 28,131 | -3,756 |
| 4 Sept 2026, 18:17 | 31,887 | -58 |
| 3 Sept 2026, 02:06 | 31,945 | -120 |
| 2 Sept 2026, 02:32 | 32,065 | -151 |
| 1 Sept 2026, 00:17 | 32,216 | -131 |
| 31 Aug 2026, 00:24 | 32,347 | -117 |
| 30 Aug 2026, 02:05 | 32,464 | -197 |
| 29 Aug 2026, 00:57 | 32,661 | -155 |
| 27 Aug 2026, 22:12 | 32,816 | -78 |
| 26 Aug 2026, 23:08 | 32,894 | first reading |
649 posts held, back to 5 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 97 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 21 of 57 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 September 2026 |
|---|---|
| Posts held | 649 (5 August 2026 – 29 September 2026) |
| Views total | 32,777 |
| Reactions total | 23 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Sept 2026, 14:56 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.
Measured directly from 59 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.
38 reactions across 36 posts, in 9 distinct kinds. The most used accounts for 21.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ⚡ | 8 | 21.1% | |
| 🤩 | 8 | 21.1% | |
| 🥰 | 5 | 13.2% | |
| 👍 | 4 | 10.5% | |
| 👏 | 4 | 10.5% | |
| ❤ | 3 | 7.89% | |
| 🎉 | 3 | 7.89% | |
| 😁 | 2 | 5.26% | |
| 🔥 | 1 | 2.63% |
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 37 of the 649 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 38 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 649 most recent posts we hold, published 5 August 2026 to 29 September 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.
东南亚新闻资讯 泰国北榄府邦普洪灾酿悲剧，六岁男童屋外玩耍跌入水沟溺亡，母亲现场悲痛抱尸痛哭。 2026年9月28日上午9时，北榄府邦普警方接到报案，一名6岁男童塔纳威在家附近失踪。受洪灾影响学校停课，男童在家门口积水区域玩耍，家人短暂疏忽后不见孩子踪影，在水沟边寻获拖鞋，随即呼叫救援。联合善堂基金会潜水员下水搜寻约十分钟，打捞起男童遗体。见到孩子遗体，男童母亲当场崩溃痛哭，紧紧抱住孩子，场面令人心酸。 据外公讲述，一家人在此居住看护墓地三十余年，洪水让房屋与水沟水位几乎齐平，孩童难以判断水深。 警方将询问家属，继续核实事件完整经过。洪水周边暗藏看不见的落水风险，照看孩童万万不可松懈。愿孩童安息，也提醒受灾家庭看护好孩子，规避水边各类险情。
#柬埔寨缉毒 #蒙多基里省 #跨省联合 柬埔寨蒙多基里省警方联合上丁省警力，开展跨省缉毒行动。9月25日至26日，共抓获10名涉毒人员，其中包括1名女性。行动中缴获毒品118.68克、9部手机、5辆摩托车、4台毒品秤及大量武器弹药。所有嫌疑人已被拘留，将依法移送法院审理。
🎉1
东南亚新闻资讯 泰国民主党副主席拉特克劳赴曼谷龙凯奥灾区救灾，呼吁政府搭建统一灾民救助系统。 2026年9月28日，拉特克劳联合感恩基金会志愿者乘船深入洪灾片区，疏散老人、卧床病患，向被困居民发放救济物资。实地勘查发现，部分灾民已两三天缺少食物，大量弱势群体亟待救援。他指出，民间、军方与基金会志愿者力量充足，但缺少统一主管机构统筹调度物资、船只与人员。 他以野猪队救援案例举例，呼吁政府快速建立系统化指挥体系，动态调配资源，避免重演合艾洪灾困境，确保援助精准送达被困民众。 多方志愿力量有心救灾，但高效统筹调度至关重要，期盼官方快速搭建救援指挥体系，保障所有被困灾民及时获得救助。
东南亚新闻资讯 泰国政府联动多方转移超38万只牲畜避险，同步核查灾情推进农户损失补偿。 2026年9月28日，总理府副发言人帕达拉通报洪灾畜牧救助进展。泰国10个府遭遇洪灾，2313户养殖户受灾，共有71.5万余只牲畜处在洪水区域。畜牧厅联合军方、地方部门，已安全转移381131只动物，发放饲草与动物保健物资，安排流动兽医下乡诊疗，并乘船深入被淹养殖场，成功转移被困生猪与牛群。目前罗勇、夜颂已有两万余只畜禽死亡失踪，相关部门正加快统计损失。 政府将依照灾害援助准则，对死亡牲畜、受损草场发放补偿金，养殖户可线下或通过畜牧厅4.0应用申请援助。 洪灾之下畜禽救援与农户补偿同步推进，希望受灾养殖户顺利拿到补助，减少灾害带来的经济损失。
东南亚新闻资讯 泰国暖武里公寓发生悲剧，骑手敲门女友未听见，冒险爬窗失足从十楼坠落身亡。 2026年9月28日凌晨1时15分，暖武里府邦艾县一处公寓发生坠楼事故，22岁外卖骑手纳鲁吉不幸殒命。监控记录事发经过，男子敲门联系女友却没有得到回应，便爬出电梯口滑动玻璃窗，试图攀爬进入自家房间，雨夜脚下打滑从十楼高空坠落。救援人员冒雨抢救，持续进行三十多分钟心肺复苏，依旧没能挽回生命。 女友表示当晚熟睡完全没有听见敲门声，透露男友过去也曾有过爬窗进屋的行为。 警方调取监控留存证据，遗体移送法医研究所开展尸检，进一步厘清完整事发经过。高空徒手攀爬风险极高，这场意外令人唏嘘，切勿采取冒险的翻墙爬窗方式进屋，避免酿成无法挽回的悲剧。
👍1
#马来西亚 #缅甸难民 #遣返行动 马来西亚移民局启动遣返缅甸难民计划。首阶段在红土坎遣返1476名缅甸籍被拘留者。行动由内政部联合移民局等部门执行，系马缅政府达成协议的成果。计划分阶段遣返总计5000人。所有被遣返者均完成身份核实、国籍确认、文件办理及健康检查。遣返过程确保安全、有序、自愿且依法进行。
东南亚新闻资讯 泰国自然资源部下令救援暹罗公园受洪灾坡鹿，成功转移10只，6只不幸溺亡。 2026年9月28日，社交媒体曝出曼谷暹罗奇妙公园内大批坡鹿困于洪水中。自然资源与环境部部长素察获悉后，立刻联动公园管理方，调派国家公园厅工作人员、兽医及多支志愿救援队伍赶赴现场。当晚20点30分，二十名救援人员开展转移作业，历经三小时完成救援，成功救出10只坡鹿，同时找到6只已经死亡的坡鹿。 素察要求相关单位持续跟进幸存坡鹿的健康状况，公园方面也表态会全力配合，最大限度降低洪水给园内动物带来的伤害。 洪灾同样威胁园内野生动物生存，此次紧急救援挽回部分生命，后续将持续照料幸存坡鹿，密切监测它们的身体恢复情况。
🥰1
东南亚新闻资讯 泰国大城府亚洲公路发生致命车祸，23岁女子骑摩托遭撞击身亡，手机留存朋友未读问询消息。 2026年9月27日23时50分，大城府亚洲公路18公里处，刚下过雨路面湿滑。23岁女子巴薇甘驾驶摩托车与轿车发生碰撞，被撞飞倒在路面。救援人员赶到后立即急救，实施心肺复苏，但女子最终抢救无效离世。事故现场摩托车严重损毁，涉事轿车并未逃逸，司机留在现场参与施救。抢救过程中，死者手机弹出朋友发来消息“到房间了吗？”，消息再也得不到回复。 警方已固定现场物证，录取轿车司机初步口供，相关说法有待核实，遗体送往法医研究所做尸检，完整事故原因仍在进一步调查。 雨夜湿滑路面行车风险大增，这起悲剧令人唏嘘，也提醒民众雨天出行务必谨慎驾驶，严守交规，避免类似不幸再次上演。
😀😃😃😃😃😃 👍👍👍👍 😀😀😀😀😀😀😀😀😀😀 😀 大品牌 · 大资金 · 大格局 😀😀😀😀😀😀😀😀😀😀 😁 别拿小台和🚩🚩比实力 😀😀😀😀😀😀😀😀 😁 G7实力早已铸就行业标杆 😀😀😀😀😀😀😀😀😀 大额玩家最怕的从来不是输赢，而是赢了之后平台扛不住，在🚩🚩 您从来不需要考虑资金的问题！ 😀😀😀😀😀😀😀😀😀😀😀😀 🥰 G7环球｜专属福利区 ❤️ 大事件 体育馆 吃瓜偷拍 商家群 小说区 无码传媒 ———————————————— 😳暴富通道：G7.com【USDT】 😳暴富通道：G7.com【人民币】 😑飞投通道：@W777 ———————————————— 😀😀😀😀 G7.com 😀😀😀😀 @G7kf 😀😀😀😀 @wwwG7com 😃点击免费领取能量 😀😀😀😀😀😀😀 😀😀😀😀😀😀😀😀 #G7环球娱乐 #G7环球 #PG电子🎣
#缅甸冲突 #军队交火 #空袭 KIA联合部队推进至莫梅克镇入口，激烈交火持续。缅军伤亡严重，9月29日上午出动空袭反击。部分缅军士兵被KIA俘获，战线推进到瑞扎利村桥附近。缅军展开强烈抵抗，战事紧张。莫梅克镇曾由缅军在中国协助下从TNLA手中夺回，边缘地区由KIA控制。局势复杂，提醒附近居民关注安全，及时撤离。
东南亚新闻资讯 泰国议员他威·索颂感慨曼谷洪灾严峻，派船救助南部劳工，呼吁放宽庞多学校办学限制。 2026年9月27日，民族党领袖他威·索颂赴北大年府参与瓦克夫慈善筹款活动，目标募集700万泰铢用于庞多教育机构协会土地与办公楼建设。他谈及曼谷洪灾，忧心约30万在曼谷谋生的南部边境府劳工受困，不少人断粮、出行受阻，已协调当地区长调派船只，为兰甘亨大学后方片区运送生活物资。 同时，他呼吁政府放宽庞多学校办学的教育学文凭硬性要求，让具备资质的宗教领袖可以办学，守护南部宗教教育遗产。 他威还分享泰沙两国恢复外交关系背后，卢特菲博士斡旋调解的相关幕后情况。南部劳工在洪灾中处境艰难，民间力量紧急援手，政策若适度优化，将有助于南部边境社会安定与多元文化和谐发展。
⚡1
东南亚新闻资讯 泰国副总理兼商业部长素帕吉表示，泰美贸易谈判原则上已达成共识，目标赶在美国301条款调查结果公布前完成全部协议。 2026年9月28日，素帕吉在政府大楼介绍进展，称剩余仅为技术细节核对，联合国大会期间与美贸易代表沟通顺畅。与此同时，泰国主办的泰欧自贸协定第十轮谈判在普吉启动，9月28日至10月6日举行，计划解决剩余三分之一议题，争取年内达成。谈及中美贸易氛围缓和，泰方表示将同时发展对中美贸易，依托国内监管，推动企业提高本土原料使用占比，把握市场机遇。 泰国正同时推进对美、对欧两大贸易谈判，力求抢抓窗口期。 若谈判顺利落地，有望为本国企业拓展更广阔的海外空间，但也要在关税与规则变化中审慎权衡，降低外部风险。
❤1
Showing the 12 most recent of 649 posts we hold for @SEAUPD. 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 152 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.
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 14 October 2026 — this entry's latest reading, not the date you are reading this.
“东南亚大事件｜华人新闻｜热点爆料” (@SEAUPD), 10,926 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/SEAUPD.
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.