Telegram RegisterThe public register of Telegram

Channel

全网热搜社

@SEA0001

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

1,496subscribers

-18 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-1003707599695
TypeChannel
Username@SEA0001
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 live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/SEA0001

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 55% 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
@bx7007/107936 Aug 2026, 14:31 UTC@SEA0001/10987 · this entry6 Aug 2026, 14:31 UTC1.00under a minute
@bx7007/108056 Aug 2026, 17:00 UTC@SEA0001/10999 · this entry6 Aug 2026, 17:00 UTC1.00under a minute
@bx7007/108166 Aug 2026, 18:59 UTC@SEA0001/11008 · this entry6 Aug 2026, 18:59 UTC1.00under a minute
@bx7007/109697 Aug 2026, 13:39 UTC@SEA0001/11151 · this entry7 Aug 2026, 13:39 UTC1.00under a minute
@bx7007/109747 Aug 2026, 14:19 UTC@SEA0001/11156 · this entry7 Aug 2026, 14:19 UTC1.00under a minute
@bx7007/109837 Aug 2026, 15:00 UTC@SEA0001/11165 · this entry7 Aug 2026, 15:00 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@bx700715 (8/8 hand-verifiable sample passed)1.00under a minute@bx7007 (150)
@SEA666NEWS13 (8/8 hand-verifiable sample passed)1.00under a minute@SEA666NEWS (112)
@k1dny9 (8/8 hand-verifiable sample passed)1.00under a minute@k1dny (90)

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. 35 of the 35 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 32 comparable posts for this entry, running 6 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.

  • 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. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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,4961,5141,5056 August 2026 — 1,514 subscribers7 August 2026 — 1,511 subscribers10 August 2026 — 1,496 subscribers6 August 202610 August 2026
3 measurements spanning 4 days, net -18. 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,493–1,517 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 21:171,496-15
7 Aug 2026, 12:151,511-3
6 Aug 2026, 19:471,514first reading

Engagement

37 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 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.074%
avg views ÷ 1,496 subscribers
Avg views / post
1.1
37 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
37
of 37 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 7 August 2026
Posts held37 (6 August 20267 August 2026)
Views total41
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 18:11 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.

What this channel posts

Video runtime
1m 56s
Average length
29s

Measured directly from 4 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.

Recent posts

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

#柬埔寨新闻 【肇事逃逸致公职人员死亡 司机父亲赔偿6万美元】 8月7日有记者爆料 一名27岁女司机Sam Mey Chou驾驶AVATR 11 SUV在超车时驶入对向车道 与一辆摩托车相撞导致公共工程和运输部官员Kuoch Limhan当场死亡 肇事司机与同行女子乘嘟嘟车逃离现场 警方确认其身份后于7月30日敦促其自首 次日被控交通肇事致人死亡及逃逸罪名 其父亲向受害者家属支付6万美元赔偿 事故发生于7月28日晚11时30分许 金边森速区Khmuonh乡1003号公路 死者为年仅35岁的政府官员 社交媒体曾曝光两名年轻女子逃离画面引发公众关注 司机自首后被审前拘留 法律程序仍在继续 父亲赔偿款可能影响后续量刑及家属谅解 这起案件突显柬埔寨交通肇事逃逸的法律及社会后果 小编PS:有钱也不能逃责! _ _ ✅投稿澄清爆料: @kq869 🤖投稿双向机器人: @tghotdnybot

7 Aug 2026, 17:29 UTC1 viewsread 7 August 2026

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

7 Aug 2026, 17:29 UTC1 viewsread 7 August 2026

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

7 Aug 2026, 17:23 UTC1 viewsread 7 August 2026

谷歌互推【频道B10】 👉关键词搜索 丨 全网搜片 1. 反差资源泄密资源 2. 艺术三级片春光 3. 体育|电竞|足球|NBA【每日推荐】 4. 裸贷校园贷泄密 5. 高端白富美 6. 及其反差❤️ 7. 全网最全的反差资源 8. 热门音乐|抖音神曲|BGM 9. 💋Ai自动去衣换脸(白嫖+赚钱) 10. 乖乖女的另一面 11. 日本AV|中文字幕|女优资源库 12. 海外素材库/人设 套图 13. 单纯可爱及其反差 14. 校园贷汇总 15. 日本无码破解av少妇人妻 16. 经典反差资源❤️ 17. 神仙文案集 一句入心 18. 内涵✨吃瓜娱乐🌱搞笑视频 19. 女优资源库 20. COS福利姬😘Cosplay😁角色扮演 21. 国产热门擦边短剧 22. 日本av(无码)(强奸)按摩 出轨(1) 23. 中文字幕|女优资源库 24. 成熟白皙反差资源 25. 裸贷校园贷系列 🌸🌸顶级颜值反差少女

