Channel
@tx9692
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
946subscribers
-24 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002184457586 |
|---|---|
| Type | Channel |
| Username | @tx9692 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/tx9692 |
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 11 August 2026 and assigned it the closest of 31 fixed categories, at 74% 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.
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 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @tx9692/22823 · this entry7 Aug 2026, 18:16 UTC | @tx9970/228207 Aug 2026, 18:16 UTC | 1.00 | under a minute |
| @tx9692/22824 · this entry7 Aug 2026, 18:31 UTC | @tx9970/228217 Aug 2026, 18:31 UTC | 1.00 | under a minute |
| @tx9692/22827 · this entry7 Aug 2026, 19:04 UTC | @tx9970/228247 Aug 2026, 19:04 UTC | 1.00 | under a minute |
| @tx9692/22828 · this entry7 Aug 2026, 19:24 UTC | @tx9970/228257 Aug 2026, 19:24 UTC | 1.00 | under a minute |
| @tx9692/22831 · this entry7 Aug 2026, 19:53 UTC | @tx9970/228287 Aug 2026, 19:53 UTC | 1.00 | under a minute |
| @tx9692/22832 · this entry7 Aug 2026, 20:07 UTC | @tx9970/228297 Aug 2026, 20:07 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @tx9970 | 10 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @tx9970 (9–1) |
| @tx9693 | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (9–0) |
| @p5559 | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @p5559 (9–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. 18 of the 18 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 11 comparable posts for this entry, running 7 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.
Across the whole group of 4, the earliest publisher we hold is @p5559. 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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 10:54 | 946 | -24 |
| 8 Aug 2026, 00:46 | 970 | no change |
| 7 Aug 2026, 19:05 | 970 | first reading |
11 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 1 pageof 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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 11 (7 August 2026 – 7 August 2026) |
| Views total | 11 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 00:46 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 3 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.
东帝汶警方捣毁一非法网络赌博及诈骗窝点，抓获13名中国籍嫌疑人！ 东帝汶媒体8月7日报道： 东帝汶刑事调查局联合移民局、法证小组、警务情报局于8月6日晚间在帝力梅蒂奥特（Metiaut）地区开展联合清查行动，对一处居民住宅开展突击搜查，抓获15名涉嫌非法网络赌博、电信诈骗的外籍嫌疑人。 据了解，本次行动共抓获外籍人员15名，其中13人为中国籍、2人为菲律宾籍。警方初步查明，该团伙利用租住民宅设立非法网络赌博及电信诈骗呼叫中心，实施违法犯罪活动。 执法现场查获大量涉案物品，包含2套星链（Starlink）网络设备、15本护照以及多部作案手机。 完成现场勘查与身份核验工作后，警方已将全部嫌疑人押解至东帝汶国家警察凯科利（Kaikoli）警察指挥部予以拘留，依法执行最长72小时羁押。 案件后续将移交公共检察院，继续推进调查及相关司法程序。 大事件➡️ @tx969 投稿➡️@tx9695
#泰国新闻 泰国大城府警方突查一家湖南中餐厅，发现店内设有麻将房。 5名中国籍人员因涉嫌组织及参与赌博被抓；另有8名外籍人员涉及无证工作、超范围工作、未申报更换雇主或非法居留。警方目前还在检查餐厅股东结构、资金流向及是否存在泰国人替外国人代持股份的问题，但“代持”尚未正式认定。
#网友投稿：我可能一直有性方面成瘾的情况，也就是性瘾。之前在国内的时候，我都是跟女朋友一天要干三次。我刚开始以为，是因为我身边有女人的缘故。 但是，我来到东南亚之后，还是这样。不喝酒的时候还好，喝完酒就想去嫖娼。平时不喝酒，也会想着打飞机。刚开始都是几天打一次，最近几个月基本上每天都打，白天一次，晚上一次。 有的时候赌博输了，心情烦躁，睡不着，要打个飞机才睡得着。很多时候都是这样。我现在感觉身体都虚透了，但是我还是忍不住打。 每次都是自己给自己洗脑，都告诉自己：“反正休息睡一觉精子量明天也会恢复回来。” 但是，我能感觉到我现在身体很差劲。走路走两步就会喘，在一个闷热的环境下，待一分钟就要出汗，而且一直出。 前两天，我在TK上约了小姐姐出来，饭吃好了带回房间，前戏弄了有五分钟，当时隐隐约约感觉自己就快忍不住了，要射了，一直再忍，最后实在忍不住了，裤子刚脱下来就感觉牛子传来一股高压炙热的温度，我还没有反应过来就射在了小姐姐…
网友：最近有一伙 职业偷东西的 外围女 来迪拜了的 昨天某别墅遇到两个，他们会先说自己掉了5万，一共10万，然后去搜别的女孩行李箱和钱包，在这个过程当中他们，很快的办法把钱塞进裤兜里，但实际上他们这笔50,000根本来路不明，而且偷钱女孩子可能由于剧情没有编号，满嘴跑火车 第一他们会说在上海地下钱庄换的 第二他们会说跟哪个香港大哥睡觉，认识了很多年，挣了他很多钱，所以才来迪拜 第三就会说是你安排给他的客人 谎言一串又一串，反正就是没有一个准确答案钱也不知道来路就说自己的钱丢了，想去搜别的包，请各位嫖客们注意自己的贵重物品，请各位外围穿的妹子们管好自己的现金和首饰 大事件➡️ @tx969 投稿➡️@tx9695
爆料：韩国足协多次为外国裁判提供性服务 据韩联社8月6日报道，韩国政府审计报告显示，韩国足协于10多年前多次在国家队比赛前为外国裁判提供性服务。 报道称，由韩国文化体育观光部编制的审计报告指出，韩国足协安排外国裁判在首尔及其他举办国际比赛的城市到按摩院和其他成人场所接受性服务，并支付了相关服务费用。 报告显示，这些比赛包括2012年伦敦奥运会预选赛和2014年巴西世界杯预选赛。 报道还称，大约有十几名裁判和比赛协调员在7场比赛中接受了韩国足协的“特殊服务”。这些官员来自日本、阿联酋、伊朗、巴林和乌兹别克斯坦。
#群友分享：昨晚打PG，上600打到2000，没下，又送给狗子庄1000。下1000赢400，喊朋友出来吃饭，消费200多，又去打了一炮，花600，还倒贴。 还不如不赢，都让弟弟享受了，弟弟爽了，钱没了😭。干了两炮，给她干高潮了两次，没射，又让我后入干了一炮。 关注曝光吧几年了！分享一下：现在大环境不好，有钱还是存起来，管住自己的小弟弟。做爱一时爽，做完泪汪汪。实在忍不住，打个飞机泄泄火。不要像我一样，管不住自己的小弟弟。 大事件➡️ @tx969 投稿➡️@tx9695
特朗普再签行政令限制美国出生公民权 美国总统特朗普 8 月 6 日在白宫签署两项行政令，再次尝试限制出生公民权。其中一项扩大了父母双方均非美国公民时子女不具出生公民权的情形，涉及外国恐怖组织成员、外国政府雇员等；另一项禁止所谓「生育旅游」，即孕妇赴美产子以使婴儿获得国籍。特朗普称此举早该实施，并批评最高法院此前否决其废除这一 150 年政策的尝试。 今年 6 月 30 日，美国最高法院以 6 比 3 裁定特朗普 2025 年上任首日签署的行政令违宪，确认出生公民权仍是法律。白宫辩称新令通过重新解释出生公民权的少数历史例外，不属该裁决管辖范围。法律专家表示新令部分内容存在严重宪法问题，移民权益组织则指责其意在规避最高法院裁决，美国公民自由联盟预测其将在法庭上败诉。
土耳其6134人国籍被撤销 涉嫌违规取得公民身份。 土耳其内政部宣布，在对后续取得土耳其国籍人员进行审查后，共有6134人因被认定存在违规取得国籍的情况，其土耳其国籍已被撤销或收回。 官方表示，这些案件主要涉及以下几类问题： - 使用伪造文件申请 - 提供虚假或不实信息； - 不符合土耳其法律规定的入籍条件； - 安全背景调查中发现此前未披露或后续查明的违规情况。 土耳其内政部强调，入籍审核和后续监督将持续进行。凡是被查明通过违法或违规方式取得土耳其国籍的人员，都将依法采取相应行政措施，包括撤销国籍。
迪拜海关成功拦截一起走私黄金案：有人把460克金熔成细条，藏进行李箱框架里。 迪拜海关8月6日在社交媒体上公布了这起案件。走私者把大约半公斤（460克）的24K纯金熔化后做成细长的金条，偷偷藏在旅行箱的框架夹层里，企图蒙混过关。 海关检查人员通过电子安检设备发现异常，随后对行李箱进行人工检查，成功找出藏在框架里的金条并予以扣押。 海关强调，这起查获说明检查人员训练有素、系统先进，即使是比较隐蔽的藏法也能查出来。他们也提醒公众：千万别随便帮别人带行李，因为你要对你所携带的一切物品负法律责任。阿联酋联邦海关也一再劝告旅客，不要在不了解内容的情况下接收陌生人或朋友的行李，否则可能面临罚款、监禁，甚至两者并罚。
#缅甸资讯：景栋打击网络诈骗团伙，抓获156人并缴获大量作案工具 CNA2026年8月7日报道：据了解，缅甸掸邦（东部）景栋镇区一处非法电信网络诈骗及赌博窝点遭安全联合部队突击搜查，抓获包括多数外国人在内的156人。 报道称，该窝点位于果卡（Kat Hpa）村行政村瑙雷（Nawng Len）村附近的某一园区内，由6栋建筑组成。根据热心民众提供的线索，当局于8月7日上午前往进行了突击检查。 在突击搜查行动中，共抓获156人，其中中国籍144人、老挝籍1人、缅甸籍11人。同时，还缴获了大量作案工具，包括658部手机、134台一体机电脑、28台笔记本电脑以及13台“星链”（Starlink）卫星互联网设备等。 相关部门表示，对被捕人员的审讯工作结束后将依法予以追责，缴获的物品也将按照相关程序进行后续处理。 大事件➡️ @tx969 投稿➡️@tx9695
超10亿微信支付用户可在越南使用二维码付款 越媒报道：8月6日，越南国家支付公司NAPAS、越南投资发展银行BIDV以及微信支付，联合宣布推出越南‑中国跨境二维码支付服务。 微信支付是继银联、支付宝之后，第三家接入NAPAS跨境二维码支付体系的中国支付平台。打通之后，微信支付用户可扫描越南商户VietQRGlobal码消费，强化两国数字支付基础设施互联互通。 交易依托NAPAS和微信支付的对接通道，搭配BIDV清算系统完成处理。这项服务面向超10亿微信支付用户，方便中国游客在越南的零售店、餐厅、酒店、民宿、旅游景区完成付款。 越南国家银行支付司司长范俊俊在发布仪式上表示：越中二维码互通，不只是新增一种支付手段，更是建设安全便捷跨境支付生态的重要里程碑，助力两国经贸、投资与旅游交流。 他提到，在数字化快速发展的背景下，央行的目标是让跨境支付尽可能像境内支付一样顺畅，让技术成为国与国旅游贸易的桥梁，而不是阻碍。
Showing the 11 most recent of 11 posts we hold for @tx9692. 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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“东南亚大事件-新加坡” (@tx9692), 946 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/tx9692.
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.