Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州大表哥SPA一余杭区公寓半套天花板

Channel

杭州大表哥SPA一余杭区公寓半套天花板

@hzdabiaoge003

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

52subscribers

+1 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003898918189
TypeChannel
Username@hzdabiaoge003
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live17 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/hzdabiaoge003

Growth

515251.58 August 2026 — 51 subscribers10 August 2026 — 51 subscribers17 August 2026 — 52 subscribers8 August 202617 August 2026
3 measurements spanning 9 days, net +1. 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 51–52 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 11:2852+1
10 Aug 2026, 11:1551no change
8 Aug 2026, 12:3151first reading

Engagement

5 posts held, back to 29 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
51.2%
avg views ÷ 52 subscribers
Avg views / post
26.6
5 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
5
of 5 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 August 2026
Posts held5 (29 July 20261 August 2026)
Views total133
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 11:15 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
16s
Average length
8s

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

Recent posts

1 Aug 2026, 04:20 UTC26 viewsread 10 August 2026
Photo

🦋🦋33号悦悦 真实十八岁女大下海(周一上班) 下海皮肤光滑水嫩 、身材匀称,主打粉嫩、可调教 可爱的,一笑心都融化了, 三点粉!情商超高!会聊天!情绪价值超高!配合度高!(本人照片) 🉑5T(👋🦶🐻🐬🦅) 🉑🐍 🉑🦞 🉑🫙🥚🉑🍭 🉑果冻🐉 #漫椿

1 Aug 2026, 04:18 UTC25 viewsread 10 August 2026
Photo

🦋🦋55号 萍萍 瑜伽教练 身材曲线完美 身高162体重48KG胸B原瑜伽教练被逼无奈转行下海,服务主动热情,配合度高,欢迎各位哥哥来调教 🉑4T(👋🦶🐻🐬) 🉑🐍(看人) 🉑🦞 🉑果冻🐲 🉑助🌧️ #漫椿

1 Aug 2026, 03:52 UTC20 viewsread 10 August 2026
Photo

乖巧少女萍萍 刚下海嫩妹🌟🌟🌟 05年萌妹子,身高163体重94斤幼师下海,刚入这行望哥哥们能多多调教,服务配合,主动性高。笑容又充满亲和力,情商很高, 聊天不冷场, 第一次做 哥哥们下手轻点💐 服务内容🉑🐍(看人)🉑🦞(看人)🉑4T(🐻🐬👋🦶)🉑果冻🐲 #御雅

31 Jul 2026, 06:01 UTC25 viewsread 10 August 2026
Photo

丨号(呆萌甜妹) 资料:170 48kg 07年 胸🐻B 项目:5t(🐻👋🐬🦶🎵)🉑🐍💋换装,丝袜,(口臭不蛇)🉑🦞(管饱)69,随便摸小豆豆,不舔,加100可解锁情趣具,新人刚下海🌊外表名媛实则非常呆萌抽象 生着一双卡姿兰大眼却害羞到不敢看人 笑点很低 逗起来特别好玩 让人上瘾🤤)真实,人甜服务好,会心疼客户 #珍惜

29 Jul 2026, 05:29 UTC37 viewsread 10 August 2026
Photo

🉑甜🉑御姐冰冰 服务王者🌟🌟🌟 07年宝藏新人,一张初恋脸,一副顶配身材, B十,丰满到让人心痒,抱起来像抱着一团有温度的水。实力派服务,配合度拉满,让你舒服全凭本事,那种被摸透的感觉,比单纯的放松更让人上瘾。走的时候腿是软的,但心里是满满的 行走的荷尔蒙,拥有两幅面孔 服务内容 🉑🐍🉑🦞🉑5T(🐻🐬🦅👋🦶)🉑摸小豆豆🉑🫙🥚🉑🍭重点🉑真毒🐲 #御雅

Showing the 5 most recent of 5 posts we hold for @hzdabiaoge003. 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 — 1,372,137 of 1,550,220entries 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.

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

“杭州大表哥SPA一余杭区公寓半套天花板” (@hzdabiaoge003), 52 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/hzdabiaoge003.

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.