Telegram RegisterThe public register of Telegram
Telegram profile photo for 柬泰马反诈新闻简讯

Channel

柬泰马反诈新闻简讯

@tgsfaa

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

22,077subscribers

-4,236 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002627320408
TypeChannel
Username@tgsfaa
Description本简讯汇总柬埔寨、泰国、马来西亚近期时事资讯,涵盖三国边境动态、政策调整、经贸往来、社会民生及区域合作等内容,内容精炼扼要,实时梳理中南半岛三国最新发展态势,便于快速掌握东南亚三地权威时事动态。 投稿 @jiaofu05
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/tgsfaa

Topic

International 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 49% 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.

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 in near-verbatim form on 3 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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
@DNYsvip888/1248329 Aug 2026, 10:41 UTC@tgsfaa/5456 · this entry29 Aug 2026, 10:45 UTC1.005 minutes
@DNYsvip888/126121 Sept 2026, 07:42 UTC@tgsfaa/5568 · this entry1 Sept 2026, 07:42 UTC1.00under a minute
@DNYsvip888/1385527 Sept 2026, 03:12 UTC@tgsfaa/6625 · this entry27 Sept 2026, 03:12 UTC1.00under a minute
@DNYsvip888/1388027 Sept 2026, 13:05 UTC@tgsfaa/6647 · this entry27 Sept 2026, 13:05 UTC1.00under a minute
@DNYsvip888/142036 Oct 2026, 01:41 UTC@tgsfaa/6909 · this entry6 Oct 2026, 01:41 UTC1.00under a minute
@DNYsvip888/143329 Oct 2026, 09:09 UTC@tgsfaa/7019 · this entry9 Oct 2026, 09:09 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@DNYsvip8881,701 (8/8 hand-verifiable sample passed)1.00under a minute@DNYsvip888 (1,693–8)
@seath91 (8/8 hand-verifiable sample passed)0.87under a minute@seath (53–38)
@dongnanya2995 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (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. 1,748 of the 1,748 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 1,875 comparable posts for this entry, running 7 August 2026 to 17 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.

  • 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @DNYsvip888. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

22,07726,31324,1957 August 202616 November 2026
64 measurements spanning 101 days, net -4,236. 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 21,442–26,948 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
16 Nov 2026, 11:5922,077-178
13 Nov 2026, 01:4722,255-73
10 Nov 2026, 15:4722,328-77
9 Nov 2026, 00:1622,405-89
7 Nov 2026, 18:4722,494-43
6 Nov 2026, 15:5822,537-21
5 Nov 2026, 17:2922,558-28
4 Nov 2026, 19:5922,586-51
3 Nov 2026, 19:1522,637-129
2 Nov 2026, 21:5722,766-22
1 Nov 2026, 21:4822,788-72
31 Oct 2026, 18:2122,860-36
30 Oct 2026, 21:0522,896-34
29 Oct 2026, 20:5022,930-47
28 Oct 2026, 19:0922,977-41
27 Oct 2026, 16:2823,018-35
26 Oct 2026, 13:0623,053-25
25 Oct 2026, 09:5723,078-45
24 Oct 2026, 08:0623,123-22
23 Oct 2026, 06:5823,145first reading

Engagement

2,013 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 126 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.005%
avg views ÷ 22,077 subscribers
Avg views / post
1.1
538 posts measured
Reaction rate
100.0%
reactions ÷ views · ER floor
Posts in window
538
of 2,013 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. It is computed over the 5 of 538 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held2,013 (7 August 2026 – 17 November 2026)
Views total594
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 15:38 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

Photos
≈7,650
Videos
≈273
Links
≈330

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.

Reaction mix

5 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 20.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍾120.0%
👍120.0%
😈120.0%
😨120.0%
🫡120.0%

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 5 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 5 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 30 September 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 538 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).

17 Nov 2026, 15:27 UTC1 viewsread 17 November 2026
Photo

【#越南】【🏥 胡志明市燃气店爆炸伤者逐步康复,1人仍危重】 据越南VnExpress 11月16日报道,胡志明市多家医院当天更新11月13日新顺坊Bui Van Ba路燃气店爆炸伤者情况。经过三天治疗,多名伤者状况趋稳,但一名36岁男性全身烧伤面积达90%,其中三度烧伤约38%,并伴呼吸道损伤,入院后接受气管插管和呼吸机支持,目前仍然危重。另一名33岁男性曾被倒塌房屋压伤,头部、颈椎及腿部受伤,并出现急性肾衰竭,治疗后肾功能已恢复正常。一名17岁店员及一名路过的56岁女子在115人民医院治疗,情况稳定,预计数日内出院。事故共造成2人死亡、两栋房屋倒塌及另外5栋受损。​ #越南社会 #燃气爆炸

