🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178712239799 🎰 半价福利活动杭州出击协会群 ⚠️ 抽奖说明: 参加抽奖的,必须要写报告交给会长,不出击的狼友不要参加,参加的不去会被群里与老师拉黑,中奖5日内必须出击 超时作废. 💁 参与情况:59达标 / 66报名 🔋 人品加成:154票 ⚡️× 9 🎅 联系领奖:@上城区自聊香香 @xiangxiang801616 1. yy y⚡️× 7 奖品:半价P优惠券 祝大家心想事成好运连连!

Channel
杭州出击协会会长频道
@huizdr001
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
9,870subscribers
-365 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1004294608291 |
|---|---|
| Type | Channel |
| Username | @huizdr001 |
| Created | 6 June 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/huizdr001 |
Topic
Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 12:55 | 9,870 | -63 |
| 11 Sept 2026, 16:42 | 9,933 | -90 |
| 9 Sept 2026, 02:17 | 10,023 | -53 |
| 3 Sept 2026, 15:41 | 10,076 | -8 |
| 2 Sept 2026, 06:23 | 10,084 | +792 |
| 30 Aug 2026, 16:25 | 9,292 | -105 |
| 27 Aug 2026, 11:57 | 9,397 | -816 |
| 26 Aug 2026, 09:15 | 10,213 | +21 |
| 25 Aug 2026, 07:28 | 10,192 | +5 |
| 24 Aug 2026, 08:43 | 10,187 | +25 |
| 22 Aug 2026, 18:17 | 10,162 | +14 |
| 21 Aug 2026, 05:52 | 10,148 | -55 |
| 20 Aug 2026, 08:22 | 10,203 | -71 |
| 19 Aug 2026, 11:53 | 10,274 | +9 |
| 18 Aug 2026, 14:36 | 10,265 | -40 |
| 17 Aug 2026, 13:07 | 10,305 | +20 |
| 16 Aug 2026, 04:09 | 10,285 | +20 |
| 14 Aug 2026, 12:16 | 10,265 | +51 |
| 13 Aug 2026, 05:48 | 10,214 | +58 |
| 12 Aug 2026, 08:11 | 10,156 | first reading |
Engagement
35 posts held, back to 6 June 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 32 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.79%
- avg views ÷ 9,870 subscribers
- Avg views / post
- 177
- 6 posts measured
- Reaction rate
- 0.451%
- reactions ÷ views · ER floor
- Posts in window
- 6
- of 35 held
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 2 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 35 (6 June 2026 – 29 August 2026) |
| Views total | 1,061 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 06:41 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.
Reaction mix
17 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 82.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 14 | 82.4% | |
| ❤ | 3 | 17.6% |
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 9 of the 35 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 17 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 35 most recent posts we hold, published 6 June 2026 to 29 August 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
关于大家关心的这个月积分清零事情,本群管理员做以下详细介绍;这个月群积分清零在9月1号00:00开始!清零后将采取奖励机制;对于🈶原价出击狼友奖励1500积分: 🈶优惠活动出击记录狼友+【本月水群前20名(第11-20名)奖励500积分.水群前10名(第1-10名)奖励1000积分.以上奖励只领取一次不可以叠加领取!】清零后找会长直接来领取!
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178748028036 🎰 特别优惠活动诗诗老师 ⚠️ 抽奖说明: 参加抽奖的,必须要写报告交给会长,不出击的狼友不要参加,参加的不去会被群里与老师拉黑,中奖5日内必须出击 超时作废. 💁 参与情况:47达标 / 50报名 🔋 人品加成:60票 ⚡️× 9 🎅 联系领奖:@拱墅区诗诗老师 @q7777777az 1. waou ya⚡️× 9 奖品:6折优惠券只要400P 2. 独具一 葛 奖品:6折优惠券只要400P 祝大家心想事成好运连连!
🎰 优惠活动上城区葡萄老师 📮 参与条件: 🌏️ 归属地 浙江 🪪 必须设置用户名 🎫 加入-杭州出击协会会长频道 🎫 加入-杭州出击协会 └ 🎟️ 发言数大于 2 条 🎫 加入-朋友圈 🎁 奖品内容: 💰️ 7折优惠只要400P × 1 ⚠️ 抽奖说明: 参加抽奖的,必须要写报告交给会长,不出击的狼友不要参加,参加的不去会被群里与老师拉黑,中奖5日内必须出击 超时作废. 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月31日 17时27分00秒
👍1
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178738175233 🎰 优惠活动小舞老师 ⚠️ 抽奖说明: 参加抽奖的,必须要写报告交给会长,不出击的狼友不要参加,参加的不去会被群里与老师拉黑,中奖5日内必须出击 超时作废. 💁 参与情况:41达标 / 41报名 🔋 人品加成:83票 ⚡️× 9 🎅 联系领奖:@小舞老师 @aldhdbs 1. jie year⚡️× 9 奖品:7折优惠券 祝大家心想事成好运连连!
👍1
今日竞拍活动🈶4位新老师搞活动,大家🈶积分的抓紧使用吧,月底了不用过时就清零了
🎰 半价优惠活动沫沫酱老师 📮 参与条件: 🌏️ 归属地 浙江 🪪 必须设置用户名 🎫 加入-杭州出击协会会长频道 🎫 加入-杭州出击协会 └ 🎟️ 发言数大于 2 条 🎫 加入-沫沫的黑森林 🎁 奖品内容: 💰️ 半价优惠只要300P × 1 ⚠️ 抽奖说明: 参加抽奖的,必须要写报告交给会长,不出击的狼友不要参加,参加的不去会被群里与老师拉黑,中奖5日内必须出击 超时作废. 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月29日 16时16分00秒
🎰 特别优惠活动诗诗老师 📮 参与条件: 🌏️ 归属地 浙江 🪪 必须设置用户名 🎫 加入-杭州出击协会会长频道 🎫 加入-杭州出击协会 └ 🎟️ 发言数大于 2 条 🎫 加入-杭州诗诗的后花园 🎁 奖品内容: 💰️ 6折优惠券只要400P × 2 ⚠️ 抽奖说明: 参加抽奖的,必须要写报告交给会长,不出击的狼友不要参加,参加的不去会被群里与老师拉黑,中奖5日内必须出击 超时作废. 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月28日 15时02分00秒
🎰 优惠活动小舞老师 📮 参与条件: 🌏️ 归属地 浙江 🪪 必须设置用户名 🎫 加入-杭州出击协会会长频道 🎫 加入-杭州出击协会 └ 🎟️ 发言数大于 2 条 🎫 加入-杭州拱墅小舞的池塘 🎁 奖品内容: 💰️ 7折优惠券 × 1 ⚠️ 抽奖说明: 参加抽奖的,必须要写报告交给会长,不出击的狼友不要参加,参加的不去会被群里与老师拉黑,中奖5日内必须出击 超时作废. 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年08月27日 15时02分00秒
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178706255509 🎰 柳柳老师优惠福利杭州出击协会群 ⚠️ 抽奖说明: 参加抽奖的,必须要写报告交给会长,不出击的狼友不要参加,参加的不去会被群里与老师拉黑,中奖5日内必须出击 超时作废. 💁 参与情况:43达标 / 64报名 🔋 人品加成:104票 ⚡️× 9 🎅 联系领奖:@上城区柳柳老师 @liuliu_y 1. 勇敢牛牛 第五重⚡️× 9 奖品:优惠卷100 2. Chris⚡️× 9 奖品:优惠卷100 3. Clow Read(封山育林)⚡️× 9 奖品:52红包🧧奖励 4. 小羊(中奖版)⚡️× 9 奖品:52红包🧧奖励 祝大家心想事成好运连连!
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178706104877 🎰 七夕优惠活动杭州出击协会群 ⚠️ 抽奖说明: 参加抽奖的,必须要写报告交给会长,不出击的狼友不要参加,参加的不去会被群里与老师拉黑,中奖5日内必须出击 超时作废. 💁 参与情况:45达标 / 52报名 🔋 人品加成:67票 ⚡️× 9 🎅 联系领奖:@余杭区教师小晴 @qianxi9915 1. Ickzew Okdnsuoie⚡️× 5 奖品:优惠券100 2. Clow Read(封山育林)⚡️× 9 奖品:优惠券100 3. mason ooo⚡️ 奖品:优惠券100 祝大家心想事成好运连连!
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178706016049 🎰 七夕优惠券杭州出击协会群 ⚠️ 抽奖说明: 参加抽奖的,必须要写报告交给会长,不出击的狼友不要参加,参加的不去会被群里与老师拉黑,中奖5日内必须出击 超时作废. 💁 参与情况:37达标 / 38报名 🔋 人品加成:64票 ⚡️× 9 🎅 联系领奖:@柠檬老师 @ningmengaa6 1. Clow Read(封山育林)⚡️× 9 奖品:优惠卷200 2. 不吃香菜⚡️× 9 奖品:优惠卷200 祝大家心想事成好运连连!
👍1
Showing the 12 most recent of 35 posts we hold for @huizdr001. 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.
Posts edited after publishing
@huizdr001 edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 18 August 2026
- Most recent edit
- 28 August 2026
Mentions
Named by 6 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.
@hz18988 · 51,84215 postsLotteryBest抽奖导航
@lotterynav · 174,17813 postsLotteryBest Bot
@LotteryBestBot · 99,18311 posts小晴频道
@qingqingjyz · 6,1812 posts杭州拱墅小舞的池塘
@wodejia77 · 5,4272 posts杭州协会老师视频频道
@ao901088 · 221 post香香兼职
@cbx801616 · 3,7271 post杭州柳柳Love巢
@liuliu0201 · 6,7181 post柠檬的家园
@mm55229 · 3,0121 post奶白🍼的小窝
@naibai520 · 9,5071 post杭州Nana小窝
@NNNYDPD · 1,9291 post
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“杭州出击协会会长频道” (@huizdr001), 9,870 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/huizdr001.
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.