Telegram RegisterThe public register of Telegram

Channel

普陀07瑶瑶

@putuo07yao

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

231subscribers

+36 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003907214506
TypeChannel
Username@putuo07yao
CreatedBetween 1 April 2026 and 19 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/putuo07yao

Growth

1952312139 Aug 2026, 12:00 — 195 subscribers10 Aug 2026, 01:01 — 231 subscribers9 Aug 2026, 12:0010 Aug 2026, 01:01
2 measurements taken within a single day, net +36. 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 190–236 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 01:01231+36
9 Aug 2026, 12:00195first reading

Engagement

13 posts held, back to 19 May 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
35.0%
avg views ÷ 231 subscribers
Avg views / post
80.9
9 posts measured
Reaction rate
1.10%
reactions ÷ views · ER floor
Posts in window
9
of 13 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 9 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 9 August 2026
Posts held13 (19 May 20269 August 2026)
Views total728
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 12:00 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
21s
Average length
11s

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.

Reaction mix

4 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4100.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 4 of the 13 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 19 May 2026 to 9 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

9 Aug 2026, 11:20 UTC22 viewsread 9 August 2026
Photo

🎉 萝莉岛(@shlldq) 萝莉岛 普陀 瑶瑶 老师半价券抽奖 🎁 奖品清单 • 1p半价劵 × 1 🛡️ 参与条件 • 加入 上海萝莉岛 • 加入 普陀07瑶瑶 • 加入 上海萝莉岛榜单 • 加入 上海萝莉岛报告 • 加入 上海萝莉岛甄选 • 必须设置用户名 🔮 祝福加持 • 祝福消耗:10积分 • 祝福上限:5次 • 祝福一次增加一个抽奖号,提高中奖率 • 幸运值祝福:支持 幸运值说明 ⌛ 抽选时刻 • 2026-08-12 15:18:00 📜 抽奖说明 1️⃣本次抽奖由 瑶瑶 老师赞助 @putuo07yaoy 2️⃣开奖后七天有效,请再七天内使用 3️⃣遇到问题请找唯一客服 @shlldbot ✨ 愿命运之剑指引你们前行,直至胜利之光照耀每一个人。

9 Aug 2026, 09:23 UTC41 viewsread 9 August 2026

CJ不迷路模版: https://t.me/qinchun_cj 评分标准:6分-差;7分-及格;8分-良好;9分-优秀;10分-极品 【艺名】:#瑶瑶 【联系】:@putuo07yaoy 【人照】:8分 【颜值】:8.5分(类型:嫩妹) 【身材】:9.5分(1米6左右,丰满微胖) 【服务】:8.5分(YYY、嫩妹三件套、69、调情) 【综合评分】:8.7分 【概述详情】:妹子19岁,良家少女,小白一个,经验较少。有点肉肉的,没有明显的赘肉,微胖刚刚好。嫩妹服务不多,嫩妹三件套。 大胸很软,摸着很舒服,她舔我胸时,大胸压在我肚子上,好舒服好软。摸摸妹妹咪咪,乳头会慢慢变硬很好玩。 温柔的慢慢的摸摸妹妹的阴蒂,妹妹会呻吟。传教士进入,趴在妹妹身上,压着大胸软软的,很不错。妹妹异常的紧,很少见,无奈我居然123,很快就射了。 优点:很嫩,很紧,胸大,微胖 【留名】:匿名

9 Aug 2026, 02:51 UTC86 views1 reactionsread 9 August 2026

🔰上海泡芙课后作业🔰 【时间】:2026-08-09 【老师】:@putuo07yaoy 【留名】:林总 【人照】:9 【颜值】:8.8 【身材】:9 【服务】:9 【态度】:10 【环境】:9 【综合】:9.13 【过程】:简洁一些吧! 1.微胖c罩杯,是个妹妹嫩妹子。 2.老师很紧一般两次我都出不了,但是今天出来了,主要是老师太紧了。 3.大家轻点凿别把老师凿坏了。 4.很温柔性格很好的妹妹,会反食的。

1

8 Aug 2026, 14:00 UTC95 views1 reactionsread 9 August 2026
Photo

📊 0条车评,综合评分 好评 0% |人照 |服务 中评 0% |颜值 |态度 差评 0% |身材 |环境 艺名:07瑶瑶 地区:普陀区 资料:19 165 55 D 拍摄费用:7p 14pp 电报:@putuo07yaoy 频道:https://t.me/putuo07yao 通过此链接评价: https://t.me/shxcxw_bot?start=commentTeacher-TE178619755417 查看详细资料: https://t.me/shxcxw_bot?start=teacherContact-TE178619755417 🔰 Powerd by 泡芙: 闲聊群 上课群 真实作业 会员群(提交作业获取进群链接)

