Telegram RegisterThe public register of Telegram

Channel

东南亚热点|新闻|曝光

@SEA666NEWS

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

1,299subscribers

-6 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003701144450
TypeChannel
Username@SEA666NEWS
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/SEA666NEWS

Topic

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 83% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear word for word on 3 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@SEA666NEWS/10997 · this entry6 Aug 2026, 11:39 UTC@SEA0001/109696 Aug 2026, 11:39 UTC1.00under a minute
@SEA0001/109716 Aug 2026, 12:05 UTC@SEA666NEWS/10998 · this entry6 Aug 2026, 12:05 UTC1.00under a minute
@SEA666NEWS/11000 · this entry6 Aug 2026, 12:19 UTC@SEA0001/109736 Aug 2026, 12:20 UTC1.00under a minute
@SEA0001/109876 Aug 2026, 14:31 UTC@SEA666NEWS/11015 · this entry6 Aug 2026, 14:31 UTC1.00under a minute
@SEA666NEWS/11017 · this entry6 Aug 2026, 15:00 UTC@SEA0001/109896 Aug 2026, 15:00 UTC1.00under a minute
@SEA666NEWS/11023 · this entry6 Aug 2026, 15:59 UTC@SEA0001/109956 Aug 2026, 16:00 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@SEA000113 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (112)
@bx70079 (8/8 hand-verifiable sample passed)1.00under a minute@bx7007 (90)
@k1dny5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (50)

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. 11 of the 11 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 19 comparable posts for this entry, running 6 August 2026 to 6 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 4, the earliest publisher we hold is @SEA666NEWS — 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 8 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 3 other registered channels, 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.

Growth

1,2991,3051,3026 August 2026 — 1,305 subscribers7 August 2026 — 1,304 subscribers11 August 2026 — 1,299 subscribers6 August 202611 August 2026
3 measurements spanning 4 days, net -6. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,298–1,306 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 02:561,299-5
7 Aug 2026, 17:331,304-1
6 Aug 2026, 19:471,305first reading

Engagement

19 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.126%
avg views ÷ 1,299 subscribers
Avg views / post
1.6
19 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
19
of 19 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held19 (6 August 20266 August 2026)
Views total31
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 19:47 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.

Recent posts

6 Aug 2026, 19:32 UTC1 viewsread 6 August 2026

常规资源: 新闻频道:https://t.me/hotdny 吃瓜搞笑:https://t.me/iiit001 DJ经典:https://t.me/DJ057 国际资讯:https://t.me/qqhots 体育赛事每日更新:https://t.me/kq978 文案馆:https://t.me/wenan018 币圈实时更新新闻:https://t.me/niuniubtc 电影解说:https://t.me/dianying28 海外素材/人设/套图:https://t.me/sucai098 黑平台曝光:https://t.me/baoguang066 群组: 体育交流群:https://t.me/sportscn 极搜中文资源搜索:https://t.me/qisuso AI中文搜索:https://t.me/aasuso 色情搜索大全:https://t.me/sosozwz 成人内

6 Aug 2026, 19:22 UTC1 viewsread 6 August 2026

📌 其他 📢 精选福利社 📢 菲律宾大事件 菲律宾日记 📢 缅甸新闻 泰国大事件 越南大事件 📢 金三角大事件 特区实时资讯 📢 西港事件 西港曝光 西港大事件 西港日记 西港新闻 📢 斯里兰卡大事件 东南亚动态 东南亚早报 东南亚新鲜事 📢 内涵段子🔥搞笑视频 📢 吃瓜 猎奇 热门 搞笑 📢 娱乐头条(吃瓜段子) 📢 内涵段子TV 📢 搞笑视频 内涵段子 吃瓜视频 📢 国产热门擦边短剧 📢 海外素材库/人设 套图 📢 欧美AV无码女优 📢 人间文案馆 📢 擦边短剧精选热播 📢 日本AV 中文字幕 精品女优合集 📢 日本AV|高清无码 📢 日本AV 中文字幕 精品女优合集 📢 每日精选AV(黑丝 自慰 露出 巨乳 ) 📢 中文字幕 | 日本AV 📢 日本无码AV/在线/最新 📢 日本无码破解av少妇人妻 📢 无码AV精选 📢 热门电影速看/高分电影推荐 📢 每日素材精选 📢 热门BGM|抖音神曲 📢 海外大事件 海外华人大事件

