Telegram RegisterThe public register of Telegram

Channel

余杭

@Yu1hang1

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

529subscribers

+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-1002709440794
TypeChannel
Username@Yu1hang1
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/Yu1hang1

Growth

528529528.58 Aug 2026, 14:16 — 528 subscribers8 Aug 2026, 18:32 — 529 subscribers8 Aug 2026, 14:168 Aug 2026, 18:32
2 measurements taken within a single day, 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 528–529 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 18:32529+1
8 Aug 2026, 14:16528first reading

Engagement

6 posts held, back to 5 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
17.3%
avg views ÷ 529 subscribers
Avg views / post
91.5
6 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
6
of 6 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 2 of 6 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 6 August 2026
Posts held6 (5 August 20266 August 2026)
Views total549
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 14: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
4s
Average length
4s

Measured directly from 1 video 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

6 Aug 2026, 07:19 UTC86 views0 reactionsread 8 August 2026
Photo

小婷年龄04年 熊🐻B+ 身高164cm 体重45kg 🉑 开发度 👏🦶🐻🐬 🎶五种出水方式 广州小美女 身材真的是勾魂 舌吻海鲜都行 真实描述:身材一级棒 尺度绝对到位 比例超级好 特色:骚 骚 骚

5 Aug 2026, 05:09 UTC111 viewsread 8 August 2026
Photo

金牌:五宝(真毒龙🐉)🥰🥰🥰 年龄:02年 体重:100斤 身高:163 胸围:D 可共浴 5T选手 骚得很🥰舔🥚

5 Aug 2026, 05:09 UTC98 viewsread 8 August 2026
Photo

金牌:十宝🥰🥰🥰(全能王) 年龄:02年 体重:100斤 身高:161 胸围:C 可共浴 5T选手叫的唤 骚得很🥰舔🥚棒棒糖🍭 蛇🐍海鲜管饱

5 Aug 2026, 05:08 UTC89 viewsread 8 August 2026
Photo

王者:大宝(全能真毒龙🐉) 身高:165 体重:98斤 年龄:01 胸围:C+ 🉑👋 🉑🦶🉑 🐻🉑 🐬🉑🦞 (🉑腿夹 超级舒服那种)手法好花样多 青春的气息扑面而来 高颜值 女友版的陪伴 青春 活泼 开朗 舌吻海鲜 管饱照片保真!保真!保真!

5 Aug 2026, 05:08 UTC78 viewsread 8 August 2026
Photo

王牌:悠悠(会抓龙筋的气质女神) 基本资料: 2001年 163cm 50kg 🐻C 增值项目: 🉑🦞🉑舔🥚🉑😚 5T(🐻🐬👋🦶🎵) 果冻毒🐉 抓龙筋 海鲜管饱 各种角色扮演 配合度拉满 掼蛋

5 Aug 2026, 05:08 UTC87 views0 reactionsread 8 August 2026
Photo

头牌:六宝 基资料:(反差女大学生下海) 05年 168cm 50kg 🐻C+ 增值项目: 4T🐻🐬🖐🦶 果冻毒🐉 青纯女大学生,极致体验,皮肤白皙,视觉效果拉满,🐻软腿白性感反差极大,给你带来不一样的体验,手法专业技能专业,无差评!

Showing the 6 most recent of 6 posts we hold for @Yu1hang1. 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,349,734 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.

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

“余杭” (@Yu1hang1), 529 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Yu1hang1.

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.