Channel
@jpzwaimai
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
10subscribers
+1 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002563844007 |
|---|---|
| Type | Channel |
| Username | @jpzwaimai |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/jpzwaimai |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 10:38 | 10 | +1 |
| 29 Aug 2026, 22:23 | 9 | no change |
| 28 Aug 2026, 23:00 | 9 | first reading |
3 posts held, back to 4 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 3 posts for this entry, the most recent from 4 August 2025. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 2 of the 3 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 4 August 2025 to 4 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.
#柬埔寨本地生活 #海鲜 #小龙虾 #烧烤 优选新鲜好虾，肉质饱满好吃不贵！新鲜现做烤鱼味道一绝！鲜肉烤串杜绝冻货！ 小龙虾3斤只需36¥，烧烤+小龙虾寓意着今年的我们事业红红火火，前程似锦！ 备用下单号：@xiabang888 2️⃣4️⃣小时营业 ➖➖➖➖ ➖➖➖分割线➖➖➖➖➖➖➖ 【本频道发布内容不担保任何事项 请注意甄别 】 📍曝光大群： @xinwenbb 📍交流大群： @nanhai_YYY 📍美食交流： @jpzwaimai 📍求职频道： @iusyyy ➖➖➖➖ ➖➖➖分割线➖➖➖➖➖➖➖ 📲商务合作｜商家入驻：@wpio588 📲投稿曝光： @wpio588
#柬埔寨本地生活 #烧烤 零点烧烤24小时营业，外送随时待命。 吃烧烤选零点！ 吃烧烤选零点！ 吃烧烤选零点！ 吃了不后悔的烧烤，好吃不等待… 下单号：@longhau999 ➖➖➖➖ ➖➖➖分割线➖➖➖➖➖➖➖ 【本频道发布内容不担保任何事项 请注意甄别 】 📍曝光大群： @xinwenbb 📍交流大群： @nanhai_YYY 📍美食交流： @jpzwaimai 📍求职频道： @iusyyy ➖➖➖➖ ➖➖➖分割线➖➖➖➖➖➖➖ 📲商务合作｜商家入驻：@wpio588 📲投稿曝光： @wpio588
❤1
#柬埔寨本地生活 #鸭货 #周黑鸭 周黑鸭 正宗卤味木牌店 现卤现捞，秘制卤味，精选食材，麻辣香甜，好吃到停不下来！🔥 口味： 微辣（默认）、中辣、特辣 限时特惠： 满五送一，满十送二 卤味 鸭脖 鸭头 鸭心 鸭胗 鸭锁骨 鸭肠 鸭胗带 鸭爪 鸭翅 鸭舌 翅尖 鸡爪 牛肉 猪耳 龙虾尾 八爪鱼 墨鱼仔 鱿鱼须 还有各种素菜等等… 没滋味就吃周黑鸭 快来下单吧 🈺 @zhouheiya855 24小时营业 防失联➕道 @mupailuwei8 ➖➖➖➖ ➖➖➖分割线➖➖➖➖➖➖➖ 【本频道发布内容不担保任何事项 请注意甄别 】 📍曝光大群： @xinwenbb 📍交流大群： @nanhai_YYY 📍美食交流： @jpzwaimai 📍求职频道： @iusyyy ➖➖➖➖ ➖➖➖分割线➖➖➖➖➖➖➖ 📲商务合作｜商家入驻：@wpio588 📲投稿曝光： @wpio588
Showing the 3 most recent of 3 posts we hold for @jpzwaimai. 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.
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.
@jpzwaimai named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“柬埔寨本地美食商家频道” (@jpzwaimai), 10 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/jpzwaimai.
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.