Telegram RegisterThe public register of Telegram
Telegram profile photo for 东南亚曝光-泰国大事件(曼谷日记)

Channel

东南亚曝光-泰国大事件(曼谷日记)

@jpzjdft

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

81,085subscribers

-16,961 since we began measuring on 26 September 2026

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

Register entry

Telegram ID-1003175832017
TypeChannel
Username@jpzjdft
Description海外华人必看的吃瓜聚集地! 华人大小事,频道专注于东南亚华人最新动态资讯,生活故事分享,海外华人求助 最新内幕、爆笑生活趣事、意想不到的惊喜…… 工作再累,也别错过这里的欢乐和刺激,一起嗨、一起瓜! 投稿曝光: @judlalan 商务广告: @judlalan 🌏 覆盖区域: #东南亚 #菲律宾 #泰国 #缅甸 #斯里兰卡
CreatedBetween 1 September 2025 and 31 December 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 September 2026
Last confirmed live12 November 2026
Measurements held33
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/jpzjdft

Topic

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 71% 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. 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
@jpzjdft/10334 · this entry11 Oct 2026, 11:06 UTC@vayi6/344911 Oct 2026, 11:06 UTC1.00under a minute
@jpzjdft/10356 · this entry12 Oct 2026, 11:12 UTC@vayi6/347112 Oct 2026, 11:13 UTC1.0072 seconds
@jpzjdft/10451 · this entry14 Oct 2026, 12:07 UTC@vayi6/354114 Oct 2026, 12:08 UTC1.00under a minute
@jpzjdft/10517 · this entry16 Oct 2026, 11:49 UTC@vayi6/360816 Oct 2026, 11:50 UTC1.00under a minute
@jpzjdft/10519 · this entry16 Oct 2026, 12:09 UTC@vayi6/360916 Oct 2026, 12:11 UTC1.0072 seconds
@jpzjdft/10725 · this entry22 Oct 2026, 15:20 UTC@vayi6/386922 Oct 2026, 15:22 UTC1.002 minutes
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
@vayi612 (7/8 hand-verifiable sample passed)1.0072 secondsthis entry (12–0)
@ys315bg9 (8/8 hand-verifiable sample passed)1.00under a minute@ys315bg (9–0)
@TGlanhuo6 (6/6 hand-verifiable sample passed)1.00under 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 645 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.

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

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.

Growth

81,085104,30092,692.526 September 2026 — 98,046 subscribers26 September 2026 — 98,046 subscribers4 October 2026 — 94,810 subscribers8 October 2026 — 90,748 subscribers13 October 2026 — 100,162 subscribers14 October 2026 — 101,553 subscribers15 October 2026 — 100,966 subscribers16 October 2026 — 103,229 subscribers17 October 2026 — 103,171 subscribers18 October 2026 — 102,903 subscribers19 October 2026 — 104,300 subscribers20 October 2026 — 103,472 subscribers21 October 2026 — 103,040 subscribers22 October 2026 — 82,277 subscribers23 October 2026 — 97,918 subscribers24 October 2026 — 97,211 subscribers26 October 2026 — 96,311 subscribers27 October 2026 — 95,259 subscribers27 October 2026 — 92,896 subscribers28 October 2026 — 89,214 subscribers29 October 2026 — 88,119 subscribers30 October 2026 — 86,493 subscribers31 October 2026 — 86,119 subscribers1 November 2026 — 85,443 subscribers2 November 2026 — 85,323 subscribers3 November 2026 — 85,071 subscribers4 November 2026 — 84,955 subscribers5 November 2026 — 84,794 subscribers6 November 2026 — 84,433 subscribers7 November 2026 — 83,694 subscribers8 November 2026 — 82,982 subscribers10 November 2026 — 82,115 subscribers12 November 2026 — 81,085 subscribers26 September 202612 November 2026
33 measurements spanning 47 days, net -16,961. 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 77,603–107,782 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
12 Nov 2026, 13:4781,085-1,030
10 Nov 2026, 08:5082,115-867
8 Nov 2026, 21:0682,982-712
7 Nov 2026, 12:1183,694-739
6 Nov 2026, 09:1584,433-361
5 Nov 2026, 12:3084,794-161
4 Nov 2026, 14:1084,955-116
3 Nov 2026, 16:2485,071-252
2 Nov 2026, 17:4785,323-120
1 Nov 2026, 18:4885,443-676
31 Oct 2026, 18:5186,119-374
30 Oct 2026, 19:3686,493-1,626
29 Oct 2026, 19:4188,119-1,095
28 Oct 2026, 21:4989,214-3,682
27 Oct 2026, 23:0792,896-2,363
27 Oct 2026, 00:3895,259-1,052
26 Oct 2026, 01:0696,311-900
24 Oct 2026, 23:1797,211-707
23 Oct 2026, 22:4597,918+15,641
22 Oct 2026, 19:3882,277first reading

