#供方 项目名称:一手批发 港卡美卡企业微信 首次 全部有现货 供应内容: 香港实名企业微信子号 自己拉主体 香港实名企业微信红标主体 美国实名企业微信红标主体 港卡企微 红标 不实名 网站自助下单https://qiyewx.top/shop/ 发卡机器人 @qiyevxjiqi_bot 联系方式: @yoyoka1 👉点击查看发布者👈 - 【累计发布 30 次】
Signed 【活死人】

Channel
@HSRpd
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
17,899subscribers
-441 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001871671264 |
|---|---|
| Type | Channel |
| Username | @HSRpd |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/HSRpd |
Ecommerce storefront — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 21:58 | 17,899 | +18 |
| 15 Sept 2026, 19:15 | 17,881 | +53 |
| 14 Sept 2026, 03:17 | 17,828 | +7 |
| 12 Sept 2026, 08:55 | 17,821 | +41 |
| 10 Sept 2026, 03:38 | 17,780 | -100 |
| 6 Sept 2026, 21:36 | 17,880 | -47 |
| 4 Sept 2026, 11:16 | 17,927 | -38 |
| 3 Sept 2026, 01:15 | 17,965 | -22 |
| 2 Sept 2026, 00:53 | 17,987 | -19 |
| 1 Sept 2026, 03:03 | 18,006 | -18 |
| 30 Aug 2026, 23:04 | 18,024 | -33 |
| 30 Aug 2026, 00:09 | 18,057 | -49 |
| 28 Aug 2026, 23:25 | 18,106 | -33 |
| 27 Aug 2026, 20:45 | 18,139 | -23 |
| 26 Aug 2026, 21:34 | 18,162 | -5 |
| 25 Aug 2026, 23:56 | 18,167 | -36 |
| 25 Aug 2026, 00:37 | 18,203 | -67 |
| 23 Aug 2026, 11:05 | 18,270 | -63 |
| 21 Aug 2026, 19:07 | 18,333 | -7 |
| 21 Aug 2026, 11:00 | 18,340 | first reading |
412 posts held, back to 21 August 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 24 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. It is computed over the 17 of 201 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 412 (21 August 2026 – 3 September 2026) |
| Views total | 17,433 |
| Reactions total | 118 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 08:58 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.
215 reactions across 17 posts, in 3 distinct kinds. The most used accounts for 47.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 103 | 47.9% | |
| 🔥 | 99 | 46.0% | |
| ❤ | 13 | 6.05% |
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 30 of the 412 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 215 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 412 most recent posts we hold, published 21 August 2026 to 3 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.
#供方 项目名称:一手批发 港卡美卡企业微信 首次 全部有现货 供应内容: 香港实名企业微信子号 自己拉主体 香港实名企业微信红标主体 美国实名企业微信红标主体 港卡企微 红标 不实名 网站自助下单https://qiyewx.top/shop/ 发卡机器人 @qiyevxjiqi_bot 联系方式: @yoyoka1 👉点击查看发布者👈 - 【累计发布 30 次】
Signed 【活死人】
#供方 项目名称:一手批发 港卡美卡企业微信 首次 全部有现货 供应内容: 香港实名企业微信子号 自己拉主体 香港实名企业微信红标主体 美国实名企业微信红标主体 港卡企微 红标 不实名 批发各种港卡首次业务,有量有价 网站自助下单https://qiyewx.top/shop/ 发卡机器人 @qiyevxjiqi_bot 联系方式: @yoyoka1 👉点击查看发布者👈 - 【累计发布 29 次】
Signed 【活死人】
#需方 项目名称:地推十名子号 需求内容:谁做地推十名子号的叫我 支持活死人担保 靠谱的来 具体细聊 联系方式:@aa569866 👉点击查看发布者👈 - 【累计发布 5 次】
Signed 【活死人】
#供方 项目名称: 供应内容: 联系方式 主营业务🍉 1️⃣企业微信 真机绿 云机绿 均有🔸.直登红 2️⃣公众号🔸服务号🔸云机公众号🔸 视频号蓝V🔸 3️⃣H5小程序🔸微购相册🔸云机红 4️⃣云手机🔸绿子代做🔸红标 5️⃣芝麻客服🔸米多克🔸微博号🔸陌陌🔸小红书 6:快手小店🔸 抖音小店🔸抖音来客🔸 7:云机 二次人脸红 可 开通邮箱 联系客服:@vp125126 👉点击查看发布者👈 - 【累计发布 2 次】
Signed 【活死人】
#供方 请按照以下模版填写: 项目名称:公众号服务号 供应内容:大量出三年公众号可带活管理员 日租买断都有货 联系方式:@qwer45006 👉点击查看发布者👈 - 【累计发布 2 次】
Signed 【活死人】
#供方 项目名称:企业微信二次人脸 供应内容:云机红标号(可开通邮箱)/云机绿标客服子号 联系方式:@xiangyun95 @xiaomin996 跑路了 ,大家注意,量大一些必跑路 👉点击查看发布者👈 - 【累计发布 15 次】
Signed 【活死人】
#供方 项目名称:一手批发 港卡美卡企业微信 首次 全部有现货 供应内容: 香港实名企业微信子号 香港实名企业微信红标主体 美国实名企业微信红标主体 港卡企微 红标 不实名 批发各种港卡首次业务,有量有价 网站自助下单https://qiyewx.top/shop/ 发卡机器人 @qiyevxjiqi_bot 联系方式: @yoyoka1 👉点击查看发布者👈 - 【累计发布 28 次】
Signed 【活死人】
#需方 【需求】 项目名称:企业微信/主体/普微 需求内容:长期大量收远控投屏企业独苗号,绿标子号,成品红标子号,普通私人微信号,欢迎实力号商一线地推来对接,长期稳定包养,风控已经过了,还把号当宝漫天要价的不要来,没点逼本事还要先款的垃圾勿扰,公群报备先号后款 优势:价高款稳当天结,包养到明年 联系方式: @AnningWT2030 群链接:https://t.me/+yv3B7uAphRQ0MmM1 👉点击查看发布者👈 - 【累计发布 5 次】
Signed 【活死人】
#需方 项目名称:地推团队企业微信白标 需求内容:地推团队有企业微信学校白标的联系 联系方式:@w11888 👉点击查看发布者👈 - 【累计发布 7 次】
Signed 【活死人】
#需方 项目名称:地推团队企业微信白标 需求内容:地推团队有企业微信学校白标的联系 联系方式:@w11888 👉点击查看发布者👈 - 【累计发布 6 次】
Signed 【活死人】
#供方 项目名称:曝光跑路狗 供应内容:今天主体自己做的没够,找这个逼拿两个主体一个两分钟秒死,一个没给上超管直接就不售后 联系方式: 狗逼一个,有他共同群的联系我,我去曝光有图有记录 钱给他留着买棺材了 @nuanfeng33 谁找这个逼拿货谁倒霉 👉点击查看发布者👈 - 【累计发布 1 次】
Signed 【活死人】
#供方 项目名称:满半年认证服务号 供应内容:长期大量出 1.企业认证服务号,满三月服务号 2.视频号蓝v认证 3.不认证公众号 服务号一拖五 4.微信小店 联系方式:@xiaoben189 联系频道:@wxgzh168 👉点击查看发布者👈 - 【累计发布 3 次】
Signed 【活死人】
Showing the 12 most recent of 412 posts we hold for @HSRpd. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“企业微信 钉钉(供需1群) 【活死人】” (@HSRpd), 17,899 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/HSRpd.
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.