17 Nov 2026, 14:57 UTC1 viewsread 17 November 2026
Photo

【#泰国】【🔥 普吉芭东摩托车租赁店火灾致11死16伤】 据泰国The Thaiger 11月16日报道,当日凌晨约3时15分,普吉府卡图县芭东Phang Muang Sai Kor路一栋六层建筑起火。建筑底层为摩托车租赁店,停放逾100辆摩托车,上层为出租房。6辆消防车约一小时后控制火势,事故造成11人死亡、16人受伤;伤者包括15名泰国人和1名缅甸人,无游客伤亡。遇难者中1人在三楼被发现,其余10人在五楼,多数人疑因吸入浓烟丧生。警方正调查建筑外电线杆短路的可能性,但起火原因尚未确认。普吉府尹到场指挥搜寻,总理阿努廷要求迅速调查,若发现安全违规须依法处理。​ #泰国社会 #普吉火灾

17 Nov 2026, 14:17 UTC2 viewsread 17 November 2026
Photo

【#印度尼西亚】【🎧 警员EHS涉嫌非法窃听将接受职业道德听证】 据印尼ANTARA通讯社11月16日报道,印尼国家警察职业道德委员会定于11月17日就警员EHS涉嫌非法窃听及不当访问系统一事举行听证。警方介绍,审查内容涉及滥用职权、缺乏职业操守、未依程序行事,以及涉嫌合谋非法访问等问题,与其在警察刑事侦查局行动监测部门任职期间所拥有的系统访问权限有关。相关刑事案件已将LSP、AS、EH和SU四人列为嫌疑人,其中AS于11月10日被不光彩解职后已提出上诉。此次职业道德听证与刑事调查属于不同程序,听证安排不代表EHS已被认定违法,最终责任仍须依据调查结果和相应裁决确定。 #印尼非法窃听 #警察纪律审查

17 Nov 2026, 13:13 UTC1 viewsread 17 November 2026
Photo

【#印度尼西亚】【📋 Firli Bahuri涉嫌勒索案等待补证讯问安排】 据印尼ANTARA通讯社11月16日报道,雅加达都会警察局仍在等待前肃贪委员会主席Firli Bahuri方面确认到案时间,以继续办理其涉嫌勒索前农业部长Syahrul Yasin Limpo一案。警方表示,正与Firli的律师协调后续检查安排,此次讯问旨在完成检方提出的P19补充案卷要求,即进一步完善证据和案件材料。报道并未确认Firli已于11月16日到案,因此不能把警方的协调进展表述为已经完成讯问。警方称,将在时间确定后依法开展补证工作,案件仍处于侦查及案卷完善阶段,相关指控尚未经法院最终审理认定。​ #FirliBahuri #印尼勒索案

17 Nov 2026, 12:40 UTC1 viewsread 17 November 2026
Photo

【#越南】【💰 胡志明市警方调查两起月息最高40%高利贷案】 据越南《青年报》11月16日报道,胡志明市警方正调查两起“民事交易中的高利贷”案件,并寻找曾向Phạm Văn Cường、Đỗ Xuân Sơn和Đào Thanh Hải借款的人员。其中,Cường所涉案件于9月8日在新山坊Tân Canh街78—80号前被发现;Sơn与Hải所涉案件则于10月2日在黎文士街424号前被发现。调查称,涉案人员通过派发“快速金融支持”卡片招揽借款人,口头约定21至25天的按日分期还款,月息为25%至40%,相当于越南民法典允许利率的15至20倍。警方呼吁相关借款人联系调查人员,提供借款及还款资料,以协助确定案件规模。​ #越南高利贷 #胡志明市警方

17 Nov 2026, 11:59 UTC1 viewsread 17 November 2026
Photo

【#印度尼西亚】【👊 雅加达Petamburan群殴事件5人被捕】 据印尼ANTARA通讯社11月16日报道,雅加达警方已控制5名涉嫌参与Petamburan群殴事件的人员,并继续对其展开调查。事件发生于11月15日晚,地点位于雅加达中区Tanah Abang的Jalan Petamburan一带。初步信息称,有人向另一群体及居民区方向发射大型烟花,随后引发互相攻击和破坏。居民铁栏、家具、两辆手推车、展示柜、防水布、汽车玻璃、摩托车及街边摊位等受到不同程度损坏。警方到场后平息冲突并展开取证,目前尚未公布5人的最终法律处理结果。当局正核对现场视频、证人陈述及损坏情况,以厘清各人具体行为。​ #雅加达群殴 #公共秩序

17 Nov 2026, 11:19 UTC1 viewsread 17 November 2026
Photo