6 Aug 2026, 19:22 UTC1 viewsread 6 August 2026

🔍同城交友 📢 767资源导航|精品资源 🧩兴趣社区 📢 网红极品无码推特 📢 伪娘TS人妖男同 📢 足交黑丝白丝母狗玉足 📢 大屌人妖女王伪娘高潮 📢 欧美黑人无码AV 📢 伪娘男奴潮喷 📢 热点曝光台 📢 i8国际娱乐平台(⚽️2026世界杯专属平台) 📢 体育|电竞|足球|NBA【每日推荐】 🍉新闻吃瓜 📢 搞笑视频 内涵段子 吃瓜视频 📢 亚太曝光 亚太大事件 金边大事件 国家大事件 📢 东南亚吃瓜搞笑 📢 木牌大事件 戈公日记 西港新闻 📢 迪拜新闻|东南亚大事件|曝光群 📢 全网热搜社 📢 东南亚吃瓜 @cg258 📢 东南亚吃瓜新闻|新闻快讯 📢 新闻情报局 📢 吃瓜群众丨抖音热搜 📢 国际新闻|吃瓜新闻|突发事件 📢 全球新闻|曝光|吃瓜|突发事情 📢 东南亚大事件 | 吃瓜新闻 📢 东南亚大事件 | CG快报 🎬影视资源 📢 口爆反差极品 📢 群P巨乳妹迷奸 📢 母狗|反差|福利 📢 网红资源之家 📢 网

6 Aug 2026, 18:59 UTC1 viewsread 6 August 2026
Photo

#新加坡新闻 【谎称炸机致三航班延误 20岁男判缓刑监视12个月】 20岁青年陈志凯去年6月7日在樟宜机场候机时在社媒发文戏称要炸机并设自动回复称已成功炸机 警方接获匿名举报后紧急排查三架酷航航班导致延误至凌晨 共损失约2000新元 被告返新时被捕后全额赔偿 8月6日被判12个月缓刑监视 须遵守每晚10时至清晨6时宵禁90小时社区服务及父母担保5000元 法官指其行为造成严重后果不容轻视 但考虑被告年轻不成熟无预谋和恶意且已积极悔改并赔偿 认为缓刑足以达到改造目的 辩方称被告犯案时仅19岁因幼稚和判断力差鲁莽行事 控方曾要求评估是否适合缓刑或改造训练 强调机场属关键基础设施此类行为浪费公共资源须起阻吓作用 小编PS:玩笑开大了! _ _ ✅投稿澄清爆料: @kq869 🤖投稿双向机器人: @tghotdnybot

6 Aug 2026, 18:40 UTC1 viewsread 6 August 2026

谷歌互推【频道A7】 👉关键词搜索 丨 全网搜片 1. 福利姬轮奸海角社区 2. 夏小姐的黑丝长腿高跟鞋👠 3. 35都怪小姨子太漂亮 4. 网红福利/推特 5. 情侣自拍/真实 6. 电报智能吸粉流量翻倍 7. cos sex修罗场 黄色 8. 欧美无码 9. 稀缺影片互助互推 10. 🪃萝莉 福利姬 cos 反差 11. 强奸 巨乳 12. 东南亚~色情吃瓜 13. 伦理乱伦护士处 14. 🟢激情诱惑|双马尾萝莉|熟女少妇 15. 玉女高清/怀旧三级/四级片 16. 上海(外围)兼职选妃频道 17. 爆款素材库 18. 大学生宿舍和男的一起自拍泄露 19. 影视,擦边短剧、热门短剧,上头剧情 20. 九江外围品茶甜美大学生会调情 21. 初中老师被学生偷拍 22. 【日本无码AV&反差少女】 23. 日本好片无码AV高颜值FC2 24. 骚女精神小太妹 25. 超清日本AV |无码FC2| 26. 国产反差,母狗调教 27

