25年初 一个长期合作的公司 因为一点矛盾 直接跟我取消合作了 那一两个月我很迷茫 因为那时候市场很缺公司 相当长的一部分时间里 我都在寻找稳定且好的公司 25年中 一个小公司 十几个人员 我们合作的很融洽 短短两个月时间 日均突破三万U交易额 借这件事 我想说的是 只要你本身有能力 当机会来临时 发展速度会超乎你的想象
👍13❤6❤🔥1🥰1

Channel
@hczpd
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
32,883subscribers
-883 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001653724687 |
|---|---|
| Type | Channel |
| Usernames | @fygzs000 @hczpd |
| Description | 欲买桂花同载酒 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 54 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/hczpd |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 22:38 | 32,883 | -2 |
| 5 Sept 2026, 17:37 | 32,885 | -65 |
| 3 Sept 2026, 20:59 | 32,950 | no change |
| 3 Sept 2026, 19:17 | 32,950 | -41 |
| 2 Sept 2026, 12:25 | 32,991 | -8 |
| 2 Sept 2026, 10:59 | 32,999 | -24 |
| 1 Sept 2026, 13:44 | 33,023 | -13 |
| 1 Sept 2026, 08:45 | 33,036 | -14 |
| 31 Aug 2026, 12:35 | 33,050 | -4 |
| 31 Aug 2026, 09:06 | 33,054 | -57 |
| 30 Aug 2026, 10:25 | 33,111 | no change |
| 30 Aug 2026, 07:06 | 33,111 | -18 |
| 29 Aug 2026, 11:45 | 33,129 | -5 |
| 29 Aug 2026, 09:05 | 33,134 | -14 |
| 28 Aug 2026, 10:16 | 33,148 | -2 |
| 28 Aug 2026, 08:26 | 33,150 | -19 |
| 27 Aug 2026, 09:54 | 33,169 | +1 |
| 27 Aug 2026, 05:36 | 33,168 | -12 |
| 26 Aug 2026, 08:46 | 33,180 | no change |
| 26 Aug 2026, 08:42 | 33,180 | first reading |
19 posts held, back to 18 May 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 65 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 4 September 2026 |
|---|---|
| Posts held | 19 (18 May 2026 – 4 September 2026) |
| Views total | 7,370 |
| Reactions total | 80 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Sept 2026, 07:17 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.
Lifetime counters from Telegram’s own channel header, read 8 September 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.
469 reactions across 18 posts, in 17 distinct kinds. The most used accounts for 43.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 203 | 43.3% | |
| 👍 | 113 | 24.1% | |
| 🤣 | 79 | 16.8% | |
| 🖕 | 22 | 4.69% | |
| 🥰 | 8 | 1.71% | |
| 🌚 | 7 | 1.49% | |
| 🎉 | 6 | 1.28% | |
| 👏 | 6 | 1.28% | |
| 🔥 | 5 | 1.07% | |
| 😁 | 5 | 1.07% | |
| 💯 | 4 | 0.853% | |
| 😍 | 4 | 0.853% | |
| 🆒 | 2 | 0.426% | |
| 🤯 | 2 | 0.426% | |
| ❤🔥 | 1 | 0.213% | |
| 👻 | 1 | 0.213% | |
| 🤔 | 1 | 0.213% |
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 18 of the 19 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 469 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 18 May 2026 to 4 September 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.
25年初 一个长期合作的公司 因为一点矛盾 直接跟我取消合作了 那一两个月我很迷茫 因为那时候市场很缺公司 相当长的一部分时间里 我都在寻找稳定且好的公司 25年中 一个小公司 十几个人员 我们合作的很融洽 短短两个月时间 日均突破三万U交易额 借这件事 我想说的是 只要你本身有能力 当机会来临时 发展速度会超乎你的想象
👍13❤6❤🔥1🥰1
目前 搞业务的 谁做新鲜血液 谁是傻逼 某些人都是依靠平台 蹭平台流量 最终内卷 你幸苦做流量最终也是为别人做嫁衣 押金可以加 价格可以抬 但不要再去吭哧吭哧做流量了 我已经很久没有怎么去做这方面的事了 我可以不赚 但不能让别人赚
❤8🎉1
最近国内很火的 嗯所谓男权 搞来搞去 最终获利的还是这些做自媒体的 喝毒鸡汤的得到一个不正确的三观 仅此而已 关于两性关系处理 中国男人 容易拎不清 总听别人 爱她就要对她好 要去付出 然后进行猛烈的追求 可是 热情一般是不会持续的 恋人又往往要陪伴很久 让你演三五天行 让你演个三五年 是个人都累 如果你把对方当短期伴侣 可以猛烈追求 拿出最多的资源塑造一个你能做到最好的自己 如果你需要长期关系 首先是接触 对方各方面是否合你心意 接触的人多与渣并不划等号 当你了解了 合你心意了 再去表达心意 也不迟 不要像吊长脑门一样 看见个长得不错的女的就去追 关于付出与承诺 付出这方面 谁都是爹生妈养的 没有谁欠谁的 你乐意就付出 不舒服就提 不要把自己绷得太紧 承诺 要慎重 不要给你吊一舔就什么都答应了 承诺了做不到反而适得其反 而且还会成为隐形捆绑
👍31❤15🎉2🆒2
😎自营业务·闲鱼代聊 鱼力❤️❤️❤️起➕三实名 即可上👍 1️⃣操作方式:腾讯会议·共享屏幕 价格 400的❤️❤️❤️/小时 450的❤️❤️❤️/小时 500的❤️❤️❤️/小时 600的❤️❤️❤️/小时 700的❤️❤️❤️/小时 - - - - - - - - - - - - - - - - - - - - - 🀄️🀄️🀄️@qiurao
❤6
不到24小时就收到转错 2470+5817+1323=9610U 各位转账还是要多核对 遇见我这种好点的也就是扣点手续费 遇见没格局的就直接跑路了 当然也理解各位很多时候都把闪租地址保存在地址本 闪租我只推荐自己做的 @fydgnbot 转错包退
❤13👍5
声明一下 离乱团队不卖 我群里吹牛逼瞎几把说的 別再问了 我真是开玩笑的呜呜呜
🖕22❤10😁5👍2🔥1
❤️离乱团队自营 👍收5000小额卡44点位 门槛400U 招微信群转小额车,门槛1500U 😙客服:@xueke
❤8👍2
今天派发了52个福利 感觉四处发也没啥意思 这样子吧 下周开始 @diyu @tujian 每周10个35 活跃即可参与抽奖 上口的可进养老群 每天都有抽奖福利
👍6
朋友做的项目 有需要可以看一下
🟢TG钱包闪兑|即时到账 ❌ 钱包互提 = 1U手续费 ✅ 换U宝闪兑 = 仅0.5U 👛 支持: OKpay|福利来|达利|爱赌钱包|未来钱包|PPay|YYPay 🔹全钱包互通 🔹即时到账 🔹24小时自助 🔹TG玩家首选 👇 立即兑换,省下每一笔手续费!
❤10
今天是6/21号 也是父亲节 为数不多 独属于男性的节日 不知道你是谁的儿子 又是谁的父亲 在传统文化中 男性往往被赋予着 负责任 要养家 要独立 等等重担 承担着生活中不可或缺的压力 就像这个节日一样 鲜花掌声宽慰 总是极少部分 男性也有诉求 也需要情绪价值 也需要鲜花与掌声 就在今天 @diyu 就为各位基霸们 送上点小福利 原本不在群内的 就不要再申请了
❤13🤔1
重新启用副群 可以打软广 也送点钱 感兴趣的进 https://t.me/tujian
❤5
Showing the 12 most recent of 19 posts we hold for @hczpd. 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 2 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.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“灰产总频道” (@hczpd), 32,883 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/hczpd.
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.