Telegram RegisterThe public register of Telegram

Channel

沪杭目录

@hhlsml

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

11,632subscribers

+103 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003979814035
TypeChannel
Username@hhlsml
Description沪杭精选榜单 https://t.me/+buhUm5mj89M5Njkx 沪杭目录 https://t.me/hhlsml 沪杭游学团 https://t.me/+NylpAQPF6CFiZjhh 沪杭精选超优群 https://t.me/+rr9NPUJTxBYyYWM1 沪杭精选报告 https://t.me/hhjxreport 上榜 投稿 合作 https://t.me/HH_TomBot
CreatedBetween 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/hhlsml

Growth

11,52911,63211,580.57 August 2026 — 11,529 subscribers7 August 2026 — 11,531 subscribers8 August 2026 — 11,543 subscribers9 August 2026 — 11,556 subscribers10 August 2026 — 11,593 subscribers11 August 2026 — 11,624 subscribers12 August 2026 — 11,628 subscribers14 August 2026 — 11,632 subscribers7 August 202614 August 2026
8 measurements spanning 7 days, net +103. 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 11,514–11,647 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 08:0411,632+4
12 Aug 2026, 23:1511,628+4
11 Aug 2026, 20:4211,624+31
10 Aug 2026, 19:1211,593+37
9 Aug 2026, 16:2211,556+13
8 Aug 2026, 14:0411,543+12
7 Aug 2026, 13:1611,531+2
7 Aug 2026, 07:1611,529first reading

Engagement

11 posts held, back to 4 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 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
10.6%
avg views ÷ 11,632 subscribers
Avg views / post
1,230
11 posts measured
Reaction rate
0.083%
reactions ÷ views · ER floor
Posts in window
11
of 11 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 3 of 11 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 13 August 2026
Posts held11 (4 August 202613 August 2026)
Views total13,513
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 02:39 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

Photos
318
Videos
81
Links
82

Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
1m 26s
Average length
11s

Measured directly from 8 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

3 reactions across 2 posts, in 1 kind.

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

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

13 Aug 2026, 09:09 UTC≈1,160 views2 reactionsread 15 August 2026
Photo

👤 名字:#胡图图 #上海 📇 资料:身高163 胸C+ 📌 标签: #12P #22PP #嫩妹 #颜值 #甜妹 #美乳 #胸控 #白虎 #三点粉 #足控 ✈️ 联系:@tutuhappy1 👆 ✈️ 双向:@tutuha_bot 👆 半价600优惠券 数量1 游学团内竞拍 ✨ 游学团 👆 ✨ 优质群 👆 (审核制)

2

11 Aug 2026, 10:53 UTC353 viewsread 15 August 2026
Forwarded from @hhjxbdPhoto

出现假冒猫王盗号,说联系不上的,要求验证码的,老师们不要上当!

10 Aug 2026, 13:03 UTC≈1,290 viewsread 15 August 2026
Photo

👤 名字:#诗诗 #上海 #杭州 📇 资料:身高163 胸B 📌 标签: #14P #26PP #甜妹 #女友系 #颜值 ✈️ 联系:@shi112233abc 👆 ✈️ 双向:@shishi996bot 👆 ✨ 报告1 ✨ 游学团 👆 ✨ 优质群 👆 (审核制)

10 Aug 2026, 05:44 UTC≈1,240 viewsread 15 August 2026
Photo

👤 名字:#林一 #上海 #杭州 📇 资料:身高175 胸D 📌 标签: #25P #46PP #御姐 #正妻气质 #身材 #臀控 #2度白皮 #舌吻到窒息 #澳门红牌 #服务 ✈️ 联系:@futianlinqiao1 👆 ✈️ 双向:@linyidebot 👆 ✨ 游学团 👆 ✨ 优质群 👆 (审核制)

10 Aug 2026, 03:20 UTC≈2,120 viewsread 15 August 2026
Photo