6 Aug 2026, 18:28 UTC2 viewsread 6 August 2026
Video

🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🥸🥸🥸😅😞😉😉😉😝😝 😁😁😁😁😁😁😁😁😁😁😁 😁零审核😁秒到账😁无风控😁免实名 信誉保障,大额无忧,赢的放心,出的舒心 😬okpay上押500万u担保 放心赢 😬 😬信誉保障,大客户最佳选择:U存U提 😬每日提款不限额 不限制次数 免实名 😬无需绑银行卡 无需绑手机号 不限ip 🥸新人注册首充最高送😄😄😄😄😬 🔝热门赛事 · 实时互动 · 多元玩法🔝 ⭐️无限代理模式,业内最高佣金😶😬😬 注册网址:🌟 i8.COM【USDT通道】 注册网址:💸 i8.COM【人民币通道】 注册网址:🏆 i8.COM【世界杯通道】 😁😁😁😁😁😁😁😁😁 😁😁😁😁:@i8kf 😁😁😁😁:@i8xmm (彩金客服) 😁😁😁😁:@i8pd 😁😁😁😁:i8.com 🔥欢迎各位老板加入i8国际娱乐城! i8国际 #娱乐平台 #i8 #世界杯 #真人 #PG电子 #棋牌 #捕鱼 #彩票

6 Aug 2026, 17:59 UTC1 viewsread 6 August 2026
Photo

#柬埔寨新闻 【AOT视察柏威夏边境冲突受损平民区】 东盟驻柬埔寨观察团8月6日上午在柬埔寨联络小组协调下 前往柏威夏省乔姆克桑县北斯拉恩村进行实地观察 以核实边境局势并监督停火执行情况 该地区为居民区 去年12月泰国军方曾出动F-16战斗机并发射155毫米炮弹实施空袭 造成严重破坏 大量房屋 个人财产和民用基础设施被摧毁 柬埔寨国防部表示柬方一直全力配合观察团工作 强调加强该小组作用以核实停火有效执行 促进透明度和问责制并建立互信 柬埔寨重申致力于全面执行去年12月签署的柬泰边境总委员会联合声明及和平协议 将继续推动恢复和重建工作 以实现边境持久和平与稳定 小编PS:平民区被轰太惨了! _ _ ✅投稿澄清爆料: @kq869 🤖投稿双向机器人: @tghotdnybot

6 Aug 2026, 17:00 UTC2 viewsread 6 August 2026
Photo

#泰国新闻 【41岁男子失踪后死于车内 家人寻获震惊悲痛】 北榄府邦普里县一名41岁男子8月5日晚被发现死于公寓停车场车内 驾驶座放倒 身旁有炭火盆 身上无袭击痕迹 家属当天早上发现男子失联后寻找一整天 最终在停车场找到车辆并确认其死亡 警方已介入调查 死者姐夫表示男子近期疑似承受巨大压力 但未透露具体原因 亲属对死因存疑 警方已收集现场证据并将遗体送检 确认死因后将依法处理 案件引发公众对心理压力问题的关注 小编PS:压力过大悲剧了! _ _ ✅投稿澄清爆料: @kq869 🤖投稿双向机器人: @tghotdnybot

6 Aug 2026, 15:59 UTC1 viewsread 6 August 2026
Photo

