4 measurements spanning 17 days, net +35. 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 412–457 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
24 Aug 2026, 12:23
452
+20
16 Aug 2026, 08:56
432
+15
8 Aug 2026, 05:33
417
no change
7 Aug 2026, 13:09
417
first reading
Engagement
6 posts held, back to 28 October 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 31 October 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
44s
Average length
22s
Measured directly from 2 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.
Reaction mix
7 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 57.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
4
57.1%
🎉
3
42.9%
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 3 of the 6 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 28 October 2024 to 31 October 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Showing the 6 most recent of 6 posts we hold for @jpz887. 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.
Appears in Telegram’s recommendations for other channels
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.
东南亚新闻 | 亚太日报 | 华人便民 @ytxw88 · 68,507 Telegram ranks this channel #4 of 21 here — alongside 20 others — read 20 August 2026
缅北大事件|亚太新闻|东南亚吃瓜 曝光 悬赏 @mbxw2 · 59,739 Telegram ranks this channel #5 of 26 here — alongside 25 others — read 22 August 2026
柬埔寨大事件|头条新闻曝光🌏 @JPZ990 · 92,004 Telegram ranks this channel #6 of 43 here — alongside 42 others — read 15 August 2026
🔔柬埔寨大事件|最新资讯! @ow333 · 74,199 Telegram ranks this channel #9 of 70 here — alongside 69 others — read 19 August 2026
东南亚娱乐曝光💠 @dny488 @dny488 · 79,788 Telegram ranks this channel #9 of 20 here — alongside 19 others — read 18 August 2026
全球|大事件|新闻|曝光|吃瓜 @bgtjt · 70,669 Telegram ranks this channel #9 of 69 here — alongside 68 others — read 16 August 2026
柬埔寨大事件/曝光 @jpz0123 · 52,658 Telegram ranks this channel #12 of 69 here — alongside 68 others — read 24 August 2026
📣精彩东南亚大事件📣 @pp666 · 236,772 Telegram ranks this channel #27 of 54 here — alongside 53 others — read 11 August 2026
柬埔寨新闻|华人资讯曝光|cambodia news @jianpuzhaihuarenzixun · 82,612 Telegram ranks this channel #45 of 72 here — alongside 71 others — read 15 August 2026
东南亚华人大事件 @DNY181 · 50,326 Telegram ranks this channel #60 of 66 here — alongside 65 others — read 22 August 2026
全球大事件曝光❖东南亚吃瓜新闻 @dsj665 · 114,393 Telegram ranks this channel #68 of 72 here — alongside 71 others — read 15 August 2026
This channel appears in 11 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 24 August 2026 — this
entry's latest reading, not the date you are reading this.
“😈柬埔寨《骗子曝光》/西港/菩萨/财通/国公” (@jpz887), 452 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/jpz887.
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.