Telegram RegisterThe public register of Telegram
Telegram profile photo for 柬埔寨-日用百货

Channel

柬埔寨-日用百货

@jpzriyong

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

10subscribers

+0 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002644626875
TypeChannel
Username@jpzriyong
CreatedBetween 1 March 2025 and 23 June 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/jpzriyong

Growth

1011 Aug 2026, 11:16 — 10 subscribers12 Aug 2026, 10:33 — 10 subscribers11 Aug 2026, 11:1612 Aug 2026, 10:33
2 measurements taken within a single day. 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 9–11 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 10:3310no change
11 Aug 2026, 11:1610first reading

Engagement

7 posts held, back to 23 June 2025the 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 7 posts for this entry, the most recent from 14 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
3,110
Videos
13
Links
1

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

14 May 2026, 04:42 UTC4 viewsread 12 August 2026

国内,客家话,闽南语,找配音员,一天1小时以下,30,一天一小时以上35,一天2小时以上40,时间,年龄不限,男女不限,有意联系

23 Jun 2025, 07:43 UTC228 viewsread 12 August 2026

大哥们,款式太多,不好找,可点击下方搜索可以更快找到 ❤️床品家纺❤️ #被芯 #蚕丝被 #抱枕 #毛毯 #枕头 #娃娃 #天丝 #u型枕 #四件套 #冰丝 #床笠 #脚垫 #迪士尼 #夏凉被 #床帘 #冰垫 #坐垫 #乳胶凉席 #凉席 #一次性四件套 ❤️家居清洁❤️ #一次性烟灰缸 #烟灰缸 #灭烟沙 #内衣清洗液 #洗衣液 #留香珠 #洗衣凝珠 #洗衣机清洗液 #洗衣机清洁液 #洁厕灵 #洗洁精 #晾衣架 #脏衣篓 #蓝泡泡 #马桶清洁剂 #马桶垫 #一次性马桶刷 #泡腾片 #管道疏通剂 #马桶刷 #蓝泡泡 #马桶清洁剂 #马桶垫 #泡腾片 #管道疏通剂 #马桶刷 #鞋架 #鞋刷 #烘鞋器 #全身镜 #杀虫剂 #蚊香 #灭蚊灯 #花露水 #电子蚊香液 #消毒液 #香薰 #空气清新剂 #洗衣机清洁剂 #地板清洁片 #垃圾袋 #垃圾架 #垃圾桶 #扫把套装

23 Jun 2025, 07:41 UTC78 viewsread 12 August 2026
Photo

❤️真空水波纹排钩❤️ 分开收纳,各种物件都可挂1秒安装即可使用不等待,高颜值水波纹美观,简约家居稳固承重,挂东西不摇晃,加长挂钩,可折叠,节省空间! #挂钩 #收纳

23 Jun 2025, 07:41 UTC102 viewsread 12 August 2026
Photo

❤️多巴胺圆球挂钩❤️ 旋转上墙1秒安装无痕拆卸位置随心调,品质细节贴心,无处不在! 可选颜色奶白粉,奶白红! #挂钩 #收纳

23 Jun 2025, 07:41 UTC124 viewsread 12 August 2026
Photo

❤️手指理线器❤️ 颜色随机 钥匙,耳机,数据线,每天给自己点一个赞,免打孔,轻松收纳,用途多多!办公桌在也不是乱糟糟了😊 #理线器 #收纳

23 Jun 2025, 07:41 UTC152 viewsread 12 August 2026
Photo

❤️花香洁厕❤️ 剂马桶去污,除垢留香,深层除垢,洁净光亮不伤瓷面!科技改变生活六大卖点,去垢因子,快速去痘,深层分解温和配方,淡雅花香,不伤瓷面! #洁厕灵

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

Citation-graph rank

Citation-graph rank — 108,838 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“柬埔寨-日用百货” (@jpzriyong), 10 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/jpzriyong.

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.