#泰国新闻 【好心提醒忘关转向灯 15岁少年遭围殴】 芭堤雅一名15岁少年8月6日凌晨骑摩托车时 发现另一司机未关转向灯便好意提醒 不料对方却命令其停车并叫来同伙围殴 导致少年和朋友受伤 摩托车摔倒 施暴者事后逃离现场 少年已向警方报案 警方正追查肇事者下落 少年表示当时只是善意提醒 对方却突然发难召集同伴施暴 他朋友在冲突中同样受伤 事发后他立即报警求助 警方已将事件记录在案 并派员前往现场调查 正通过监控追捕嫌疑人 案件仍在侦办中 少年呼吁目击者提供线索协助破案 小编PS:好人没好报,太离谱了! _ _ ✅投稿澄清爆料: @kq869 🤖投稿双向机器人: @tghotdnybot

6 Aug 2026, 15:00 UTC2 viewsread 6 August 2026
Photo

#泰国新闻 【剖腹产致膀胱子宫破裂 产妇身亡夫投诉】 泰国北部一家知名医院发生剖腹产医疗事故 一名35岁产妇在手术中膀胱和子宫遭医生损伤引发严重出血不幸身亡 丈夫已向帕维娜基金会提交证据提起申诉 要求追究医疗责任 基金会初步受理并协调公共卫生部监察长介入调查 院方已成立委员会调查事故真相并准备赔偿 但家属对医疗处置存疑 基金会8月6日将赴清迈与卫生官员和涉事医生会面 核实手术操作及事故责任认定 丈夫强调妻子死亡不应被简单归为意外 要求彻查医疗失误 案件仍在调查中 小编PS:这桩医疗事故太沉重了! _ _ ✅投稿澄清爆料: @kq869 🤖投稿双向机器人: @tghotdnybot

6 Aug 2026, 14:40 UTC2 viewsread 6 August 2026
Video

泰国芭提雅清晨街头爆发冲突:一群女子围殴外籍男子,警方介入调查 泰国芭提雅街头发生一起争执事件。一名外籍男子与一群女子发生冲突,现场画面显示,多名女子围上前对男子进行推搡和殴打,引发路人关注。 目前冲突原因尚不明确,相关情况仍在进一步调查中。警方是否介入及双方是否有人员受伤,暂未公布详细信息。 _ ✅投稿澄清爆料: @kq869 🤖投稿双向机器人: @tghotdnybot

6 Aug 2026, 14:31 UTC3 viewsread 6 August 2026
Video

#群友投稿:为什么打飞机比嫖娼更有性价比? 相信目前的形势,海外漂泊的没业绩小狗推,每个月都会因为去会所舔逼绞尽脑汁,要么借支,要么套花呗。今天你看到我这篇文章,读懂以后,每个月能省5000u😁。 首先,对比一下嫖娼和打飞机的成本。 **打飞机:**纯手工活,要么网上找个片,要么意淫一下白天女同事的腿,在厕所抹点沐浴露就开始撸。有条件的买个飞机杯,自己爽一下能用一百多次,成本几乎接近于0。 **嫖娼:**会所漂亮一点的,基本300u左右90分钟。而且嫖娼这玩意没有回本概念,每次射完以后都觉得真tm亏,下次来又要重新付钱。 其次,对比一下嫖娼和打飞机的健康问题。 **打飞机:**只要你没有丧心病狂到偷保洁阿姨沾满白带的内裤套在鸡巴上撸,基本是不会得病的。 **嫖娼:**HIV、HPV、梅毒,全等着你呢。虽然说会所妹子都有定期体检,但是保不准你哪天去嫖的时候上头了,直接拔套开始干,回宿舍过几天鸡巴越来越痒,还起红疹子。

Showing the 12 most recent of 19 posts we hold for @SEA666NEWS. 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

Citation-graph rank — 99,956 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.

Mentions

Named by 84 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.

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.

Cite this entry

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“东南亚热点|新闻|曝光” (@SEA666NEWS), 1,299 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/SEA666NEWS.

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.