#印度新闻 印度中央工业安全部队、机场运营商、航空公司、地方政府、医疗服务、警察、消防、情报机构、民航安全局、民航总局、国家安全卫队及陆军等多个部门共同参加联合演习,展示了跨部门协调能力和应急行动准备水平。
Signed 先锋(24小时在线)

Channel
@ddmm789
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
65,440subscribers
+8,002 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001667567411 |
|---|---|
| Type | Channel |
| Username | @ddmm789 |
| Description | 🌍面向全球聚焦 🤝投稿澄清商务合作 @w8090w 全网大事件,专注于海外华人最新动态,悬赏通缉,揭露事实,曝光真相! 声明:网友投稿内容频道只负责投稿发布信息,真假自行甄别,理性吃瓜,恶意投稿,后果自负! 感观世界实时更新币圈财经-东南亚头条-新闻资讯-吃瓜曝料-影视-成人电影-包养-小火箭免费机场 🔰 关注导航不迷路 :搜索 @AACCTV ✈️ 广告/管理员 @YDL89 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/ddmm789 |
National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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.
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 in near-verbatim form on 12 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 |
|---|---|---|---|
| @wmxw8687/298578 Aug 2026, 10:40 UTC | @ddmm789/41006 · this entry8 Aug 2026, 10:40 UTC | 1.00 | under a minute |
| @wmxw8687/2998811 Aug 2026, 14:06 UTC | @ddmm789/41378 · this entry11 Aug 2026, 14:06 UTC | 1.00 | under a minute |
| @ddmm789/42721 · this entry22 Aug 2026, 19:40 UTC | @wmxw8687/3040022 Aug 2026, 19:43 UTC | 1.00 | 2 minutes |
| @wmxw8687/3057526 Aug 2026, 13:40 UTC | @ddmm789/43245 · this entry26 Aug 2026, 13:41 UTC | 1.00 | under a minute |
| @wmxw8687/3069729 Aug 2026, 12:55 UTC | @ddmm789/43574 · this entry29 Aug 2026, 12:55 UTC | 1.00 | under a minute |
| @ddmm789/43821 · this entry1 Sept 2026, 16:00 UTC | @wmxw8687/308011 Sept 2026, 16:00 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @wmxw8687 | 95 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | @wmxw8687 (52–43) |
| @TGlanhuo | 96 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (50–46) |
| @ershouflb | 39 (8/8 hand-verifiable sample passed) | 1.00 | 1.7 hours | @ershouflb (33–6) |
| @wd809 | 33 (6/8 hand-verifiable sample passed) | 1.00 | 3 minutes | @wd809 (19–14) |
| @xigang9918 | 29 (8/8 hand-verifiable sample passed) | 1.00 | 55 minutes | @xigang9918 (29–0) |
| @xinwenriji | 27 (6/8 hand-verifiable sample passed) | 1.00 | 1.9 hours | @xinwenriji (25–2) |
| @chiguabgt | 23 (8/8 hand-verifiable sample passed) | 1.00 | 1.7 hours | @chiguabgt (23–0) |
| @ZFJCG | 22 (8/8 hand-verifiable sample passed) | 1.00 | 4.3 hours | @ZFJCG (22–0) |
| @sucaidny | 22 (8/8 hand-verifiable sample passed) | 1.00 | 79 minutes | @sucaidny (18–4) |
| @PG681 | 22 (8/8 hand-verifiable sample passed) | 1.00 | 2.6 hours | @PG681 (21–1) |
| @aichiguaba | 18 (8/8 hand-verifiable sample passed) | 1.00 | 5.9 hours | this entry (10–8) |
| @neihanduanzi1 | 16 (7/8 hand-verifiable sample passed) | 1.00 | 3.1 hours | @neihanduanzi1 (14–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. 400 of the 400 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 645 comparable posts for this entry, running 7 August 2026 to 11 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.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 13 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 12:59 | 65,440 | -342 |
| 9 Nov 2026, 16:56 | 65,782 | -249 |
| 8 Nov 2026, 11:06 | 66,031 | -227 |
| 7 Nov 2026, 07:54 | 66,258 | -207 |
| 6 Nov 2026, 07:19 | 66,465 | +102 |
| 5 Nov 2026, 08:17 | 66,363 | +1,203 |
| 4 Nov 2026, 09:59 | 65,160 | +106 |
| 3 Nov 2026, 10:36 | 65,054 | -48 |
| 2 Nov 2026, 11:06 | 65,102 | -55 |
| 1 Nov 2026, 13:07 | 65,157 | +724 |
| 31 Oct 2026, 12:16 | 64,433 | +2,494 |
| 30 Oct 2026, 14:31 | 61,939 | -2,406 |
| 29 Oct 2026, 13:35 | 64,345 | -3,999 |
| 28 Oct 2026, 13:16 | 68,344 | -317 |
| 27 Oct 2026, 14:57 | 68,661 | -189 |
| 26 Oct 2026, 14:50 | 68,850 | -306 |
| 25 Oct 2026, 12:16 | 69,156 | -465 |
| 24 Oct 2026, 12:16 | 69,621 | -895 |
| 23 Oct 2026, 11:07 | 70,516 | -313 |
| 22 Oct 2026, 09:45 | 70,829 | first reading |
2,074 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 197 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.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 2,074 (7 August 2026 – 13 November 2026) |
| Views total | 105,806 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 11:07 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 13 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.
Measured directly from 57 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.
52 reactions across 36 posts, in 9 distinct kinds. The most used accounts for 15.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 8 | 15.4% | |
| ❤ | 7 | 13.5% | |
| 🔥 | 7 | 13.5% | |
| 😁 | 7 | 13.5% | |
| 👏 | 6 | 11.5% | |
| ⚡ | 5 | 9.62% | |
| 🎉 | 5 | 9.62% | |
| 👍 | 5 | 9.62% | |
| 🤩 | 2 | 3.85% |
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 36 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 52 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 13 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.
Telegram’s own ‘edited’ marker: 0 of 610 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).
#印度新闻 印度中央工业安全部队、机场运营商、航空公司、地方政府、医疗服务、警察、消防、情报机构、民航安全局、民航总局、国家安全卫队及陆军等多个部门共同参加联合演习,展示了跨部门协调能力和应急行动准备水平。
Signed 先锋(24小时在线)
#美国新闻 凯蒂·斯派塞担任美国国家航空航天局蓝色起源“蓝月”二代月球着陆器项目的着陆器集成负责人,该着陆器是美国国家航空航天局阿尔忒弥斯计划商业载人登月系统之一。
Signed 先锋(24小时在线)
#美国新闻 美国海军“乔治·华盛顿”号航空母舰上的水兵分工协作,负责飞机调度、飞行甲板管理、舰载机起降及回收保障等任务,确保舰载航空作业全天候持续运行。
Signed 先锋(24小时在线)
#美国新闻 美国海关与边境保护局纽瓦克口岸官员协助美国法警局接收并处理从厄瓜多尔抵达的三名外国恐怖组织成员。三人涉嫌毒品贩运、枪支及机枪相关犯罪、共谋和洗钱等罪名,将根据美国纽约东区和南区联邦地区法院签发的逮捕令接受司法追究。
Signed 先锋(24小时在线)
#美国新闻 美国驻沙特阿拉伯达兰总领事艾米·史密斯会见沙特美国商会领导团队,就推动美国商业利益、拓展美国企业发展机会以及支持在沙特运营的美国公司进行交流。与会人员包括执行主任埃里希·菲利普斯、东部省分会董事会主席大卫·埃金顿及东部省区域主任穆娜·加约尔。
Signed 先锋(24小时在线)
#美国新闻 美国欧洲特种作战司令部回顾“坚定巨蛇26”演习,强调演习不仅检验了部队在北极环境下的作战能力,也加强了与北约盟友的协同合作,提升多环境下的联合训练水平和伙伴关系。
Signed 先锋(24小时在线)
#美国新闻 美国空军学院男子足球队前往内利斯空军基地,与空军官兵交流并近距离了解作战准备情况,随后参加对阵内华达大学拉斯维加斯分校的足球比赛,展现不同任务领域之间的团队合作精神。
Signed 先锋(24小时在线)
#美国新闻 美国空军F-35A“闪电II”隐形战斗机在中东地区上空执行巡逻任务。
Signed 先锋(24小时在线)
#新加坡新闻 新加坡方面欢迎泰国劳工部长朱拉蓬·阿蒙维瓦及其代表团访问新加坡,并回顾双方此前在曼谷举行的东盟劳工部长会议期间的友好交流。
Signed 先锋(24小时在线)
#美国新闻 美国空军与陆军官兵联合开展重型装备空投训练,提升联合行动准备能力及在任务需要时快速投送关键物资的能力。
Signed 先锋(24小时在线)
#英国新闻 由于他们生前居住在附近地区,当地海域和海岸线对他们有着特殊意义,因此将他们一同归还大海,安葬在熟悉且靠近家乡的海域。
Signed 先锋(24小时在线)
Photo, posted without a caption
Signed Channel Help
Showing the 12 most recent of 2,074 posts we hold for @ddmm789. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 2 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.
@ddmm789 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“全球东南亚凤凰新闻_曝光” (@ddmm789), 65,440 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/ddmm789.
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.