Channel
@jpzdsjj
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
56,598subscribers
-42,752 since we began measuring on 26 September 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002872747690 |
|---|---|
| Type | Channel |
| Username | @jpzdsjj |
| Description | 🌴东南亚新闻曝光-聚焦时事 频道专注于东南亚华人最新动态资讯，让你看尽海外华人大小事。 🌴本频道工作人员不会主动私聊任何飞机用户！ 🌴新闻投稿： @judlalan 🌴广告招商： @judlalan |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 September 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/jpzdsjj |
International news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 13 October 2026 and assigned it the closest of 31 fixed categories, at 61% 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 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 |
|---|---|---|---|
| @jpzdsjj/7277 · this entry11 Oct 2026, 14:37 UTC | @vayi6/345611 Oct 2026, 14:38 UTC | 1.00 | 72 seconds |
| @jpzdsjj/7434 · this entry14 Oct 2026, 12:50 UTC | @vayi6/354214 Oct 2026, 12:51 UTC | 1.00 | under a minute |
| @jpzdsjj/7477 · this entry15 Oct 2026, 14:01 UTC | @vayi6/358215 Oct 2026, 14:01 UTC | 1.00 | under a minute |
| @jpzdsjj/7501 · this entry16 Oct 2026, 14:15 UTC | @vayi6/361516 Oct 2026, 14:15 UTC | 1.00 | under a minute |
| @jpzdsjj/7707 · this entry21 Oct 2026, 14:36 UTC | @vayi6/382521 Oct 2026, 14:37 UTC | 1.00 | under a minute |
| @jpzdsjj/7733 · this entry22 Oct 2026, 13:15 UTC | @vayi6/386422 Oct 2026, 13:16 UTC | 1.00 | 72 seconds |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @vayi6 | 11 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (11–0) |
| @ys315bg | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @ys315bg (9–0) |
| @TGlanhuo | 6 (5/6 hand-verifiable sample passed) | 1.00 | under a minute | @TGlanhuo (5–1) |
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. 14 of the 14 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 716 comparable posts for this entry, running 26 September 2026 to 13 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_source, last confirmed 14 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 |
|---|---|---|
| 13 Nov 2026, 23:00 | 56,598 | -1,383 |
| 11 Nov 2026, 08:09 | 57,981 | -891 |
| 9 Nov 2026, 11:06 | 58,872 | -954 |
| 8 Nov 2026, 01:00 | 59,826 | -544 |
| 6 Nov 2026, 21:55 | 60,370 | -736 |
| 5 Nov 2026, 22:58 | 61,106 | -253 |
| 5 Nov 2026, 00:08 | 61,359 | -91 |
| 4 Nov 2026, 00:06 | 61,450 | -219 |
| 3 Nov 2026, 02:25 | 61,669 | -210 |
| 1 Nov 2026, 23:06 | 61,879 | -456 |
| 31 Oct 2026, 23:55 | 62,335 | -791 |
| 30 Oct 2026, 20:39 | 63,126 | -832 |
| 29 Oct 2026, 19:40 | 63,958 | -639 |
| 28 Oct 2026, 22:00 | 64,597 | -773 |
| 28 Oct 2026, 00:19 | 65,370 | -628 |
| 26 Oct 2026, 22:16 | 65,998 | -664 |
| 26 Oct 2026, 00:31 | 66,662 | -498 |
| 25 Oct 2026, 00:45 | 67,160 | -798 |
| 23 Oct 2026, 22:45 | 67,958 | -1,609 |
| 22 Oct 2026, 21:36 | 69,567 | first reading |
739 posts held, back to 26 September 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 100 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 1 of 380 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 739 (26 September 2026 – 14 November 2026) |
| Views total | 622,461 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Nov 2026, 02:59 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 15 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 51 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.
544 reactions across 132 posts, in 8 distinct kinds. The most used accounts for 20.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 112 | 20.6% | |
| 🔥 | 95 | 17.5% | |
| 👍 | 92 | 16.9% | |
| 👏 | 89 | 16.4% | |
| 🎉 | 80 | 14.7% | |
| ❤ | 74 | 13.6% | |
| 👎 | 1 | 0.184% | |
| 🤩 | 1 | 0.184% |
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 134 of the 739 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 544 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 739 most recent posts we hold, published 26 September 2026 to 14 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 380 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).
泰国帆板错失青奥会奖牌 “比乌”伊提蓬表现最佳获第四名 在2026年青年奥林匹克运动会风帆项目比赛中，泰国队未能收获奖牌，但年轻选手的表现依然可圈可点。其中，年仅14岁的小将“碧”伊提蓬在女子风帆比赛中一路拼搏，最终排名第四，距离领奖台仅一步之遥，成为泰国队本次赛事表现最为突出的选手。另一名泰国选手“维纳斯”则在同项目中位列第九。 据泰国INN新闻率先报道，伊提蓬在奖牌轮比赛中一度保有争夺铜牌的希望。她在起航后奋力追赶前面的突尼斯选手，试图在航线选择和风况利用上寻找突破口。然而，对手在关键航段保持了稳定的速度与角度控制，伊提蓬虽全力施压，最终未能完成超越，以第四名的成绩结束了自己的首次青奥会之旅。按照风帆项目的竞赛规则，奖牌轮的成绩往往对最终排名起到决定性作用，第四名也意味着她与奖牌擦肩而过。
人工智能技术成为今天下午弗朗科科技论坛首日边会的主要议题 人工智能技术成为弗朗科科技论坛首日会议重要议题 本报讯 今日下午，弗朗科科技论坛首日会议如期举行，人工智能技术成为与会各方讨论的重要议题。据金边日报报道，本次论坛汇聚了来自科技界、产业界及学术界的多位代表，围绕人工智能的最新进展、应用场景及治理挑战展开了深入交流。
移民局说明中国乘客被遣返事件 抱怨拘留室有异味 声称向中介支付1.8万元人民币 澄清移民局 近日，一则关于中国籍乘客在泰国素万那普机场被移民局拒绝入境的消息在社交平台持续发酵。据称，该事件发生于2569年11月12日，相关页面在发帖中详细描述了当事人被拒绝入境后的遭遇，包括对遣返等候室条件的投诉，以及声称有中介索要18000元人民币以“帮助通过边检”的情况。帖子发布后迅速引发关注，不少网友对事件细节和机场处置流程提出疑问。 从目前披露的信息看，事件的核心指向两个层面：一是当事乘客被拒绝入境后的安置与等待条件，二是所谓“中介索费”的说法。按照国际航空运输的通行做法，被目的地国移民部门拒绝入境的人员，通常需要在机场指定区域等待遣返或后续安排，等候环境的舒适度、信息告知是否充分，往往成为争议焦点。此次投诉中提到的等候室条件问题，正触及这一容易被忽视的环节。而关于中介索要费用的说法，则涉及口岸通关秩序和旅客权益保护，若属实，不仅损害…
“A Asset”宣布推进泰国房地产业务，提出“始终向前，创造，可持续”理念
吉布兰辞职，普拉博沃与佐科维的政治关系进一步破裂？ 吉布兰辞去职务引发印尼政坛连锁反应，普拉博沃阵营或成最大受益者 雅加达消息——印度尼西亚政坛近日因一则人事变动再度泛起波澜。据当地媒体报道，现任副总统吉布兰·拉卡布明·拉卡已正式辞去其所担任的某项重要职务，这一举动被广泛解读为印尼政治力量重组的最新信号。尽管官方尚未就辞职的具体原因作出详细说明，但分析人士普遍认为，此举将在总统普拉博沃·苏比安托与前任总统佐科·维多多之间本就微妙的政治博弈中投下新的变量。
染色体异常导致男子无精子症 显微取精技术为克氏综合征患者带来生育希望 35岁的平哥（化名）因患有克氏综合征，长期面临睾丸萎缩和无精症的困扰。近日，医生通过显微手术在其睾丸组织中寻找精子，尝试为其实施试管婴儿受精。这一案例再次引发人们对男性不育特殊病因及辅助生殖技术进展的关注。
河内彩票今日 69年11月14日 查询河内彩票今日开奖结果 在此实时查看 河内彩票今日开奖结果实时可查 便捷服务助力彩民掌握开奖动态 11月14日，河内彩票如期开奖，众多彩民通过线上渠道关注本期开奖结果。当天，不少用户通过相关平台查询“河内彩票14/11/69”的开奖信息，希望第一时间了解本期中奖号码。目前，相关查询服务已实现每日实时更新，彩民可随时查看最新开奖结果，及时掌握开奖动态。
滕·蓬指责“索蓬”拒绝将“克拉塔姆”党逐出反对派的文件退回，理由是不符合议会规章。 泰党内部人事风波持续发酵 滕·梭蓬抗议“索蓬”拒签撤职书 近日，泰国政坛围绕一份撤职文件再起波澜。据媒体报道，滕·梭蓬就“索蓬”拒绝签署相关撤职书一事公开表达抗议，事件迅速引发外界对相关阵营内部协调机制与人事安排走向的关注。围绕“格拉……”相关职务变动的争议，也随之成为舆论焦点。
国际法院即将就罗兴亚问题作出的判决：民族团结政府的立场与国际社会的关切 缅甸民族团结政府外交部长杜欣玛昂近日就罗兴亚人问题公开表态，强调正义不应取决于政治上的便利与否，而应被视为一项基本原则。这一表态在缅甸当前复杂政治格局下引发关注，也为长期悬而未决的罗兴亚人处境再度投下聚光灯。 杜欣玛昂是在谈及罗兴亚人权利与问责问题时作出上述表示的。她指出，对罗兴亚人而言，正义不是可以因政治需要而灵活取舍的选项，而是一项必须坚守的根本原则。这一表述被外界解读为民族团结政府对罗兴亚群体权益问题的明确立场宣示，也暗含对以往政策中将正义让位于政治考量的做法提出批评。
阿克莱达银行2026年第三季度利润增长14%至6700万美元，利息收入增加和融资成本下降推动盈利，不良贷款率达6.94% 爱喜利达银行第三季度税后利润同比增长14.05%，不良贷款率升至6.94% 据柬埔寨投资评论消息，爱喜利达银行及其子公司近日公布的经营数据显示，2026年第三季度该集团实现税后利润2715.2亿瑞尔（约合6712万美元），较去年同期增长14.05%，延续了今年以来稳健的盈利态势。与此同时，截至9月30日，集团不良贷款率为6.94%，较去年年底的5.94%上升1个百分点，资产质量变化引发市场关注。
战火中的农民将如何挺过持续数月的厄尔尼诺灾害 缅甸农民面临气候与冲突双重压力 厄尔尼诺加剧农业风险 随着厄尔尼诺现象持续发展，缅甸各地农民正面临气温升高、降雨模式异常以及潜在缺水等多重气候风险。在冲突持续、农业投入品价格高涨和信息获取渠道有限的背景下，这一轮气候冲击可能进一步加剧当地农业生产的脆弱性。
内阁取消总理府8项过时且重复的规定，具体有哪些？！ 内阁决定废止8项总理府规章 着力提升政府服务效能 内阁会议日前审议通过一项决定，取消8项现行总理府规章。据悉，这些规章因制定时间较早、内容明显滞后于当前实际，且部分条款在职能配置上与其他现行规定存在交叉重叠，已难以适应政府运行和管理需要。此次集中清理，旨在理顺制度体系、减少职责不清带来的效率损耗，进一步提升政府服务效能。
Showing the 12 most recent of 739 posts we hold for @jpzdsjj. 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.
We recorded 1 post on @jpzdsjj as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“东南亚曝光吃瓜《缅甸 斯里兰卡 菲律宾 柬埔寨》” (@jpzdsjj), 56,598 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/jpzdsjj.
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.