👤 名字:#小茉莉 #上海 📇 资料:身高165 胸B 📌 标签: #13P #22PP #嫩妹 #颜值 #清纯 #甜妹 #白丝 ✈️ 联系:@xiaomoli5 👆 ✈️ 双向:@xxmlyydbot 👆 ✨ 报告1 ✨ 游学团 👆 ✨ 优质群 👆 (审核制)

9 Aug 2026, 13:33 UTC≈1,200 views0 reactionsread 13 August 2026
Photo

👤 名字:#小洁酱 #上海 📇 资料:身高165 胸E 📌 标签: #25P #48PP #嫩妹 #颜值 #女友感 #玩具 #野战 #大胸 ✈️ 联系:@miss_jiebao 👆 ✈️ 双向:@xiaojiejiangovo_bot 👆 500优惠券 数量1 游学团内竞拍 300优惠券 数量3 积分兑换 ✨ 游学团 👆 ✨ 优质群 👆 (审核制)

9 Aug 2026, 03:57 UTC≈1,150 viewsread 10 August 2026
Photo

👤 名字:#奈奈子 #上海 📇 资料:身高160 胸C 📌 标签: #30P #55PP #颜值 #三点粉 #双飞 #莞式服务 #SM ✈️ 联系:@nainai69 👆 ✈️ 双向:@nai56bot 👆 ✨ 游学团 👆 ✨ 优质群 👆 (审核制)

6 Aug 2026, 08:36 UTC≈1,260 viewsread 9 August 2026
Photo

👤 名字:#暖暖 #上海 📇 资料:身高175 胸C 📌 标签: #8P #15PP #御姐 #身材 #丝袜 #高妹 ✈️ 联系:@Jiajia123654 👆 ✈️ 双向:@HH_TomBot 👆 半价400优惠券 数量1 200优惠券 数量2 积分兑换 ✨ 游学团 👆 ✨ 优质群 👆 (审核制)

6 Aug 2026, 03:56 UTC≈1,270 viewsread 9 August 2026
Photo

👤 名字:#景涵 #上海 📇 资料:身高172 胸C 📌 标签: #40P #80PP #大蜜 #网红 #颜值 #气质 #韩系财阀风 #身材 #胸控 #臀控 ✈️ 联系:@xiangxi379 👆 ✈️ 双向:https://t.me/+6IP91C8Wp8IwYzI1 👆 800优惠券 数量1 游学团内竞拍 500优惠券 数量4 积分兑换 ✨ 报告1 ✨ 游学团 👆 ✨ 优质群 👆 (审核制)

5 Aug 2026, 07:42 UTC≈1,220 viewsread 9 August 2026
Photo

👤 名字:#咔咔 #上海 📇 资料:身高168 胸D 📌 标签: #10P #18PP #嫩妹 #胸控 #臀控 #身材 ✈️ 联系:@qwykwww 👆 ✈️ 双向:@qwykwwwbot 👆 半价500优惠 数量1 游学团内竞拍 ✨ 游学团 👆 ✨ 优质群 👆 (审核制)

4 Aug 2026, 03:52 UTC≈1,250 views1 reactionsread 9 August 2026
Photo

👤 名字:#桐绾绾 #上海 #杭州 📇 资料:身高168 胸C 📌 标签: #25P #50PP #气质 #颜值 #身材 #胸控 #女友系 #1度白皮 #馒头 #蜜桃臀 #玉足 ✈️ 联系:@wtongzi 👆 ✈️ 双向:@yourwanwanbot_bot 👆 ✨ 报告1 ✨ 游学团 👆 ✨ 优质群 👆 (审核制)

1

Showing the 11 most recent of 11 posts we hold for @hhlsml. 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.

Citation-graph rank

Citation-graph rank — 155,817 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

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

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.

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

“沪杭目录” (@hhlsml), 11,632 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/hhlsml.

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.