Engagement

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

ERR · 30 days
2.23%
avg views ÷ 81,085 subscribers
Avg views / post
1,810
407 posts measured
Reaction rate
0.088%
reactions ÷ views · ER floor
Posts in window
407
of 668 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 58 of 407 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 14 November 2026
Posts held668 (26 September 2026 – 14 November 2026)
Views total735,224
Reactions total62
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 01:48 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
≈10,100
Videos
≈742
Links
≈22

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.

Video runtime
4s
Average length
4s

Measured directly from 1 video 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.

Reaction mix

157 reactions across 105 posts, in 9 distinct kinds. The most used accounts for 56.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍8956.7%
🔥2012.7%
❤1610.2%
😁106.37%
🎉85.10%
👏85.10%
⚡21.27%
🤩21.27%
🥰21.27%

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 113 of the 668 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 157 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 668 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.

Recent posts

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

14 Nov 2026, 14:36 UTC≈5,430 viewsread 15 November 2026
Photo

斯里兰卡航空将墨尔本航班增至每周10班 斯里兰卡航空公司近日宣布,将从11月15日起每周增加三班飞往澳大利亚墨尔本的航班,使其飞往澳大利亚的航班总量增至每周14班。此举被视为该航司在南亚至大洋洲航线网络布局上的又一重要动作,也反映出两国间旅行需求的持续升温。 根据安排,新增航班将在现有航线基础上进一步加密科伦坡与墨尔本之间的空中通道。此前,斯里兰卡航空已运营连接科伦坡与澳大利亚多座城市的航班,墨尔本作为澳大利亚重要的航空门户之一,长期是南亚旅客前往维多利亚州及周边地区的主要目的地。航班频次的提升,意味着旅客在出行时间选择上将获得更大灵活性,中转衔接效率也有望随之改善。

14 Nov 2026, 13:54 UTC11 viewsread 15 November 2026
Photo

Grab推出T.A.S.T.E战略,以数字力量延展文化资本,创造机遇并驱动十万亿级经济 Grab正式推出T.A.S.T.E战略,以数字力量延展文化资本,并联合公私部门举办“GrabNEXT 2026”政策研讨会,围绕数字经济与文化产业融合发展展开讨论。此举被视为该公司在区域数字生态布局上的又一重要动作,也反映出平台型企业正加快从单一服务提供者向经济赋能者转型。 据了解,T.A.S.T.E战略聚焦文化资本的数字化延展,旨在通过技术手段将地方文化资源、传统产业与数字平台相连接,从而创造新的就业与创业机遇。Grab方面表示,该战略并非孤立的企业行为,而是希望借助公私协作机制,推动更广泛的经济参与。在“GrabNEXT 2026”研讨会上,来自公共部门、产业界与学术界的代表就政策协同、数字基础设施建设及中小微企业赋能等议题交换了意见。

14 Nov 2026, 13:13 UTC9 viewsread 15 November 2026
Photo

海水咸咸却甜甜的,“塔吉·卡温”开启痴爱模式“弗伦德·披拉格立” “塔吉·昆”开启痴爱模式:一场向妈妈们挥动绿旗的温情出发 近日,一则来自《前线新闻社》的报道引发关注。报道以“是时候向妈妈们挥动绿旗让心情飞扬了”开篇,将视线投向“塔吉·昆”所开启的“痴爱模式”。相关文章由“弗伦德·披拉格立”撰写,首发于《前线新闻社》,以“坚定、直行、直往”的姿态,传递出一种轻快而真挚的情感信号。

