请滑到最上面,耐心观看,都是干货,请务必仔细观看!

Channel
(个人经历)刘聪
@jianquanzidaohang
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
14subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002731032275 |
|---|---|
| Type | Channel |
| Username | @jianquanzidaohang |
| Created | 8 July 2025 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 4 times, most recently 13 September 2026 |
| On Telegram | t.me/jianquanzidaohang |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 08:08 | 14 | -1 |
| 11 Aug 2026, 23:16 | 15 | no change |
| 7 Aug 2026, 14:48 | 15 | first reading |
Engagement
4 posts held, back to 8 July 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 4 posts for this entry, the most recent from 3 January 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
21 reactions across 2 posts, in 5 distinct kinds. The most used accounts for 76.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 16 | 76.2% | |
| 🤣 | 2 | 9.52% | |
| 👍 | 1 | 4.76% | |
| 💯 | 1 | 4.76% | |
| 🤡 | 1 | 4.76% |
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 4 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 21 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 8 July 2025 to 3 January 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.
Recent posts
前言1️⃣ 本人(刘聪)是于2018年就孤身踏入了柬埔寨这片土地,从最早的狗推一步步走到今天,回想当时来这里的原因和经历,也是感慨颇多,当时在国内还只是个公司策划,虽然丰衣足食、家庭美满。但谁没想过不靠家里,白手起家的英雄梦,记得当时只是在公司无聊的时候搜,如何暴富,然后大数据就推送给了我一个词:出国工作。也许是从未出过国,本人又是喜欢乱跑的性格,于是在机缘巧合下在百度贴吧找到了一名人事,当时听到柬埔寨,我还以为是国内的某个小城市,后面才得知是神秘莫测的东南亚,在经过1个月的自我思想工作准备,再三对比了工作环境和薪资待遇后毅然决然的去到广州搭上了飞往柬埔寨的航班,依稀记得当时飞机落地我还穿着不适合东南亚的厚衣服,第一次体验到热带闷热的气候,最重要的是海关要小费,所以对柬埔寨这个国家第一印象并不好,给了小费办理完落地签出了机场,看着没有一点信号的手机,只能去寻找举牌接机的人,所幸是找到了,第一次见到这么黑的人,给我带到了一辆黑色面…
❤7💯1🤡1
第四篇5️⃣关于禁足和找工作事项 人的天性就是向往自由,尤其是经历过不赚钱的公司或黑公司就更加向往不禁足的公司。但换位思考如果你是公司老板会将一个赚钱的项目放在不禁足随意进出或外宿的公司吗?下面员工可能上个厕所就跑了,毕竟要考虑的太多,比如:现在外界信息干扰,很多人事画饼把人挖走。工作有点不顺心直接跑路。跟外面柬妹儿分手了跑了。即使是在国内工作很多公司也会压工资或压身份证保障公司的人员流动不可控因素。任何项目都需要学习和沉淀,好不容易沉淀好了,人跑了,跑的时候还带你几个人跑,哪个公司受得了呢? 现在所有园区都是需要报备的,除了南海,但是南海押护照,这是最容易出事的。因为南海普遍为快杀和博彩盘且国盘占比在同期其他园区比例极高,目前国内打击国内盘极严,卧底更是渗透多,且所有网络监控都被红客监控,没收网是因为要抓管理和老板的大鱼,让他们返脏(我同学透露给我的,在某省刑侦任职副队)举个例子:我朋友19年的时候做博彩盘,在海纳天,那时候南…
❤9🤣2👍1
Channel created
Showing the 4 most recent of 4 posts we hold for @jianquanzidaohang. 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.
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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“(个人经历)刘聪” (@jianquanzidaohang), 14 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/jianquanzidaohang.
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.