1

7 Aug 2026, 13:58 UTC156 viewsread 9 August 2026
Forwarded from @suming00

奶茶妹报告模版:https://t.me/+VXhIbgbL0k9mYjc1 【茶妹艺名】:#普陀瑶瑶 【联系方式】:@putuo07yaoy 【所在位置】:#普陀 【上课茶费】: p 【验证时间】:5.19 【人照几成】:8.5 【服务态度】:9.5 【体验评价】:9 【服务过程】: 看见榜上07的瑶瑶妹妹,在群里又正好见到瞬移推荐,怎能不去尝试,可惜ls排的太满时间不凑巧,约了两天才约上。 1️⃣进门见到老师个字不高,纯素颜跟照片8.5分相似(主要照片有磨皮美白,老师本身皮肤偏黄),🈚️纹身,吉林人但是一点口音都没有,不问我是真没听出来。 2️⃣妹妹真实07的才19岁,可以看出特别嫩,很懵懂且听话,基本啥也不知道,你要什么都会照做,没有一点风尘气息,并且会主动脱衣服yyy(今天这房子浴室灯坏的,来了个摸黑yyy,新体验啊),但是动作很不熟练,连打沐浴露的动作都稍显生疏。 3️⃣妹妹衣服一脱就见两个大白🐰跳了出来,大d大灯还特

20 May 2026, 10:50 UTC≈1,110 views2 reactionsread 9 August 2026

上海艺术展览会报告模板: https://t.me/+nFnE0wANtSRkMjEx 【体验评分】:9.9 【人照几成】:9 【验证留名】:后空 【验证时间】:5.20 【妹子艺名】:#瑶瑶 【联系方式】:@putuo07yaoy 【所在位置】:普陀 【上课水费】:工兵pp 【身材描述】:大胸嫩妹 【凶器罩杯】:c+胸型好看挺拔 【服务类型】:嫩妹服务 【服务态度】:听话配合 【优点缺点】:值得推荐 【整体补充】:最近几次都是约的午饭时间,正巧附近都有麦当劳,打包一份和妹妹分享一下打开话题,简单吃两口后进入正题,解开衣服呼之欲出的一对巨乳,让我爱不释手,舌吻也很投入,带套开始,刚下海的就是紧,第一次直接被秒😂,洗漱完,和瑶瑶吃完剩下的麦当劳补充能量,回到床上把玩了一会大胸,开始第二次,cjs,侧入,后入…大战三百回合😂。总结:刚下海嫩妹,青涩但听话配合,做爱反馈真实,i人需要老爷引导,值得推荐。 【温馨提醒】:报告仅供参考,请

2

19 May 2026, 17:39 UTC988 views0 reactionsread 9 August 2026
Photo

这几天单子排的比较🈵,想来的哥哥要提前预约时间,避免约不到哦

19 May 2026, 12:24 UTC988 viewsread 9 August 2026

上海艺术展览会报告模板: https://t.me/+nFnE0wANtSRkMjEx 【体验评分】:9 【人照几成】:8.5 【验证留名】:Leo 【验证时间】:5.19 【妹子艺名】:#瑶瑶 【联系方式】:@putuo07yaoy 【所在位置】:#普陀 【上课水费】:P 【身材描述】:微胖 【凶器罩杯】:C+ 【服务类型】: 课表上的都有 【服务态度】:10 【优点缺点】:大白🐰、紧 / fw不熟练 【整体补充】:初见瑶瑶,给人邻家妹妹的感觉。本人虽然没有照片那么靓丽,但也还好,属于大众脸吧。寒暄过后就准备更衣、沐浴。一对大白🐰duang~的一下就跳出来了。洗白白上🛏️后赶紧先抚摸一下大白🐰,爽!接下来课表上的内容都可以有,只是ls还不够熟练,ly自己发挥吧。等时机成熟,带☔️后准备开战。ls的小穴是真的紧啊,从里到外的那种。期间曾尝试后入,结果发现无法锁定目标😂。于是换回cjs,开始向目标进攻。整个过程行云流水、一气呵

Showing the 12 most recent of 13 posts we hold for @putuo07yao. 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 — 901,158 of 1,189,255entries 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.

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

“普陀07瑶瑶” (@putuo07yao), 231 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/putuo07yao.

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.