现在空有位置滴滴滴

Channel
年年岁岁花相似
@hs58d
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
564subscribers
+1 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 | -1003937331162 |
|---|---|
| Type | Channel |
| Username | @hs58d |
| Created | Between 1 April 2026 and 19 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/hs58d |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 12:18 | 564 | +1 |
| 13 Aug 2026, 21:46 | 563 | no change |
| 13 Aug 2026, 21:35 | 563 | first reading |
Engagement
20 posts held, back to 19 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 192.4%
- avg views ÷ 564 subscribers
- Avg views / post
- 1,090
- 6 posts measured
- Reaction rate
- 0.033%
- reactions ÷ views · ER floor
- Posts in window
- 8
- of 20 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 5 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (19 May 2026 – 7 August 2026) |
| Views total | 6,511 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 21:46 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
20 reactions across 8 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 20 | 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 13 of the 20 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 20reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 19 May 2026 to 7 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
年年岁岁花相似 pinned a photo
Photo, posted without a caption
年年岁岁花相似 pinned Deleted message
两点一线 上线⁺¹ºº 可以提前约辣~~
❤2
杭州学生会:https://t.me/students_union 评分标准:6分﹣差 7分﹣及格 8分﹣良好 9分﹣优秀 10分﹣极品 【出击老师】:#岁岁 @suiusi1413 【出击留名】:lajase 【出击时间】:7月27日 【大概位置】:东站 【修车水费】:18包时 【高端服务】:有的打 ✅ 没有的打 ❎ ① 舌吻 ✅ ② 六九 ✅ ③ 毒龙 ❎ 【人照相似】:人照十分,可甜可御,致命诱惑 【身高身材】:165+,四六分身材,纹身正合适,性感的身材和恰到好处的身材相呼应 【胸器罩杯】:胸型B+,乳头粉粉的,皮肤光滑细腻紧致 【湿度紧度】:户型毛发,紧度湿度,做爱反馈 【课室环境】:小区,停车很方便,门禁很宽松 【个人卫生】:有抽烟,但无烟味,有陪浴,一次性物品很齐全 【时间管理】:排课合理,无催客赶客,情绪价值超满 【服务点评】:性价比的神,我将永远拥护,服务态度是嫩妹的顶中顶,个人给到夯 【推荐程…
杭州颜值嫩妹报告 https://t.me/hzyanzhi 【综合评价】:‼️下面只留一个 #好评 【妹子花名】:#岁岁 【联系方式】:@suiusi1413 【妹子年龄】:20左右 【验证留名】:Edison 【验证时间】:7月26日 【大概位置】:东站附近 【修车水费】:竞拍半价p 【高端服务】:有的打✅ ① 舌吻 ✅ ② 69舔逼 ✅ ③ 情绪价值 ✅ ④ 毒龙 【人照相似】:人照相似9分,颜值气质8.5分 【身材皮肤】:身高162左右,有纹身,不大,皮肤黄皮,手感嫩滑 【凶器罩杯】:胸型B到C,乳头颜色粉嫩,正常大小,手感不错,很柔软 【湿度紧度】:水量多,紧度很紧,周围毛量较少 【环境细节】:交通 停车方便,房间环境整洁 【个人卫生】:抽烟但课室无烟味,有漱口水 浴巾,事前事后有清洗 【时间管理】:开课准时,排课宽松,课时做完 【服务总结】:服务到位,无少做,过程无机车 【流程小…
>学生会小秘书: 杭州学生会:https://t.me/students_union 10分﹣极品 【出击老师】:#岁岁 @suisui1413 【出击留名】:Naruto 【出击时间】:7月25日 【大概位置】:上城 【修车水费】:工兵pp 【高端服务】:有的打 ✅ 没有的打 ❎ ① 舌吻 ✅ ② 六九 ✅ ③ 毒龙 ❎ 【人照相似】:人照9分,极品嫩妹 【身高身材】:165左右,很有料! 【胸器罩杯】:胸很大,配合细腰,后入有劲儿 【湿度紧度】:很紧很湿 【课室环境】:小区,很方便 【个人卫生】:抽烟但是没烟味,很注意卫生 【时间管理】:排课宽松,很周到 【服务点评】:700档幻神,值得多刷 【推荐程度】:没有缺点,冲啊! 【流程细节】: 岁岁是我心里独一份的女孩。门打开时,她笑着看我,眼睛弯成好看的弧度,像我们只是昨天才分开。简单寒暄了两句,声音里带着久别后的生涩和喜悦。衣服一件件落下,她的身体露出来,不夸张,…
Photo, posted without a caption
❤1
杭州颜值嫩妹报告 https://t.me/hzyanzhi 【综合评价】:‼️下面只留一个 #超级好评 【妹子花名】:岁岁 【联系方式】:@suiusi1413 【妹子年龄】:19 【验证留名】: 农村 @Jatsbyjay 【验证时间】:6月16日 【大概位置】:东站附近 【修车水费】:700p 【高端服务】:有的打✅ ① 舌吻 ✅ ② 69舔逼 应该有没要 ③ 情绪价值 ✅ ④ 毒龙 【人照相似】:人照相似8.5-9分,颜值气质 8.5-9 【身材皮肤】: 身高腿长162-164 纹身大小 胸前手臂有纹身 皮肤观感手感 黄白皮嫩妹中算光滑 【凶器罩杯】: 胸型大小 水滴奶 B样子 乳头颜色 粉嫩 手感良好 【湿度紧度】:户型颜色 粉 腹部一撮有修建痕迹 水多b紧有阻尼感 【环境细节】:交通方便,附近停车有一点困难 房间环境干净整洁 【个人卫生】:有抽烟但是无烟味 有漱口水浴巾,事前…
❤3
今天刚做检测
❤1
📢 来自报告机器人的报告: 杭州颜值嫩妹报告 https://t.me/hzyanzhi 【综合评价】:‼️下面只留一个 #好评 【妹子花名】:#岁岁 【联系方式】:@suiusi1413 【妹子年龄】:18左右 【验证留名】:@king88ss 【验证时间】:6月11日 【大概位置】:东站附近 【修车水费】:7p 【高端服务】:有的打✅ ① 舌吻 ✅ ② 69舔逼 ✅ ③ 情绪价值 ✅ ④ 毒龙 【人照相似】:9分 【身材皮肤】:身高162 ,皮肤光滑手感舒服,有点小纹身 【凶器罩杯】:B+ 奶,胸型非常挺,握感舒适, 【湿度紧度】:毛少水多 较紧嫩嫩的🦋 【环境细节】:交通 停车方便,房间整洁 【个人卫生】:无抽烟,有浴巾,有漱口水,事前事后有清洗 【时间管理】:开课准时,排课宽松,课时做完 【服务总结】:服务到位,无少做,过程无机车,情绪价值拉满 【流程小文】:今天还没下班,就心心念…
❤1
Showing the 12 most recent of 20 posts we hold for @hs58d. 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 — 891,435 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.
Mentions
Named by 1 registered channel — 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.
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.
“年年岁岁花相似” (@hs58d), 564 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/hs58d.
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.