希望大家在的这片神奇的土地,能够越来越好!!!
❤6🏆1

Channel
@wzjpz
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
105subscribers
-12 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002495543086 |
|---|---|
| Type | Channel |
| Username | @wzjpz |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/wzjpz |
Other / unclassifiable — 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 26 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.
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 1 other registered channel. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @ywsylm/1681 Aug 2025, 08:44 UTC | @wzjpz/199 · this entry1 Aug 2025, 08:44 UTC | 1.00 | under a minute |
| @ywsylm/1772 Aug 2025, 07:28 UTC | @wzjpz/208 · this entry2 Aug 2025, 07:28 UTC | 1.00 | under a minute |
| @wzjpz/210 · this entry2 Aug 2025, 11:42 UTC | @ywsylm/1792 Aug 2025, 11:42 UTC | 1.00 | under a minute |
| @ywsylm/1803 Aug 2025, 07:18 UTC | @wzjpz/211 · this entry3 Aug 2025, 07:18 UTC | 1.00 | under a minute |
| @wzjpz/213 · this entry4 Aug 2025, 07:32 UTC | @ywsylm/1824 Aug 2025, 07:33 UTC | 1.00 | under a minute |
| @wzjpz/215 · this entry5 Aug 2025, 07:22 UTC | @ywsylm/1845 Aug 2025, 07:22 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @ywsylm | 7 (7/7 hand-verifiable sample passed) | 1.00 | under a minute | @ywsylm (4–3) |
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. None of the 4 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 7 comparable posts for this entry, running 1 August 2025 to 6 August 2025. 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @ywsylm. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 11 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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 17:07 | 105 | -2 |
| 3 Nov 2026, 11:30 | 107 | -1 |
| 27 Oct 2026, 05:09 | 108 | -1 |
| 19 Oct 2026, 18:39 | 109 | -1 |
| 12 Oct 2026, 10:02 | 110 | -4 |
| 2 Oct 2026, 05:01 | 114 | -2 |
| 16 Sept 2026, 11:37 | 116 | +2 |
| 23 Aug 2026, 05:45 | 114 | -2 |
| 16 Aug 2026, 16:49 | 116 | -1 |
| 9 Aug 2026, 05:15 | 117 | no change |
| 7 Aug 2026, 17:18 | 117 | first reading |
11 posts held, back to 1 August 2025 — 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 page 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 11 posts for this entry, the most recent from 9 August 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
13 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 69.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 69.2% | |
| 😍 | 2 | 15.4% | |
| 🏆 | 1 | 7.69% | |
| 👍 | 1 | 7.69% |
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 5 of the 11 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 1 August 2025 to 9 August 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
希望大家在的这片神奇的土地,能够越来越好!!!
❤6🏆1
宇宙母亲,真的太神奇了,更美了……
希望大家今天都能有好运发生!!!
凌晨五点的金边,美的不像话!!!神奇的宇宙!!!
😍2
🎉【竞猜活动战报&最新规则】🎉 📊 最新战况:8月6号 ☹️本期八位高手竞逐,未能精准命中! ☹️🍄🖥🖥 🔤大奖已被累计, ☹️当前奖池👁🃏👁🔤(增幅🃏😽😽%) 🎯参与方式➡️任选其一➡️ 1️⃣当日 @wzjpz2 聊天达188条(内容以柬埔寨🇰🇭吃喝玩乐为主,🚫禁止水群) 2️⃣找管理报备后,拉3️⃣个在柬华人进群(❌僵尸粉/协议号勿扰,发现即踢,包括活动参与人) ⏰活动开奖时间:次日中国时间15:00 🎮活动规则: ✅达标小伙伴报出0-9任意数字 👶由宝宝 @wzjpz5 统计记录 🔗永旺哈希官方转账1trx后,取区块哈希值最后一位为开奖数字 🏆 奖励机制 ✅流局:奖金自动累积至下期(奖池越滚越大!) ✅唯一胜者:独享当期全部奖池,直接抱走奖金! ✅多人中标:均分奖池,见者有份! 🔥活动火热进行中… ✨ 下一位赢家会是你吗? 📈 奖池金额持续增长中,参与越多,奖金越高! 🚀立即参与,把奖金带回家! ➡️点…
❤1
🎉【竞猜活动战报&最新规则】🎉 📊 最新战况:8月5号 ☹️本期九位高手竞逐,未能精准命中! ☹️🍄🖥🖥 🔤大奖已被累计, ☹️当前奖池🃏🔴🃏🔤(增幅👁😽😽%) 🎯参与方式➡️任选其一➡️ 1️⃣当日 @wzjpz2 聊天达188条(内容以柬埔寨🇰🇭吃喝玩乐为主,🚫禁止水群) 2️⃣找管理报备后,拉3️⃣个在柬华人进群(❌僵尸粉/协议号勿扰,发现即踢,包括活动参与人) ⏰活动开奖时间:次日中国时间15:00 🎮活动规则: ✅达标小伙伴报出0-9任意数字 👶由宝宝 @wzjpz5 统计记录 🔗永旺哈希官方转账1trx后,取区块哈希值最后一位为开奖数字 🏆 奖励机制 ✅流局:奖金自动累积至下期(奖池越滚越大!) ✅唯一胜者:独享当期全部奖池,直接抱走奖金! ✅多人中标:均分奖池,见者有份! 🔥活动火热进行中… ✨ 下一位赢家会是你吗? 📈 奖池金额持续增长中,参与越多,奖金越高! 🚀立即参与,把奖金带回家! ➡️点…
🎉【竞猜活动战报&最新规则】🎉 📊 最新战况:8月4号 • 本期八位高手竞逐,一位 @Sudamei 精准命中! • 564美元大奖被幸运儿独揽! 🎯参与方式(任选其一): 1️⃣ 当日 @wzjpz2 聊天达188条(内容以柬埔寨🇰🇭吃喝玩乐为主,🚫禁止水群) 2️⃣ 找管理报备后,拉3个在柬中国👫活人进群(❌僵尸粉/协议号勿扰,发现即踢,包括活动参与人) ⏰活动开奖时间:次日中国时间15:00 🎮活动规则: ✅达标小伙伴报出0-9任意数字 👶由宝宝 @wzjpz5 统计记录 🔗永旺哈希官方转账1trx后,取区块哈希值最后一位为开奖数字 🏆 奖励机制 ✅ 流局:奖金自动累积至下期(奖池越滚越大!) ✅ 唯一胜者:独享当期全部奖池,直接抱走奖金! ✅ 多人中标:均分奖池,见者有份! 🔥 活动火热进行中… ✨ 下一位赢家会是你吗? 📈 奖池金额持续增长中,参与越多,奖金越高! 🚀 立即参与,把奖金带回家! 👉 点…
🎉 【竞猜活动战报 & 规则说明】 🎉 📊 最新战报 8 月 3 号 • 本期五位挑战者遗憾未命中目标,188美元奖金已全部注入奖池! • 当前奖池累计:😍(👁🃏👁😠增幅高达 🃏😽😽😽%!) 🎯参与方式(任选其一): 1️⃣ 当日 @wzjpz2 聊天达188条(内容以柬埔寨🇰🇭吃喝玩乐为主,🚫禁止水群) 2️⃣ 找管理报备后,拉3个在柬中国👫活人进群(❌僵尸粉/协议号勿扰,发现即踢,包括活动参与人) ⏰活动开奖时间:次日中国时间15:00 🎮活动规则: ✅达标小伙伴报出0-9任意数字 👶由宝宝 @wzjpz5 统计记录 🔗永旺哈希官方转账1trx后,取区块哈希值最后一位为开奖数字 🏆 奖励机制 ✅ 流局:奖金自动累积至下期(奖池越滚越大!) ✅ 唯一胜者:独享当期全部奖池,直接抱走奖金! ✅ 多人中标:均分奖池,见者有份! 🔥 活动火热进行中… ✨ 下一位赢家会是你吗? 📈 奖池金额持续增长中,参与越多,奖金…
❤2
❤️❤️❤️❤️❤️❤️❤️❤️❤️ 🥰🥰美食探店补贴活动来啦! 凡是在群里分享好吃的美食店照片/视频 📸🎮经过我们的美食鉴定官 亲自鉴定通过后➡️(如果多人同时发,就按照拍的最好的人评定💯评定通过我们收录之后,已经收录的店铺暂不参与此次活动)即可获得该单探店金额补贴!💸 💵 金额上限:2️⃣8️⃣-1️⃣8️⃣8️⃣美元 💵 我们的美食鉴定官会按照 公平公正 ⚖️的原则评定,绝对 不存在黑幕 ❌放心参与🥰 ⭐️⭐️【永旺今日随机搭子召集令】 抓一个饭搭子/酒友/逛gai搭子啦!🫧🫧 今天不想一个人发呆,随机揪⚡️–⚡️位,有可能辣辣的火锅,还有可能是吃下午茶品味甜甜的甜点🎂 还有各种各样的美食,等你一起去探店🍓 更有可能是去一起体验泰拳按摩spa,尽情的k歌,释放压力💪 ➡️➡️➡️本活动由 永旺商业联盟 ❤️❤️❤️❤️❤️❤️❤️❤️❤️ 😃😃 特别推出! 快来分享你发现的美食吧~ 🍽 ✨更多商家推荐和本地资讯吃喝玩乐请…
🎉 【竞猜活动战报 & 规则说明】 🎉 📊 最新战报 8 月 2 号 • 本期四位挑战者遗憾未命中目标,188美元奖金已全部注入奖池! • 当前奖池累计:😍(🃏🔴🃏😠增幅高达 👁😽😽%!) 🎯参与方式(任选其一): 1️⃣ 当日 @wzjpz2 聊天达188条(内容以柬埔寨🇰🇭吃喝玩乐为主,🚫禁止水群) 2️⃣ 找管理报备后,拉3个在柬中国👫活人进群(❌僵尸粉/协议号勿扰,发现即踢,包括活动参与人) ⏰活动开奖时间:次日中国时间15:00 🎮活动规则: ✅达标小伙伴报出0-9任意数字 👶由宝宝 @wzjpz5 统计记录 🔗永旺哈希官方转账1trx后,取区块哈希值最后一位为开奖数字 🏆 奖励机制 ✅ 流局:奖金自动累积至下期(奖池越滚越大!) ✅ 唯一胜者:独享当期全部奖池,直接抱走奖金! ✅ 多人中标:均分奖池,见者有份! 🔥 活动火热进行中… ✨ 下一位赢家会是你吗? 📈 奖池金额持续增长中,参与越多,奖金越…
❤️❤️❤️❤️❤️❤️❤️❤️❤️ 🥰【螺蛳姐姐の暴风安利】🥰 ——这是一碗让人又爱又恨的"臭宝"❤️🔥 💨"救命!这味道…"(捏鼻) 👅"真香!再来一口!"(疯狂嗦粉) 🔥热量炸弹?不存在! 🤪快乐干饭人,减肥明天再说! ✨【神仙配料大揭秘】✨ 🔸豆皮天妇罗:汤汁刺客!一口爆汁💦 🔸木耳仙子:咔哧咔哧自带BGM🎵 🔸花生狙击手:香到想单独买十斤! 🇨🇳这碗粉可是拿了"非遗皮肤"的柳州顶流! 💥【必杀技组合】💥 🐯虎皮猪脚:泡汤前是壮汉,泡汤后变软妹! 💣炸蛋:汤界海绵宝宝,吸水力MAX! 🐔卤鸡爪:建议泡到脱骨,直接嘬着吃~ 🔔响铃卷:汤笛演奏家,咬下去会唱歌! 🍜嗦粉TIP: ▫️粉要硬点才够飒! ▫️空心菜是官方CP! ▫️辣椒温柔刀,刀刀催人胖🌶 ▫️冰奶茶是续命神器❄️ 🦞【小吃天团】🦞 臭豆腐(臭味相投版) 麻辣小龙虾(撩人小妖精) 店铺定位:https://maps.app.goo.gl/q4Th24u…
👍1
Showing the 11 most recent of 11 posts we hold for @wzjpz. 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.
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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“我在柬埔寨 很想你” (@wzjpz), 105 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/wzjpz.
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.