Gambling & betting — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 66% 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.
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 word for word on 4 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)
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. 44 of the 44 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 20 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.
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).
Across the whole group of 5, the earliest publisher we hold is @jdcmyn. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_source, last confirmed 8 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.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 4 other registered channels, 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.
15 measurements spanning 52 days, net -2,129. 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 7,002–9,769 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
28 Sept 2026, 21:18
7,321
-156
18 Sept 2026, 19:56
7,477
-189
14 Sept 2026, 19:18
7,666
-206
11 Sept 2026, 16:15
7,872
-122
7 Sept 2026, 05:40
7,994
-143
2 Sept 2026, 10:44
8,137
-195
30 Aug 2026, 06:13
8,332
-132
27 Aug 2026, 12:06
8,464
-162
24 Aug 2026, 15:02
8,626
-216
20 Aug 2026, 12:46
8,842
-152
17 Aug 2026, 20:36
8,994
-131
15 Aug 2026, 05:09
9,125
-159
11 Aug 2026, 12:53
9,284
-147
8 Aug 2026, 02:36
9,431
-19
7 Aug 2026, 18:33
9,450
first reading
Engagement
331 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 27 pages of 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 331 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
1h 03m
Average length
45s
Measured directly from 85 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.
Showing the 12 most recent of 331 posts we hold for @jianpuzhaiFBI. 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
Named by 1 registered channel — 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.
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.
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.
东南亚新闻|海豹资讯曝光|news @JXBGW · 179,872 Telegram ranks this channel #15 of 21 here — alongside 20 others — read 13 August 2026
迪拜新闻|海豹资讯曝光|dubai news @dibai_01 · 177,582 Telegram ranks this channel #21 of 50 here — alongside 49 others — read 15 August 2026
越南新闻大事件 @VN704 · 60,495 Telegram ranks this channel #23 of 65 here — alongside 64 others — read 27 August 2026
东南亚|曝光|吃瓜|寻人 @jinbian8 · 49,572 Telegram ranks this channel #24 of 41 here — alongside 40 others — read 25 August 2026
全网曝光|东南亚大事件 @dnysj · 193,354 Telegram ranks this channel #25 of 59 here — alongside 58 others — read 13 August 2026
东南亚缅北菲律宾迪拜大曝光|大事件|悬赏令 @dny2023dbg · 76,734 Telegram ranks this channel #27 of 64 here — alongside 63 others — read 13 August 2026
缅甸新闻大事件 @MB104 · 68,912 Telegram ranks this channel #30 of 75 here — alongside 74 others — read 16 August 2026
泰国新闻大事件 @th769 · 50,114 Telegram ranks this channel #34 of 67 here — alongside 66 others — read 23 August 2026
东南亚黑暗事件 @aq7777 · 53,208 Telegram ranks this channel #36 of 64 here — alongside 63 others — read 23 August 2026
缅甸新闻|华人资讯曝光|myanmar news @miandianhuarenzixun · 77,670 Telegram ranks this channel #40 of 77 here — alongside 76 others — read 16 August 2026
🍉吃瓜中心&搞笑日常 @cggx33 · 80,625 Telegram ranks this channel #45 of 72 here — alongside 71 others — read 21 August 2026
🔔柬埔寨大事件|最新资讯! @ow333 · 61,422 Telegram ranks this channel #48 of 70 here — alongside 69 others — read 19 August 2026
🅥世界TG华人曝光吧吃瓜社🇨🇳 @BG576 · 328,406 Telegram ranks this channel #50 of 68 here — alongside 67 others — read 10 August 2026
全网曝光|东南亚日记 @bbb1b · 329,787 Telegram ranks this channel #50 of 63 here — alongside 62 others — read 10 August 2026
吃瓜东南亚头条㊖ @CG887 · 106,503 Telegram ranks this channel #55 of 72 here — alongside 71 others — read 15 August 2026
东南亚大事件/曝光头条 @dnybgtt · 53,306 Telegram ranks this channel #57 of 68 here — alongside 67 others — read 23 August 2026
东南亚头条曝光 @QQ888880000 · 105,775 Telegram ranks this channel #58 of 69 here — alongside 68 others — read 17 August 2026
菲律宾新闻大事件 @flb608 · 90,990 Telegram ranks this channel #59 of 80 here — alongside 79 others — read 14 August 2026
东南亚曝光/大事件 @dny099 · 94,952 Telegram ranks this channel #62 of 67 here — alongside 66 others — read 22 August 2026
东南亚新闻头条(曝光) @dnyxwtt · 52,255 Telegram ranks this channel #63 of 79 here — alongside 78 others — read 24 August 2026
东南亚快讯|海外曝光【9y.com冠名】 @DNYKX · 57,897 Telegram ranks this channel #65 of 67 here — alongside 66 others — read 23 August 2026
柬埔寨新闻大事件 @jpz9118 · 89,389 Telegram ranks this channel #66 of 79 here — alongside 78 others — read 14 August 2026
菲律宾今日新闻|海豹资讯曝光|philippine news @baoguang_123 · 188,001 Telegram ranks this channel #71 of 73 here — alongside 72 others — read 14 August 2026
博彩黑平台曝光🔍 @uuuuuf · 267,362 Telegram ranks this channel #72 of 82 here — alongside 81 others — read 17 August 2026
This channel appears in 24 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 28 September 2026 — this
entry's latest reading, not the date you are reading this.
“🇰🇭柬埔寨新闻【转转娱乐赞助】” (@jianpuzhaiFBI), 7,321 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/jianpuzhaiFBI.
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.