Telegram RegisterThe public register of Telegram
Telegram profile photo for 柬埔寨安全快讯@rj111

Channel

柬埔寨安全快讯@rj111

@rj111

3 usernames

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Handles named that no longer answer · Cite this entry

13,485subscribers

+294 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003893838033
TypeChannel
Usernames@jianpuzhaichache @rj111 @w3bbb
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 November 2026
Measurements held164
Confirmed unchanged1 time, most recently 19 November 2026
On Telegramt.me/rj111

Topic

Local community — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 2 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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
@rj111/3927 · this entry22 Aug 2026, 05:12 UTC@hwrj8/279522 Aug 2026, 05:12 UTC1.00under a minute
@hwrj8/283724 Aug 2026, 16:10 UTC@rj111/3996 · this entry24 Aug 2026, 16:10 UTC1.00under a minute
@hwrj8/296330 Aug 2026, 09:38 UTC@rj111/4103 · this entry30 Aug 2026, 09:39 UTC1.00under a minute
@rj111/4163 · this entry31 Aug 2026, 14:13 UTC@hwrj8/304031 Aug 2026, 14:13 UTC1.00under a minute
@hwrj8/31411 Sept 2026, 13:38 UTC@rj111/4249 · this entry1 Sept 2026, 13:39 UTC1.00under a minute
@hwrj8/31692 Sept 2026, 14:24 UTC@rj111/4326 · this entry2 Sept 2026, 14:26 UTC1.0072 seconds
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
@hwrj840 (7/8 hand-verifiable sample passed)1.00under a minutethis entry (24–16)
@UULook5 (5/5 hand-verifiable sample passed)0.9572 secondsthis entry (4–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. 17 of the 17 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 203 comparable posts for this entry, running 7 August 2026 to 17 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @hwrj8. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · clone_source, last confirmed 18 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Growth

13,19114,17913,68513,4857 August 202619 November 2026
164 measurements spanning 103 days, net +294. 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 13,043–14,327 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 164
Measured (UTC)SubscribersChange
19 Nov 2026, 03:5613,485-39
16 Nov 2026, 16:0913,524+3
16 Nov 2026, 07:5013,521+1
16 Nov 2026, 06:4513,520-41
13 Nov 2026, 09:1713,561-6
12 Nov 2026, 21:5413,567no change
12 Nov 2026, 17:4613,567-29
10 Nov 2026, 18:2913,596no change
10 Nov 2026, 15:5113,596-1
10 Nov 2026, 12:5413,597-12
9 Nov 2026, 02:0913,609no change
9 Nov 2026, 01:5013,609+2
9 Nov 2026, 00:0013,607+17
7 Nov 2026, 20:4013,590+8
7 Nov 2026, 16:5513,582-3
7 Nov 2026, 15:0713,585+7
6 Nov 2026, 21:0913,578-3
6 Nov 2026, 17:0113,581-2
6 Nov 2026, 13:3713,583+4
5 Nov 2026, 17:2113,579first reading

Engagement

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

ERR · 30 days
11.7%
avg views ÷ 13,485 subscribers
Avg views / post
1,580
327 posts measured
Reaction rate
0.094%
reactions ÷ views · ER floor
Posts in window
327
of 732 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 185 of 327 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 18 November 2026
Posts held732 (7 August 2026 – 18 November 2026)
Views total515,724
Reactions total281
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 21:54 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

Video runtime
52m 47s
Average length
24s

Measured directly from 134 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

634 reactions across 298 posts, in 21 distinct kinds. The most used accounts for 82.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤52182.2%
👍507.89%
😁111.74%
🤬101.58%
😢71.10%
🤣60.946%
👌40.631%
🥰40.631%
👏30.473%
🔥30.473%
😱30.473%
👎20.315%
🤡20.315%
⚡10.158%
🎃10.158%
🎉10.158%
👀10.158%
💯10.158%
😍10.158%
😭10.158%
1 further kind10.158%

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

Measured over the 732 most recent posts we hold, published 7 August 2026 to 18 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 Stars

Stars received
7
across the posts below
Posts paid on
4
of 732 we hold a reading for · 0.5%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @rj111. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 732 most recent posts we hold for this entry, published 7 August 2026 to 18 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 129 of 327 posts held from the last 30 days (39.4%) 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).

18 Nov 2026, 17:56 UTC746 viewsread 18 November 2026

#金边 往皇宫方向这个位置查车,请注意‼️

18 Nov 2026, 16:00 UTC≈1,140 views1 reactionsread 18 November 2026
Photo