14 Nov 2026, 12:30 UTC≈5,900 viewsread 15 November 2026
Photo

佐伊·克莱曼:英伟达首席执行官的风流韵事将在美国乃至更广范围引发涟漪 英伟达公司近日证实,已对首席执行官黄仁勋展开内部调查,起因是有指控称其与一名女子存在婚外情关系,而该女子被指与中国情报部门有关联。这一消息迅速引发科技界与舆论场的广泛关注,也让这家全球人工智能芯片巨头罕见地站到了公司治理与安全审查的风口浪尖。 据媒体报道,相关指控最初通过匿名渠道流传,随后进入公司内部合规程序。英伟达方面表示,公司已按照既定流程启动调查,目前尚未得出最终结论。公司强调,对高管行为设有明确的合规要求,任何涉及潜在利益冲突或安全风险的举报都会得到严肃对待。黄仁勋本人及其代表暂未就指控细节作出公开回应。

14 Nov 2026, 11:49 UTC10 viewsread 15 November 2026
Photo

国际代表团和记者赞扬柬埔寨在法语国家部长会议上的接待工作 法语国家部长级会议在金边举行 与会代表盛赞柬埔寨组织工作 应邀前来金边出席第48届法语国家部长级会议的各代表团成员及国际记者,近日对柬埔寨王国出色的组织安排和热情接待表示高度赞赏,并将此次活动视为提升柬埔寨国际形象与多边外交参与度的重要契机。

14 Nov 2026, 11:06 UTC≈6,340 viewsread 15 November 2026
Photo

丹朗镇一名28岁男子外出打猎时被同伴误当成野兽开枪击中身亡 【正文】 缅甸钦邦丹朗镇佐佩兰地区11月10日发生一起悲剧:一名28岁男子在与同伴外出打猎时,被误认为野兽遭枪击身亡。据当地消息,死者名为阿伯拉罕(又名德巴),系佐佩兰地区居民。事发当天,他与数名同伴一同进入山林狩猎,期间一名同伴误将其当作猎物开枪,子弹击中阿伯拉罕,致其当场倒地。同行人员随即将其送往附近医疗点,但终因伤势过重不治身亡。

14 Nov 2026, 10:55 UTC≈2,310 viewsread 15 November 2026
Photo

🫥😄😄😄😄😄😄😄😄😄 🫥🏆🏆🏆🏆🏆🏆🏆🏆🏆🏆 🫥🏆🏆🏆🏆🏆🏆🏆🏆🏆🏆 😀云购入口: @yyyg 😀云购网址: yyyg.com 🫥一元云购主营商品: 🏆🏆🏆🏆🏆🏆🏆 🏆🏆🏆🏆🏆 🏆🏆🏆🏆🏆🏆 🏆🏆🏆🏆🏆 🏆🏆🏆🏆🏆 🏆每消费1USDT即可获得1积分,积分可用于积分抽奖或者兑现成USDT,最低80积分兑换1USDT 🏆🏆🏆🏆🏆🏆🏆 🏆🏆🏆🏆🏆🏆🏆🏆🏆 😎新手入门 😎 视频教程 🏆🏆🏆🏆🏆🏆🏆🏆🏆🏆🏆🏆🏆🏆 注:中奖后可选择实体发货或选择兑现成USDT进行提现。 🏆官方频道: @yyygpd 🏆VIP交流群: @yyygjlq 🏆官方客服: @yyyg01 @yyyg03

14 Nov 2026, 10:24 UTC≈3,100 viewsread 14 November 2026
Photo

佳明fēnix 9 Pro手表的一系列专业运动功能 佳明近日推出芬尼克斯9专业版智能手表,围绕耐用性、屏幕显示、续航能力以及性能分析工具进行了多项改进,继续瞄准运动爱好者与户外活动人群。作为佳明旗下定位高端的户外运动腕表系列,芬尼克斯一直以兼顾城市日常佩戴与野外复杂环境使用而著称,此次专业版的更新也被视为该系列在专业运动场景中的又一次针对性强化。 从产品方向看,耐用性仍是芬尼克斯系列的核心卖点之一。户外活动人群往往面临磕碰、温差、涉水等多重考验,手表需要在结构设计和材质选择上具备足够的抗压能力。佳明此次在专业版上强调耐用性改进,意味着其在表体防护和适应恶劣环境方面做了进一步优化,以满足登山、越野跑、徒步等场景下的长期使用需求。屏幕方面的提升则直接关系到户外可读性,尤其是在强光照射或佩戴手套操作时,显示效果和交互体验的改善对运动人群尤为重要。