7 Aug 2026, 17:00 UTC1 viewsread 7 August 2026
Photo

#泰国新闻 【拉抛啤酒厂火灾案调查完成 老板面临五项严重罪名指控】 警方8月7日已将拉抛啤酒厂火灾案卷宗移交检察官办公室 计划以五项严重罪名起诉45岁老板苏维查 包括过失纵火致多人死亡和重伤 无证经营娱乐场所及违规阻塞消防通道等 调查历时近一个月询问211名证人 认定火灾由电气系统改造引发短路导致隔音材料起火 火势迅速蔓延致30余人死亡 警方指出该场所桌椅摆放阻碍通行 消防出口被锁闭不符合法律规定 老板作为法人实体和个人拥有该啤酒厂 另有4至5名合伙人但无管理证据未被追诉 过失纵火罪最高可判7年监禁 过失致人死亡最高可判10年 警方强调已收集完整准确证据 七份卷宗全部移交检方等待最终定案和起诉 小编PS:这下老板跑不掉了! _ _ ✅投稿澄清爆料: @kq869 🤖投稿双向机器人: @tghotdnybot

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

#泰国新闻 【女儿争吵中刺伤海军军官父亲 警方介入调查】 春武里府梭桃邑县一名18岁女子8月6日晚与父亲发生激烈争吵后用剪刀刺伤其左侧肋骨及手臂 致其重伤倒地 现场血迹斑斑 52岁父亲为海军舰队司令部一级士官 被紧急送医救治 行凶女儿事后站在屋前明显受惊 警方已将其拘留并将以法律程序处理 调查显示两人争吵时家中无他人 母亲在芭堤雅工作 女儿有抑郁症史且曾多次与父亲争吵 警方将在伤者病情稳定后进一步询问并调查事件确切原因 剪刀作为证物被扣押 案件引发对家庭冲突和心理健康的关注 小编PS:家庭冲突太极端了! _ _ ✅投稿澄清爆料: @kq869 🤖投稿双向机器人: @tghotdnybot

7 Aug 2026, 15:33 UTC1 viewsread 7 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 成人内

7 Aug 2026, 15:17 UTC1 viewsread 7 August 2026
Photo

#网友反馈:金三角特区 万国楼下,有治安局上去抓人了,现场的警车前门一辆,后门一辆! 目前还在查监控,不知道是查毒还是有人举报打野办公!!

7 Aug 2026, 15:05 UTC1 viewsread 7 August 2026
Photo

#网友反馈:现在老挝金三角特区1号关口进特区需要持有效证件才能进入 要检查你的护照原件,p的护照不可以,如果没有原件,需要证明的你的护照有去签证!

7 Aug 2026, 15:00 UTC1 viewsread 7 August 2026
Photo

#泰国新闻 【清迈火锅汤底惊现蟑螂 店家只给10%折扣引众怒】 一名顾客在清迈某热门涮涮锅餐厅用餐时发现汤里有蟑螂 当场差点呕吐 店员仅道歉并提供10%折扣 发帖人批评店家缺乏责任感和沟通诚意 称其他餐厅遇同类情况通常会全额退款 此事在脸书清迈府群组引发热议 大量网友涌入评论区追问店名表达不满 涉事顾客未透露餐厅具体名称和地址 称希望唤起对卫生标准的重视而非针对特定店家 许多网友质疑10%折扣不合理 要求餐厅制定更明确的补偿机制 截至目前涉事餐厅尚未发表任何声明 该事件引发公众对餐饮业食品卫生和危机处理能力的讨论 小编PS:吃出蟑螂就打九折?太离谱了! _ _ ✅投稿澄清爆料: @kq869 🤖投稿双向机器人: @tghotdnybot

7 Aug 2026, 14:39 UTC1 viewsread 7 August 2026
Photo

#群友投稿:呆了两年的公司准备解散了。 早有预感,今年上半年很多有赔付的同事都跑掉了,加上项目一直走下坡路,公司也是入不敷出。不过公司也算是讲良心,赔付不要了还发遣散费,好聚好散。 如今的东南亚,真是寸步难行,每天提心吊胆的赚着底薪,手里没钱又没脸回家,不知道这种日子什么时候是个头,或许被抓了才能把一切的幻想和自尊放下。

7 Aug 2026, 14:34 UTC1 viewsread 7 August 2026
Video

泰国机场拒绝22名中国人登机,现场视频曝光 在通往客机的登机廊桥上,几名女性将机场工作人员推开。

Showing the 12 most recent of 37 posts we hold for @SEA0001. 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 — 76,157 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 80 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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“全网热搜社” (@SEA0001), 1,496 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/SEA0001.

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.