☺️☺️☺️☺️☺️☺️ 😘😘😘😘😪😮‍💨😵 🌟 品牌运营 · 公平透明 🈴 上亿储备 · 实力品牌 · 放心娱乐 😀官方网址: 6G.com 📌柬埔寨专用域名: 6G.VIP 🦧🦣🐘🦛🦏🐪🐫🦒🦘 😔 持续积累口碑,平台实力看得见 ➡️ 新人注册即送🔡 36U体验金 💎 原平台VIP等级 · 无条件转移 💎 返水😀.😀😀起·无需打码 💎 代理全线抽水+负盈返佣高达50% 💎 邀请好友奖励🍌🍌🍌U 🦬🐃🐂🐄🫏🐎🐖🐏🐑 😔 大额处理更迅速,服务体验更稳定 😃PG赏金超级大奖|单注245万U 😃 爆庄实录|3天狂揽1086万U 😃 新客首存6万U,豪提209万U 😀 官网: 6G.COM 😀 彩票: 6G567.COM 😕飞投 @AA6G 💻客服 @KF6G 1️⃣代理 @daili6g 🤑 爆奖 @ceo6g 🔓 实力无需解释 · 出款快就是证明!

🎉1

18 Nov 2026, 14:56 UTC≈1,340 views3 reactionsread 18 November 2026
Photo

#西港星汇遭贼后续:小偷竟然是翻阳台进来的! 原来这个小偷前一天晚上就动手了,竟然是从隔壁房间翻阳台进来的!现场还发现了疑似小偷用过的绳子,阳台栏杆上也留下了痕迹。 网友感叹:“从隔壁房间翻墙进来的,厉害……” 这小偷不仅偷走了衣服、内裤、洗面奶,连护照和手机都没放过。失主现在最希望的还是能把护照和手机找回来 #独家赞助【Y3国际】不限IP 大额提款无忧 东南亚大事件上压300万U 投注:@Y3Y3 🖥订阅:@rj111 ✉️投稿:@pei_8

❤3

18 Nov 2026, 13:00 UTC≈1,500 viewsread 18 November 2026
Photo

#付费广告 🔤3️⃣🔤🔤🔤 ⚡️⚡️ ⚡️⚡️⚡️⚡️ 东南亚大事件联合担保(电子)😀😀😀😀😀 #主营百家乐真人视讯 #旗下品牌😍😍😍😍 CHOICE真人视讯 索莱尔真人视讯 DB真人视讯 OG真人视讯 BBIN真人视讯 😀😳😳 😀😀 😀😀 爆奖率超高😍😍 #东南亚首选娱乐综合😃台 集团储备资金过亿 全网最牛逼的线上娱乐平台。 【#Y3国际|大哥😘😘】 单笔提款50万u 彩金3888u 单笔提款100万u 彩金8888u 单笔提款300万u 彩金38888u ⚡活动频道: @Y3Y3 ⚡官方客服: @Y123 👇 😀发财网址: y3666.com ⚡Y3小程序:@Y3_69bot (❤️无需注册) 电子最高😀😀😀😀一拉 真人限红😀😀😀😀一注 1️⃣1️⃣1️⃣1️⃣1️⃣1️⃣1️⃣ 1️⃣1️⃣1️⃣

18 Nov 2026, 12:29 UTC≈1,550 views0 reactionsread 18 November 2026
Photo

一名男子长期性侵继女,被判12年 11月17日,蒙多基里省警方联合桔井省警方,抓获一名长期性侵继女的男子。该男子已被法院判处12年监禁。 据警方通报,男子从2019年起多次性侵继女,当时女孩年仅9岁,侵害一直持续到她15岁。 今年1月7日,女孩向警方报案,男子随后潜逃,直到11月17日被抓获。据报道,受害女孩目前仍遭受严重心理创伤。 PS:建议直接枪毙😄

18 Nov 2026, 09:30 UTC≈1,800 views1 reactionsread 18 November 2026
Photo

#西港 #网友投稿 小市场旁边有宪兵检查民房,排查没护照跟电炸人员,有电脑的收起来,没护照的出去躲一躲。 🖥订阅:@rj111 ✉️投稿:@pei_8

❤1

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

Posts edited after publishing

@rj111 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
15 November 2026
Most recent edit
15 November 2026

Posts recorded as deleted after publishing

We recorded 6 posts on @rj111 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.

First seen missing
9 August 2026
Most recent seen missing
9 November 2026
Median time before seen missing
28 hours
Seen missing in the last 30 days
2

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

10 Nov 2026, 16:54 UTCAnonymous Poll239 voters

为了频道后期素材更好的收集更新,你目前所在的地区是,请选择目前所在的地区👇

  1. 马来西亚🇲🇾10%
  2. 柬埔寨🇰🇭76%
  3. 菲律宾🇵🇭2%
  4. 泰国🇹🇭2%
  5. 越南🇻🇳3%
  6. 缅甸🇲🇲2%
  7. 老挝🇱🇦1%
  8. 其他国家5%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 732 most recent posts we hold, published 7 August 2026 to 18 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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.

Mentions

Named by 3 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.

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

“柬埔寨安全快讯@rj111” (@rj111), 13,485 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/rj111.

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.