14 Nov 2026, 09:42 UTC≈6,520 viewsread 14 November 2026
Photo

印度阿萨姆邦发生卡车与公交车相撞事故,至少24人死亡 印度东北部阿萨姆邦近日发生一起严重交通事故,一辆集装箱卡车与一辆公交车相撞,造成至少24人死亡、11人受伤。当地警方已证实这一伤亡情况,事故原因仍在进一步调查中。 据警方通报,事故发生在阿萨姆邦境内一条主要公路上。涉事集装箱卡车与载客公交车在行驶过程中发生猛烈碰撞,公交车受损严重。事发后,当地应急部门迅速赶赴现场展开救援,伤者已被送往附近医院接受救治。由于部分伤者伤势较重,死亡人数仍有可能进一步上升。警方表示,正对事故的具体原因、车辆行驶状况及道路条件等进行全面调查。

14 Nov 2026, 09:00 UTC9 viewsread 14 November 2026
Photo

阿努廷准备迎接质询战,确信能够全部解释清楚,并放话他们是否理解是每个人的角色 泰国政坛再起波澜:阿努廷备战质询战 强调以工作成果与事实回应 泰国政坛近日再度聚焦于一场即将到来的议会质询交锋。据当地媒体报道,泰国副总理兼内政部长阿努廷已明确表示,将正面迎战反对派发起的质询战,并放话称将以实际工作成果和客观事实作为回应。这一表态迅速引发舆论关注,被视为执政联盟与反对阵营在议会舞台上新一轮博弈的前奏。

13 Nov 2026, 22:30 UTC11 viewsread 14 November 2026
Photo

杜琪惊讶布姆怎么能走到这一步,曾疫情期间确实接受过帮助,说明“瞎眼老板”给一千万的争议 杜琪·素达拉就“布姆·帕娜达”相关争议发声 澄清千万铢捐款来源并派律师说明情况 近日,围绕知名人士“布姆·帕娜达”的一系列争议持续发酵,泰国政界人士杜琪·素达拉就此事公开表态,坦言自己对布姆走到如今这一步感到惊讶,并就此前备受关注的“瞎眼老板”比雅捐款1000万铢一事作出澄清,指出该笔款项实为民众为洪灾救助所捐,而非个人资金。

13 Nov 2026, 21:48 UTC≈5,670 viewsread 14 November 2026
Photo

“这算作弊吗?合法吗?”——男子在新加坡回收机前反复扫描同一饮料罐条形码,引发关于多罐退款是否合规的争论 新加坡近日一段关于饮料容器回收机的视频在网络上引发广泛讨论。画面显示,一名男子在机器前归还空饮料罐时,先扫描一个罐子,待机器成功读取条形码后,却将罐子抽出,随后又插入另一个罐子,并反复重复这一操作。相关视频传播后,围绕回收机退款机制是否被滥用、回收计划如何监管等问题,舆论出现明显分歧。 新加坡近年来推行饮料容器回收计划,通过设置反向自动售货机等方式,鼓励公众将空饮料罐、塑料瓶等投入回收系统,并按容器数量返还押金或奖励。此类机制的核心在于“先押后退”:消费者购买饮料时支付少量押金,归还空容器后取回款项。其初衷是提高回收率、减少一次性包装废弃物,并培养公众的分类与回收习惯。然而,正因退款与容器数量直接挂钩,系统在设计上必须依赖条形码识别、容器形态检测等技术手段,防止重复投放或不符合要求的物品混入。

Showing the 12 most recent of 668 posts we hold for @jpzjdft. 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

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

“东南亚曝光-泰国大事件(曼谷日记)” (@jpzjdft), 81,085 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/jpzjdft.

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.