【嫩妹报告】https://telegram.me/GZNMHEJI 【老师艺名】芳芳 【联系方式】 【所在位置】黄埔 【验证留名】匿名 【验证时间】9.18 【修车费用】600 【颜值身材】瘦底,白虎 【服务内容】正常三件套 【服务态度】还可以 【优点缺点】唯一优点,一个字嫩,天然白虎 【推荐程度】五星 【体验细节】唯一想做的就是草老师的b,只有一点点毛,跟没有一样,直接洗澡就是纯做了,边做边看下面,建议老师卫生弄好一点,喜欢嫩b的,可以来,就是才长出一点点毛,跟没有一样的天然白虎,而且也不黑,粉的 ♥️温馨提示: 以上仅代表个人体验,报告仅供参考! 👎🏿府上专员严查假报告!写手代谢出门右转! 报告提交:@Chenyaoyao1_bot

Channel
亲亲宝贝
@fang5208
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
177subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004484229123 |
|---|---|
| Type | Channel |
| Username | @fang5208 |
| Created | Between 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 1 |
| On Telegram | t.me/fang5208 |
Growth
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 06:22 | 177 | first reading |
Engagement
18 posts held, back to 11 September 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
- 267.8%
- avg views ÷ 177 subscribers
- Avg views / post
- 474
- 17 posts measured
- Reaction rate
- 0.253%
- reactions ÷ views · ER floor
- Posts in window
- 18
- of 18 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 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 September 2026 |
|---|---|
| Posts held | 18 (11 September 2026 – 18 September 2026) |
| Views total | 8,059 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Sept 2026, 06: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
- Photos
- 6
- Videos
- 1
- Links
- 8
Lifetime counters from Telegram’s own channel header, read 19 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 12s
- Average length
- 12s
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.
Reaction mix
7 reactions across 5 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 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 5 of the 18 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 11 September 2026 to 18 September 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
开课啦
下课了
【嫩妹报告】https://telegram.me/GZNMHEJI 【老师艺名】芳芳 【联系方式】 【所在位置】黄埔 【验证留名】画 【验证时间】9.17 【修车费用】600 【颜值身材】瘦底,白虎 【服务内容】正常三件套 【服务态度】很好,跟女朋友一样 【优点缺点】一个字嫩,水又多,户型超好看白嫩嫩的一点都不黑,就只有几根毛,天然白虎 【推荐程度】五星 【体验细节】进门看到芳芳小小只的,好可爱,虽然有一点纹身(本人不是很喜欢纹身)但有一说一有纹身跟性格是两码事,跟芳芳老师相处就像是女朋友一样,老师也很健谈不会冷场。最难得的是那种气质不是那种老🐔可以比拟的,完全小女友的感觉。具体的小黄文不太会写,老师会的不多,但很有耐心,不过分的要求都会做。总而言之就是又嫩又听话,前脚刚出门就开始期待二反了。 ♥️温馨提示: 以上仅代表个人体验,报告仅供参考! 👎🏿府上专员严查假报告!写手代谢出门右转! 报告提交:@Chenyaoyao1_
【嫩妹报告】https://telegram.me/GZNMHEJI 【老师艺名】芳芳(黄埔) 【联系方式】@fang52088 【所在位置】黄埔 【验证留名】匿名 【验证时间】9月15 【修车费用】6P 【颜值身材】小巧玲珑 【服务内容】洗吹做,蛇 【服务态度】微笑,态度好 【优点缺点】三点粉嫩,皮肤Q弹 【推荐程度】9 【体验细节】 一起洗,妹子的奶子坚挺,皮肤紧致,忍不住先亲了一口。洗完在床上一边蛇一边上下起手。希望水友们温柔对待老师,好好珍惜 ♥️温馨提示: 以上仅代表个人体验,报告仅供参考! 👎🏿府上专员严查假报告!写手代谢出门右转! 报告提交:@Chenyaoyao1_bot
❤1
今天睡过头了,开课啦
今天先下课啦,宝贝明天再约
下课啦,明天正常开课
【嫩妹报告】https://telegram.me/GZNMHEJI 【老师艺名】芳芳(黄埔) 【联系方式】@fang52088 【所在位置】黄埔 【验证留名】匿名 【验证时间】9月13 【修车费用】6P 【颜值身材】小巧玲珑 【服务内容】洗吹做,蛇 【服务态度】微笑,态度好 【优点缺点】三点粉嫩,皮肤Q弹 【推荐程度】10 【体验细节】 一起洗,妹子的奶子坚挺,皮肤紧致,忍不住先亲了一口。洗完在床上一边蛇一边上下起手。从后面入特别爽,一边插一边摸B。满意的一次体验 ♥️温馨提示: 以上仅代表个人体验,报告仅供参考! 👎🏿府上专员严查假报告!写手代谢出门右转! 报告提交:@Chenyaoyao1_bot
❤2
今天下课啦,宝贝明天正常开课
我在黄埔
❤2
【嫩妹报告】https://t.me/GZNMHEJI 【老师艺名】芳芳 【联系方式】@fang52088 【所在位置】黄埔 【验证留名】万 【验证时间】9.11 【修车费用】6 【颜值身材】颜值不错,黄皮,小萌妹 【服务内容】洗吹做, 【服务态度】很听话 【优点缺点】小白虎,很紧 【推荐程度】满分推荐 【体验细节】有一次性的,还可以,下面妹妹非常的粉,毛才刚刚长出,草起来很养眼 ♥️温馨提示: 以上仅代表个人体验,报告仅供参考! 👎🏿府上专员严查假报告!写手代谢出门右转! 报告提交:@Chenyaoyao1_bot
Showing the 12 most recent of 18 posts we hold for @fang5208. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“亲亲宝贝” (@fang5208), 177 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/fang5208.
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.