【#越南】【🚕 男子怀疑车辆擦碰砸出租车玻璃并殴打司机】 据越南VnExpress网站11月16日报道,以安地区警方正调查一起因疑似交通擦碰引发的砸车及伤人事件。11月15日17时以后,Võ Minh Tâm认为一辆网约出租车与其妻子驾驶的摩托车发生擦碰,遂追赶并拦停车辆。据警方初步调查,Tâm向车辆投掷手机、打砸车窗玻璃,随后将司机Trịnh Duy Thực拉出车外并实施殴打,导致司机手部受伤。现场视频显示,周围人员曾试图制止冲突。警方正按扰乱公共秩序及故意损毁财物等迹象核查事件,同时调查双方车辆是否确曾发生碰撞。相关行为性质和责任仍待进一步调查认定。​ #越南砸车伤人 #交通冲突

17 Nov 2026, 10:39 UTC1 viewsread 17 November 2026
Photo

【#印度尼西亚】【🪙 海关查获21.8公斤拟非法输往马来西亚黄金】 据印尼ANTARA通讯社11月16日报道,马辰海关在南加里曼丹破获两起企图通过航空渠道非法携带黄金出境案件,累计查获21.8公斤黄金,估值约525亿印尼盾,潜在出口税约52亿印尼盾。11月5日,执法人员先从4名印尼女性乘客身上查获4.2公斤黄金。11月12日,RN、RL和N三人准备搭乘AK-441航班前往吉隆坡时,被查出在身体部位藏匿17根金条,三人分别携带5.8公斤、5.7公斤和6.1公斤。检测显示,涉案黄金纯度均超过99%。第二次行动中的3人已被列为嫌疑人,案件正按非法出口方向深入调查。​ #印尼黄金走私 #马辰海关

17 Nov 2026, 10:02 UTC1 viewsread 17 November 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7219632682

17 Nov 2026, 10:02 UTC1 viewsread 17 November 2026
Photo

【#马来西亚】【🚨 古晋综合治安行动逮捕3名涉毒男子】 据马来西亚《砂拉越论坛报》11月16日报道,古晋警方在11月14日Sekama警区辖区内开展行动时,逮捕3名涉嫌毒品犯罪的男子,并依1952年《危险药物法令》第15(1)(a)条采取进一步措施。古晋警区主任Alexson Naga Chabu介绍,警方于11月14日和15日凌晨零时至清晨5时,分别在Sekama及Tabuan Jaya警区开展综合犯罪预防行动,共检查437人,包括317名男子和120名女子;同时检查388辆交通工具,并针对各类交通违法行为发出83张传票。警方表示,将继续在犯罪风险较高地区加强针对性巡查,并呼吁公众提供犯罪线索。​ #古晋涉毒行动 #马来西亚治安

17 Nov 2026, 09:26 UTC1 viewsread 17 November 2026
Photo

【#越南】【🏥 河内肺科医院前副院长涉伪造164份病历被诉】 据越南《青年报》11月16日报道,北宁省人民检察院已就伪造重症肺结核病历案起诉47人,其中包括河内肺科医院前副院长Hoàng Văn Huấn,其被控受贿及执行公务时伪造文件。检方指控,2021年至2025年间,Huấn指使下属为114人制作164份虚假病历,以帮助服刑人员获得暂缓执行刑罚等待遇。涉案手法包括替换检验样本、干预胸片检查、让人员穿病号服和输液摆拍,以及虚构住院、治疗和护理资料。Huấn被指收受11.8亿越南盾,调查期间已退还8亿越南盾。案件涉及医疗、司法及执法环节,多名涉案人员的责任仍在依法处理。​ #越南假病历案 #医疗腐败

17 Nov 2026, 08:52 UTC1 viewsread 17 November 2026
Photo

【#印度尼西亚】【💊 巴厘岛警方接手侦办3起移交毒品案】 据印尼ANTARA通讯社11月16日报道,巴厘岛省警察局正在侦办由国家警察刑事侦查局于11月1日移交的3起毒品案件,涉及DVG、NPA和VA三名嫌疑人,其中NPA和VA所涉案件与Kerobokan监狱有关。警方公布,三案合计查获冰毒毛重16.52克、净重10.48克,另有5片摇头丸,毛重2.49克、净重2.09克,以及0.94克疑似含毒品的绿色粉末。办案人员正分别核查毒品来源、持有者之间的关系及监狱内外的联络情况,并将对疑似毒品粉末作进一步检验。案件仍处于侦查阶段,相关人员的法律责任尚待司法程序认定。​ #巴厘岛毒品案 #监狱犯罪调查

Showing the 12 most recent of 2,013 posts we hold for @tgsfaa. 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.

Mentions

Named by 1 registered channel — 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.

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.

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

“柬泰马反诈新闻简讯” (@tgsfaa), 22,077 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/tgsfaa.

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.