Telegram RegisterThe public register of Telegram

Channel

小花园测评基地

@hhl307756

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

21subscribers

+0 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003739624093
TypeChannel
Username@hhl307756
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/hhl307756

Growth

2113 Aug 2026, 11:16 — 21 subscribers14 Aug 2026, 13:17 — 21 subscribers13 Aug 2026, 11:1614 Aug 2026, 13:17
2 measurements spanning 1 day. 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 20–22 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 13:1721no change
13 Aug 2026, 11:1621first reading

Engagement

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

ERR · 30 days
615.0%
avg views ÷ 21 subscribers
Avg views / post
129
13 posts measured
Reaction rate
0.617%
reactions ÷ views · ER floor
Posts in window
14
of 14 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 13 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 12 August 2026
Posts held14 (20 July 202612 August 2026)
Views total1,679
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 11:16 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
2m 01s
Average length
11s

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

1 reaction across 1 post, in 1 kind.

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

Measured over the 14 most recent posts we hold, published 20 July 2026 to 12 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

12 Aug 2026, 18:27 UTC8 viewsread 13 August 2026
Forwarded from @hhl25533Video

店铺:小花园 #雨雨 #客服hhy0825 看了小花园家群里发的雨雨 OOTD,犹豫了几天,今天终于还是决定出击一趟。提前约好时间,路上还有点小紧张,一方面是冲着她的颜值来的,另一方面也怕翻车。到了店里,客服简单聊了几句就让我进去等。雨雨进门的那一瞬间,包臀裙,身高大概在 165 左右,身材比例很好,腿线条也算修长,妆容不算浓,偏学生系,有点女大在读的那种气质,一眼看过去就觉得是嫩妹路线。进门先主动跟我打招呼,声音软软的,有点撒娇的感觉,不会那种隔着一道墙的生疏感。简单聊了几句日常,能感觉到她刚接触这行不久,不是那种老油子类型。问了才知道确实是在读女大,有点小腼腆,但不怯场,整体氛围就很舒服。聊了一会儿,雨雨就自然地靠了过来,随后干脆直接躺到我怀里。那一刻是真有点“小鸟依人”的感觉,整个人轻轻地倚在我身上,身上有淡淡的香味,不是浓烈香水,更像沐浴露混一点洗衣液的味道。她很会聊天,不会冷场,也不会刻意尬聊,情绪价值这块给得很到位。

12 Aug 2026, 15:49 UTC7 viewsread 13 August 2026
Forwarded from @onwow888Video

WOW指南:二星⭐️⭐️ 值得跨城出击 小花园•西湖| 客服 妹妹:小蓉 数据:163/84/B 类型:甜御 标签:高颜/混血/高情绪价值/敏感/素人 🔤背景回顾 之前就听其他哥们去了小蓉,反馈特别好。强烈推荐哇喔也去看看,OK,哥们说很好那就试试吧。在大厅的时候刚好见到推门而入的小蓉。 就那一刻,感觉她应该是现场最亮点的妹妹了。第一印象就是-人群中的明珠。 第一视角感受小蓉,颜值高!情绪价值夯! 🔤高颜值像古力娜扎 平时我也不太吃的来御姐,对比会比较少,但小蓉这类型的颜值确实好看。在大厅见到的,给我的感觉有点像古力娜扎的影子。我说是不是好多人也这么说过,她说是呀,你怎么知道,有好几个客人也这么说。我说你这么好看,我都不好意思盯着你看了。小蓉说你别害羞,我们对视,看谁先笑。哈哈,果然,败的是我。5秒就认输了。 🔤敏感度高情绪价值夯 和她聊了兴趣爱好,以及旅行的趣事,以及星座等等。 我觉得她真的会埋伏笔,好几次话题都被她

9 Aug 2026, 22:36 UTC39 viewsread 13 August 2026
Forwarded from @ylwzzVideo

店铺: #小花园 艺名: #粥粥 【进门印象】 早就听说粥粥的名头,今天可算让客服帮我约上了。推门进去,沙发上坐着个高挑妹子,净身高得有一米七左右,身材和气质确实打眼,一眼就能确认是本人。房间的床单被罩都换得干净整洁,整体环境看着挺踏实,第一印象相当不错。 【过程体验】 坐下聊天感觉很自然,不冷场也不显得过于套路,氛围拿捏得刚刚好。没一会儿妹子就顺势贴了过来,小手若即若离地撩着,气氛一下就上去了。亲吻互动的时候非常投入,舌头又软又香。 后面摸小白兔的时候皮肉确实滑嫩,不过想继续向下深入的时候被妹子温和拉住了,看来还是有点自己的小底线。接着亲胸的环节体验极佳,动作特别温柔细腻。后来一问才知道她之前在 in11 待过,难怪这素质和基本功确实扎实。 【总结】 整趟体验下来非常顺畅舒服,一点没踩雷,这趟跑得绝对值!

