🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178392800068 🎰 【杭州栖心地】 桃桃 @taotaoxiaomaomi 活动福利 💁 参与人数:57人 🔋 人品加成:2票 ⚡️× 9 🎅 联系领奖:@taotaoxiaomaomi 1. 士大夫 士大夫 奖品:400P名额 祝大家心想事成好运连连!
❤2

Channel
@HZqixindi_bangdan1
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
26,245subscribers
+2,676 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003256236376 |
|---|---|
| Type | Channel |
| Username | @HZqixindi_bangdan1 |
| Created | Between 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/HZqixindi_bangdan1 |
Giveaways & airdrops — 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 85% 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 |
|---|---|---|
| 18 Sept 2026, 11:57 | 26,245 | +392 |
| 16 Sept 2026, 06:40 | 25,853 | +89 |
| 14 Sept 2026, 16:16 | 25,764 | +158 |
| 13 Sept 2026, 02:21 | 25,606 | -47 |
| 11 Sept 2026, 01:37 | 25,653 | +182 |
| 8 Sept 2026, 05:01 | 25,471 | +174 |
| 5 Sept 2026, 00:56 | 25,297 | +149 |
| 3 Sept 2026, 09:06 | 25,148 | +19 |
| 1 Sept 2026, 23:58 | 25,129 | +73 |
| 1 Sept 2026, 00:37 | 25,056 | +144 |
| 31 Aug 2026, 00:14 | 24,912 | +142 |
| 30 Aug 2026, 01:59 | 24,770 | +53 |
| 29 Aug 2026, 00:24 | 24,717 | +105 |
| 28 Aug 2026, 01:13 | 24,612 | +165 |
| 26 Aug 2026, 22:45 | 24,447 | +101 |
| 25 Aug 2026, 19:23 | 24,346 | +22 |
| 24 Aug 2026, 20:05 | 24,324 | +173 |
| 23 Aug 2026, 07:04 | 24,151 | +64 |
| 21 Aug 2026, 20:55 | 24,087 | +141 |
| 20 Aug 2026, 19:55 | 23,946 | first reading |
6 posts held, back to 17 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 34 pages 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 6 posts for this entry, the most recent from 17 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
5 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 100.0% |
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 5 of the 6 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 17 May 2026 to 17 July 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.
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178392800068 🎰 【杭州栖心地】 桃桃 @taotaoxiaomaomi 活动福利 💁 参与人数:57人 🔋 人品加成:2票 ⚡️× 9 🎅 联系领奖:@taotaoxiaomaomi 1. 士大夫 士大夫 奖品:400P名额 祝大家心想事成好运连连!
❤2
🎰 【杭州栖心地】 桃桃 @taotaoxiaomaomi 活动福利 📮 参与条件: 🪪 必须设置用户名 🎫 加入-杭州栖心地报告区 🎫 加入-杭州栖心地工兵通告 🎫 加入-桃桃的频道空间 🎫 加入-杭州栖心地 🎫 加入-杭州栖心地榜单 🎁 奖品内容: 💰️ 400P名额 × 1 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年07月17日 15时37分00秒
骗子
✅【杭州栖心地认证】 花名: #小满 地址: #萧山区 课费: 700P/1200PP 私聊: @XsXiaoman 频道: @xsxiaoman1 备注: 🈲️偷拍、🈲️💊、🈲️喝酒的、🈲️无套、🈲大鸡鸡🈲️桩,拒绝还价。 【工兵优惠】:剩2名 2名400p/700pp优惠,需出报告 1️⃣群内发送“工兵”获取模板,填写并附火力值100以上截图及过往报告截图 2️⃣无过往报告需150火力值并附火力值截图 3️⃣将工兵模版发送 @qixindi_bot 报名,回复有效 4️⃣报名成功需一日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单 5️⃣个人原因取消不反还火力值
❤1
✅【杭州栖心地认证】 花名: #萱萱大魔王 地址: #拱墅区 课费: 600P/1200PP 私聊: @xxdmw678 频道: https://t.me/xxdam8 备注: 🈲️偷拍、🈲️💊、🈲️喝酒的、🈲️无套、🈲大鸡鸡🈲️桩,拒绝还价。 【工兵优惠】:剩2名 2名400p/700pp优惠,需出报告 1️⃣群内发送“工兵”获取模板,填写并附火力值100以上截图及过往报告截图 2️⃣无过往报告需150火力值并附火力值截图 3️⃣将工兵模版发送 @qixindi_bot 报名,回复有效 4️⃣报名成功需一日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单 5️⃣个人原因取消不反还火力值
❤1
✅【杭州栖心地认证】 花名: #静雅 地址: #余杭区 课费: 500P/1000PP 私聊: @qiqi227 频道: https://t.me/aig8886 备注: 🈲️偷拍、🈲️💊、🈲️喝酒的、🈲️无套、🈲大鸡鸡🈲️桩,拒绝还价。 【工兵优惠】:剩1名 共1名 400p/800pp,需出报告 1️⃣群内发送“竞拍1”参与 竞拍开始时间5月18日10:00 竞拍截止时间5月18日15:00 2️⃣竞拍成功后群内发送“工兵”, 需三小时内填写工兵模版提交 @qixindi_bot ,如超时奖品顺延给第二名以此类推,或取消资格 3️⃣竞拍成功后需一日内出击并出报告未按时出击或未提交出击报告将被移除群聊并挂黑名单 4️⃣竞拍成功后,个人取消不返还积分
❤1
Showing the 6 most recent of 6 posts we hold for @HZqixindi_bangdan1. 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 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“杭州栖心地工兵通告” (@HZqixindi_bangdan1), 26,245 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/HZqixindi_bangdan1.
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.