Telegram RegisterThe public register of Telegram
Telegram profile photo for 黄岩区

Channel

黄岩区

@huang1yan12

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

132subscribers

+49 since we began measuring on 15 September 2026

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

Register entry

Telegram ID-1003981869707
TypeChannel
Username@huang1yan12
CreatedBetween 1 April 2026 and 10 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 September 2026
Last confirmed live2 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/huang1yan12

Topic

Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 67% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

83132107.515 September 2026 — 83 subscribers15 September 2026 — 83 subscribers2 October 2026 — 132 subscribers15 September 20262 October 2026
3 measurements spanning 17 days, net +49. 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 76–139 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 04:17132+49
15 Sept 2026, 15:2283no change
15 Sept 2026, 14:4783first reading

Engagement

14 posts held, back to 10 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
121.6%
avg views ÷ 132 subscribers
Avg views / post
161
7 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
9
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 September 2026
Posts held14 (10 May 2026 – 11 September 2026)
Views total1,124
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Sept 2026, 15:22 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
7s
Average length
7s

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

11 Sept 2026, 14:02 UTCviews —

黄岩区 pinned «🎉台州黄岩颜值服务天花板🎉 女仆 印象SPA • 停车方便、用心服务 原价699折扣499 🈲本店🈚口🈚进入,找进入式的请绕路!»

11 Sept 2026, 14:02 UTC109 viewsread 15 September 2026
Photo

888号:欣欣 资料:02年 身高171 体重49KG B+ 项目:4t全果 商K下海,绝美大长腿、深邃的眼眸、清纯动人、第一眼是心动的感觉、皮肤紧致、A4小蛮腰,搂在怀里的感觉特别有感觉 新人下海,哥哥们下手轻点

11 Sept 2026, 14:02 UTC110 viewsread 15 September 2026
Photo

99号:KK 王炸、王牌首选 资料:02年 169cm 🐻C 情绪价值高、互动性强、一双大长腿冲击感特别强烈、妩媚烧气、身材高挑、大哥带着特别好玩、情绪到位解锁特殊风格 水王 首选闭眼冲

11 Sept 2026, 14:01 UTC100 viewsread 15 September 2026

🎉台州黄岩颜值服务天花板🎉 女仆 印象SPA • 停车方便、用心服务 原价699折扣499 🈲本店🈚口🈚进入,找进入式的请绕路!

7 Sept 2026, 13:26 UTC214 viewsread 15 September 2026
Photo

工号 333 年龄: 28 身高:165 无敌大西瓜 🐻 D+

5 Sept 2026, 15:44 UTC203 viewsread 15 September 2026
Photo

工号777 年龄 :23 身高:165 手法专业 🐻B+

5 Sept 2026, 15:44 UTC196 viewsread 15 September 2026
Photo

工号666 年龄:27 身高:171 御姐配大灯 🐻 C+

5 Sept 2026, 15:43 UTCviews —

黄岩区 pinned «(新玩法) 黄岩知韵SPA 无口 无大象 免开尊口 4t+水磨浴 原价899 代扣价 #599p 服务时长:50分钟»

5 Sept 2026, 15:43 UTC192 viewsread 15 September 2026

(新玩法) 黄岩知韵SPA 无口 无大象 免开尊口 4t+水磨浴 原价899 代扣价 #599p 服务时长:50分钟

Showing the 12 most recent of 14 posts we hold for @huang1yan12. 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.

Mentions

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

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

“黄岩区” (@huang1yan12), 132 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/huang1yan12.

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.