币安安全公告:请 iPhone 用户检查是否安装 FomoPeek,其可利用 iOS 漏洞获取设备最高权限 Ps:现在病毒迭代是越来越快了 追着版本更新… 关注新闻大事件👉 @Tx939 投稿👉 @yoozb
😁45🔥43❤42👍38🎉34🤩34

Channel
@dashijianx
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
225,021subscribers
-2,551 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001887655999 |
|---|---|
| Type | Channel |
| Usernames | @dashijianx @tx939 @y9n99 |
| Description | 东南亚大事件 欢迎加入智慧天下联盟 天下社区:华人求助贴 永久免费 全网覆盖 广告招商/商务合作: @yoozb 天下联盟导航: @Txtot This group strictly adheres to the relevant regulations and guidelines of the @Telegram community. It is strictly prohibited to spread false rumors, firearms and ammuniti |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 94 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/dashijianx |
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 8 August 2026 and assigned it the closest of 31 fixed categories, at 81% 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 1 other registered channel. 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 |
|---|---|---|---|
| @dashijianh/240977 Aug 2026, 08:11 UTC | @dashijianx/30737 · this entry7 Aug 2026, 08:11 UTC | 1.00 | under a minute |
| @dashijianh/241027 Aug 2026, 08:41 UTC | @dashijianx/30746 · this entry7 Aug 2026, 08:41 UTC | 1.00 | under a minute |
| @dashijianh/241077 Aug 2026, 09:11 UTC | @dashijianx/30752 · this entry7 Aug 2026, 09:11 UTC | 1.00 | under a minute |
| @dashijianh/241417 Aug 2026, 12:56 UTC | @dashijianx/30800 · this entry7 Aug 2026, 12:56 UTC | 1.00 | under a minute |
| @dashijianh/241457 Aug 2026, 13:11 UTC | @dashijianx/30805 · this entry7 Aug 2026, 13:11 UTC | 1.00 | under a minute |
| @dashijianh/241487 Aug 2026, 13:26 UTC | @dashijianx/30809 · this entry7 Aug 2026, 13:26 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @dashijianh | 10 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (7–3) |
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. 3 of the 3 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 14 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 2, the earliest publisher we hold is @dashijianx — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 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 1 other registered channel, 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 |
|---|---|---|
| 18 Sept 2026, 19:56 | 225,021 | +1,786 |
| 17 Sept 2026, 21:18 | 223,235 | +12,095 |
| 17 Sept 2026, 10:15 | 211,140 | -338 |
| 16 Sept 2026, 12:17 | 211,478 | -391 |
| 15 Sept 2026, 15:59 | 211,869 | -248 |
| 15 Sept 2026, 06:38 | 212,117 | -427 |
| 14 Sept 2026, 16:18 | 212,544 | -599 |
| 13 Sept 2026, 23:39 | 213,143 | -89 |
| 13 Sept 2026, 16:22 | 213,232 | -326 |
| 13 Sept 2026, 00:18 | 213,558 | +1,873 |
| 12 Sept 2026, 09:21 | 211,685 | -511 |
| 11 Sept 2026, 19:18 | 212,196 | +1,722 |
| 11 Sept 2026, 04:01 | 210,474 | +1,755 |
| 10 Sept 2026, 05:17 | 208,719 | +834 |
| 9 Sept 2026, 07:02 | 207,885 | +1,935 |
| 8 Sept 2026, 03:00 | 205,950 | +398 |
| 7 Sept 2026, 00:57 | 205,552 | -4,244 |
| 5 Sept 2026, 20:38 | 209,796 | -355 |
| 5 Sept 2026, 02:42 | 210,151 | -159 |
| 4 Sept 2026, 10:00 | 210,310 | first reading |
1,042 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 96 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 655 of 674 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 19 September 2026 |
|---|---|
| Posts held | 1,042 (7 August 2026 – 19 September 2026) |
| Views total | 2,049,347 |
| Reactions total | 185,925 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Sept 2026, 19:28 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.
Lifetime counters from Telegram’s own channel header, read 19 September 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.
Measured directly from 285 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.
270,250 reactions across 897 posts, in 13 distinct kinds. The most used accounts for 14.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 40,289 | 14.9% | |
| 🔥 | 40,222 | 14.9% | |
| 👍 | 40,114 | 14.8% | |
| ❤ | 39,923 | 14.8% | |
| 🎉 | 39,867 | 14.8% | |
| 👏 | 29,562 | 10.9% | |
| 🥰 | 29,562 | 10.9% | |
| 🤩 | 10,624 | 3.93% | |
| ⚡ | 27 | 0.01% | |
| ❤🔥 | 20 | 0.007% | |
| 😍 | 20 | 0.007% | |
| 💯 | 18 | 0.007% | |
| 🤔 | 2 | 0.001% |
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 901 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 270,250 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 8 August 2026 to 19 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.
币安安全公告:请 iPhone 用户检查是否安装 FomoPeek,其可利用 iOS 漏洞获取设备最高权限 Ps:现在病毒迭代是越来越快了 追着版本更新… 关注新闻大事件👉 @Tx939 投稿👉 @yoozb
😁45🔥43❤42👍38🎉34🤩34
FomoPeek绝对是针对币圈有预谋的精准收割 感觉和前一段时间的灯塔投毒事件类似,都是通过一些羊毛吸引用户去点击或者下载然后被盗 不过这次FomoPeek的投毒力度更大、范围更广,受影响用户数量之多,他们为了投毒竟然还上架了苹果APP,利用了IOS系统的漏洞 这次受伤最深的还是撸毛用户,辛辛苦苦撸的钱因为几U全被盗了,属实是你要人家的利息,人家要你的本金 Ps:还有前段时间 台子送彩金骗下载盗U的 也有很多人被割了一波 … 关注新闻大事件👉 @Tx939 投稿👉 @yoozb
🎉30❤29🤩28👍24🔥21😁19⚡1
https://t.me/pl555
🎉33🤩31👍25🔥24❤21😁21
男子自导自演“被绑架至国外电诈园区”向父亲索要2万元,警方依法行政拘留 9月8日22时许,谢先生到海南省东方市公安局大田派出所报警称,自家小孩被绑架至国外诈骗园区,向其索要两万元钱赎金,否则后果严重。 民警接警后,一边安抚谢先生情绪,一边详细了解事件情况,迅速开展走访、研判,于2026年9月16日,在海口市某公寓房内找到谢某。 经调查,谢某因经济拮据,其在某音短视频平台看到有诈骗园区,向国内家属勒索赎金的视频内容后,便模仿诈骗园区管理人员,虚构其被绑架到国外园区,伪造自己被殴打的图片,通过微信发给其父亲谢先生,要求父亲谢先生转账两万元钱,谢某到案后,对自己涉嫌诈骗的事实供认不讳,公安机关依法对谢某处行政拘留处罚。 警方提醒:网络空间不是法外之地,编造虚假信息、虚构事实骗取他人财物,必将承担相应法律责任。 家庭成员之间应加强沟通,遇到类似“绑架”“勒索”等信息,务必第一时间报警核实,切勿盲目转账,以免造成财产损失。 P…
😁26🔥23❤22👍19🎉16🤩15⚡1
东南亚大事件🅥 @YOSOU 搜索冠名 pinned a photo
🏆 赚赚娱乐 & 金宝娱乐 🍄🍄🟫🐚🪸🪨 ✨ 顶级线上娱乐平台联合呈现 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 😆🥹😅😂🤣🥲☺️😊 🎮 海量热门游戏 一站畅玩 ⚽ 全球体育赛事 实时开赛 🎰 PG|PP|CQ9|JDB 等热门电子 🎥 真人视讯|🃏棋牌|🎣捕鱼|🎱彩票 💰 高赔率 · 高爆率 ⚡ 极速存提 · 稳定流畅 🔐 安全稳定 · 官方直连 📲 官方机器人 🔶 赚赚娱乐:✈️ @ZZYL 🔷 金宝娱乐:✈️ @JBAO 🎁 新人福利不断 💎 每日频道不定时红包雨 🚀 百万美金秒提款,玩得放心 🔥 两大品牌,一次满足! 💰 玩游戏,就选赚赚娱乐 & 金宝娱乐!
👍29🎉27❤26😁23🤩20🔥17
#网友投稿:菲律宾马卡蒂欢乐颂中国超市,可能不会开门了 昨天总共抓了6个人,中国老板和老板娘,还有4个小菲员工都抓了。应该短时间开不了了,大概率直接关门。本地员工也抓了,我看那个部门应该是菲律宾肉联的,就是菲律宾肉品监管局 他们被抓的原因是肉类产品不合格 还有就是走私烟 中国药品。 总有头铁的中国人觉得铁拳不会砸到自己头上?也不看看现在中菲关系烂成啥逼样了都。中资钢铁厂抓了50多个,这他妈可是国有企业啊。你一个开超市的小卡拉米算个啥? 都说顺势而为,识时务者为俊杰,总有人赌自己没事?在此奉劝那些还在菲律宾做实体生意的,尽快撤!你们的目标太大了,毕竟有店在那里。快年底了,菲狗借着小马的反华大旗肯定又要敲诈勒索一批中国人,希望大家都注意安全吧。 关注新闻大事件👉 @Tx939 投稿👉 @yoozb
🎉51❤45🔥43🤩43😁42👍38
#群友投稿:那些年,东南亚人事给我们画过的饼,大家都听说过哪些? 我们这里出入自由,不禁足,公司管理人性化,没有小黑屋。 公司没有业绩压力,绝对正规,来了你就知道。老板特别惜才,优秀员工重点培养,员工晋升特别快。 业绩全靠自己,公司从来不拖欠工资,工资绝对按时发。只要肯努力,一个月买车,两个月买房,几个月赚够钱回国直接躺平。 手机可以正常使用,跟家里联系完全没问题,管理松,大家都很自由。这里美女帅哥多,工作环境特别好,来了就是一家人。(不足的欢迎补充) 关注新闻大事件👉 @Tx939 投稿👉 @yoozb
🎉37❤34👍33🔥33🤩33😁31👏1🥰1
马来西亚鑫盛国际KTV遭联合突击检查 马来西亚移民局+警方突袭刚开业的鑫盛国际KTV,现场抓获多名顾客,部分人趁乱逃走。 近期大马严查娱乐场所,网传这类场所的摇头活动风险极高。带走都是要被拘留,严重的还会被遣返 关注新闻大事件👉 @Tx939 投稿👉 @yoozb
❤51🎉40🔥37🤩37👍34😁28
#群友爆料:以前孟波代理星星,鸡爷代理,工资不结算,鸡爷直接拉黑我。 本着想解决的态度联系,结果一个个都不理不睬,会做人👍,直接曝光。盘口业绩几个亿,在那边说没钱,现在不需要结算工资了。 这一体系是孟波海哥旗下的,七匹狼是第一大代理。凡和他们有仇的,可以来联系我,我免费把他们所有信息、家庭住址发你们。 关注新闻大事件👉 @Tx939 投稿👉 @yoozb
🎉59👍50❤47🤩45😁44🔥41
#斯里兰卡资讯 斯里兰卡一名警长涉嫌持枪抢劫酒铺,2人被捕 斯里兰卡警方表示,亭可马里警方在接到报警后,仅用约1小时就抓获两名涉嫌持枪抢劫酒铺的嫌疑人。 警方称,案件发生在18日晚,地点位于亭可马里阿努拉达普勒路口附近的一家酒铺。两名嫌疑人持T-56步枪闯入店内,威胁店员后抢走现金和一瓶烈酒。 当时,其中一人正在柜台拿钱,一名店员试图阻止他逃跑。另一名持枪嫌疑人随后朝店铺屋顶开了一枪,试图吓退店员。店员随后逃离现场,两人带着现金和酒逃走。 警方接到消息后立即展开追捕,并在案发约1小时后,于乌普韦利警察分局辖区内一处临时住宿地点将两人抓获。 警方确认,涉案的T-56步枪原本配发给乌普韦利警察局。 其中一名嫌疑人为乌普韦利警察局警长,目前在基利蓬奇马莱地区的军械库工作;另一人为该警长的密切关系人。 两名嫌疑人分别为54岁和61岁,均为哈克马纳居民。 警方还缴获了疑似从酒铺抢走的1.15万斯里兰卡卢比现金、一辆疑似作案时…
😁33🎉27🔥27👍25🤩24❤23
ISP-Myanmar:果敢、佤邦诈骗集团向掸邦南部和东部转移 据ISP-Myanmar消息,“1027行动”后,果敢地区和佤邦自治区的电信诈骗团伙正向掸邦南部和东部转移业务,最集中出现在当阳、垒恰、大其力和木姐。 报告称,数据仅取自2023年1月至2026年4月7日的公开资源,受数据获取限制和方法差异影响,可能存在偏差。 此外,ISP-Myanmar 9月7日曾报道,掸邦霍榜、垒恰、南散、迈耶、当阳、景栋、勐撒、勐统、大其力等至少17个镇区中,仍有至少25个诈骗窝点在运作。 关注新闻大事件👉 @Tx939 投稿👉 @yoozb
🔥40❤35👍35🤩32🎉29😁29
Showing the 12 most recent of 1,042 posts we hold for @dashijianx. 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.
@dashijianx edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Named by 12 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 11 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“东南亚大事件🅥” (@dashijianx), 225,021 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/dashijianx.
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.