Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州蘇冉茶馆

Channel

杭州蘇冉茶馆

@HZcha6688

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

8,057subscribers

-637 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003926752971
TypeChannel
Username@HZcha6688
CreatedBetween 1 April 2026 and 7 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/HZcha6688

Growth

2,7708,6945,7328 August 2026 — 8,694 subscribers8 August 2026 — 8,639 subscribers11 August 2026 — 8,397 subscribers15 August 2026 — 7,833 subscribers18 August 2026 — 7,737 subscribers20 August 2026 — 7,690 subscribers24 August 2026 — 2,770 subscribers28 August 2026 — 4,237 subscribers31 August 2026 — 8,356 subscribers2 September 2026 — 8,566 subscribers8 September 2026 — 8,057 subscribers8,0578 August 20268 September 2026
11 measurements spanning 31 days, net -637. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,881–9,583 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 06:598,057-509
2 Sept 2026, 21:368,566+210
31 Aug 2026, 01:378,356+4,119
28 Aug 2026, 03:434,237+1,467
24 Aug 2026, 19:322,770-4,920
20 Aug 2026, 22:257,690-47
18 Aug 2026, 05:327,737-96
15 Aug 2026, 03:127,833-564
11 Aug 2026, 19:448,397-242
8 Aug 2026, 12:388,639-55
8 Aug 2026, 10:028,694first reading

Engagement

44 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.643%
avg views ÷ 8,057 subscribers
Avg views / post
51.8
23 posts measured
Reaction rate
0.709%
reactions ÷ views · ER floor
Posts in window
23
of 44 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 1 of 23 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 22 August 2026
Posts held44 (7 August 202622 August 2026)
Views total1,191
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 20:54 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.

What this channel posts

Video runtime
4m 55s
Average length
8s

Measured directly from 36 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.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
150.0%
👍150.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 2 of the 44 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 44 most recent posts we hold, published 7 August 2026 to 22 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

22 Aug 2026, 16:28 UTC24 viewsread 22 August 2026
Photo

#杭州 #滨江区1000以上 #滨江区极品莞服 #微信飞机 #DL #泳儿 🉑69🉑丝袜情趣🉑3p 🥐安排 @hzsr520 🥐私信限制联系 @suran520bot 🥐水费莞服pp23张💋

Signed 蘇冉

22 Aug 2026, 11:58 UTC74 viewsread 22 August 2026
Forwarded from @HZjx6688Photo

#杭州上城区 #少量毛 #丝袜制服 #加200可69蛇 #微信卡卡西 #噗噗 🦋安排 @hzsr520 🦋私信限制联系 @suran520bot 🦋水费 #1200p

Signed 蘇冉

22 Aug 2026, 10:59 UTC73 viewsread 22 August 2026
Forwarded from @fankuibaogao520Photo

天猫028-4哪吒,地址:拱墅区石桥铭苑东区,杭州07 百变甜妹哪吒杭州🆕人第一次 百变甜妹哪吒 ■ 168 /真🐻c /07 天然无整三点粉 ■ 皮肤雪白 笑容甜美 🈵🈵生命力 ■ 湖南妹子 性格开朗不见生 温柔体贴 ■ 百变甜妹 轻松驾驭各种风格 哪吒 #好评 【验证留名】:可留可匿 【验证日期】:2026年7月6日 【妹妹花名】: 【妹妹类型】:嫩妹 【妹子技能】:口,做 【人照几成】:8成 【目测年纪】:19 【身高身材】:155,75 【胸围大小】:b 【优点缺点】:很好看,特别嫩,性格挺开朗的 【过程报告】: 【简评总结】:有点美颜 但本身就长得相当好看 主要还真嫩 【最终评分】:9

Signed 蘇冉

22 Aug 2026, 10:55 UTC141 views1 reactionsread 22 August 2026
Photo

🥐 杭州cn,好评,真照,无套两次8小时

👍1

Signed 蘇冉

20 Aug 2026, 09:50 UTC6 viewsread 20 August 2026
Forwarded from @HZsm6688Photo

#杭州#宝宝#莹莹#07兼职#只上🚪 🉑 🈚️🍑🉑💋 🥓安排 @hzsr520 🥓私信限制联系 @suran520bot 🥓水费1300 🈚+300

Signed 蘇冉

20 Aug 2026, 07:13 UTC38 viewsread 20 August 2026
Forwarded from @HZjx6688Photo

#杭州 #LvLv #刚下海嫩妹可鸳鸯浴69口爆 #赵云小丸子 🥓安排 @hzsr520 🥓私信限制联系 @suran520bot 🥓水费2300pp

Signed 蘇冉

20 Aug 2026, 07:11 UTC45 viewsread 20 August 2026
Photo

#杭州 #上城绿地 #甜妹 #太阳城 #兼职学生 #小可 🉑外🉑✌ 🥓安排 @hzsr520 🥓私信限制联系 @suranbot 🥓水费2300pp

Signed 蘇冉

19 Aug 2026, 13:00 UTC40 viewsread 19 August 2026
Photo

#杭州#宝宝#果果#09少萝兼职#只上🚪 🉑 🈚️🍑🉑💋🉑69🉑🛀 🥓安排 @hzsr520 🥓私信限制联系 @suran520bot 🥓水费1200 pp2200 🈚+300

Signed 蘇冉

19 Aug 2026, 07:42 UTC124 viewsread 19 August 2026
Forwarded from @HZgs6688Photo

#杭州滨江 #萝莉 #雪白三点粉 #赵云HpHp 🉑69🉑🐍吻🉑情趣诱惑 🥓安排 @hzsr520 🥓私信限制联系 @suran520bot 🥓水费2300pp

Signed 蘇冉

19 Aug 2026, 07:22 UTC113 viewsread 19 August 2026
Forwarded from @fankuibaogao520Photo

#再次好评 【验证留名】:可留可匿 【验证日期】:2026.8@16 【妹妹花名】:倩倩 【妹妹类型】:嫩妹 【妹子技能】:正常口做 【人照几成】:7 【目测年纪】:25 【身高身材】:170左右,身材不错 【胸围大小】:b 【简评总结】:嫩妹,皮肤偏黄,不过很光滑,可以体验一下,情绪价值还是很到位,不过说话带点口音 【最终评分】:8 🥓水费2300pp

Signed 蘇冉

19 Aug 2026, 07:20 UTC91 viewsread 19 August 2026
Forwarded from @HZwt6688Photo

#上城 #位置丁桥海伦堡 #微信挖掘机 #无纹身 #暑假兼职 #木木 反馈7分像 🉑🈚无服务 🥓安排 @hzsr520 🥓私信限制联系 @suran520bot 🥓活动价1200💋 无套+300

Signed 蘇冉

18 Aug 2026, 05:06 UTC24 viewsread 18 August 2026
Forwarded from @HZyj6688Photo

#杭州 #微信伟哥 #澳大利亚 🥓安排 @hzsr520 🥓私信限制联系 @suran520bot 🥓水费1000张💋

Signed 蘇冉

Showing the 12 most recent of 44 posts we hold for @HZcha6688. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 7 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.

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 8 September 2026 — this entry's latest reading, not the date you are reading this.

“杭州蘇冉茶馆” (@HZcha6688), 8,057 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/HZcha6688.

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.