8 Aug 2026, 05:35 UTC65 viewsread 13 August 2026
Forwarded from @onwow888Video

WOW指南:优质推荐 👍 小花园•西湖| 客服 妹妹:雨雨 数据:06/165/B 🔤背景回顾 刚好在刷模卡,老板突然发来一个妹妹。说这个雨雨本人挺好看,值得一试。看了一下雨雨的视频,感觉还不错,随即出击。虽然有点路途,但感觉还是有期待值的。 🔤初次见面 在大厅见到雨雨的时候,感觉这个侧面就还不错的,没有仔细撇清,跟着就进了房间。雨雨主动就是拉我聊了起来。我说这个好像没有VIP,小雨居然直接说,哥哥要不我给你开一个会员。当时就惊呆了,妹妹这么大气吗.... 感觉雨雨性格还蛮好的,我说我i人咋办啊这,话不多的。她说没事,哥哥我来带你...怎么带? 骑着带啊,哈哈哈,你坐好了?! 🔤钟上流程 随后便轻松卸甲。还主动邀请来卸。哥哥,不对!哥,你有点笨笨的哈哈。这里这里...呼的一下就见到了大白兔....哥哥,你要不?.........哈。芜湖,埋着头。随后便是紧实,饱满,松软感。之后便跨坐了上来? 哥哥,你动,还是我动? 啥动

3 Aug 2026, 10:40 UTC162 views1 reactionsread 13 August 2026
Forwarded from @hhl25533Photo

粥粥 小蓉 来自优质客户的好评➕1❤️

1

2 Aug 2026, 16:51 UTC110 viewsread 13 August 2026
Forwarded from @onwow888Video

WOW指南:二星⭐️⭐️ 值得跨城出击 小花园•西湖| 客服 妹妹:小蓉 数据:163/84/B 类型:甜御 标签:高颜/混血/高情绪价值/敏感/素人 🔤背景回顾 听闻老板上新了一位混血妹妹,高颜面孔让试钟员一眼心动。老板说这个是纯素人刚入行,之前没做过的,再多看了两眼照片还是让人按捺不住好奇心,决定一试。 🔤笑容满面亲和力拉满 见到妹妹时她已在大厅等待,真人如照片一般非常精致甜美。吊带衫配上牛仔短裤与自身气质相搭,打招呼时笑容满面,看起来不像是一个有距离感的妹妹,亲和力瞬间拉满。和小蓉的破冰非常顺利,情商挺高,会切入话题与你互动,眼神交流时很有女友感。舌吻循序渐进,不太会喘气需要温柔引导。身材微瘦削但不骨感,B杯挺拔柔软,耳朵和胸非常敏感,反应强烈,甚至身体会有点发烫。会主动服务,为你舔上半身很久,虽然是素人但服务意识意外地到位。 🔤总结 她属于圈内少有的中俄混血高颜,五官立体深邃,辨识度很高! 御姐系里小蓉属顶颜,

28 Jul 2026, 11:37 UTC131 viewsread 13 August 2026
Forwarded from @onwow888Video

WOW指南:优质推荐 👍 小花园•西湖| 客服 妹妹:雨雨 数据:06/165/B 🔤背景回顾 刚好在刷模卡,老板突然发来一个妹妹。说这个雨雨本人挺好看,值得一试。看了一下雨雨的视频,感觉还不错,随即出击。虽然有点路途,但感觉还是有期待值的。 🔤初次见面 在大厅见到雨雨的时候,感觉这个侧面就还不错的,没有仔细撇清,跟着就进了房间。雨雨主动就是拉我聊了起来。我说这个好像没有VIP,小雨居然直接说,哥哥要不我给你开一个会员。当时就惊呆了,妹妹这么大气吗.... 感觉雨雨性格还蛮好的,我说我i人咋办啊这,话不多的。她说没事,哥哥我来带你...怎么带? 骑着带啊,哈哈哈,你坐好了?! 🔤钟上流程 随后便轻松卸甲。还主动邀请来卸。哥哥,不对!哥,你有点笨笨的哈哈。这里这里...呼的一下就见到了大白兔....哥哥,你要不?.........哈。芜湖,埋着头。随后便是紧实,饱满,松软感。之后便跨坐了上来? 哥哥,你动,还是我动? 啥动

Showing the 12 most recent of 14 posts we hold for @hhl307756. 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 — 444,373 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

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

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.

“小花园测评基地” (@hhl307756), 21 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/hhl307756.

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.