Channel
@yaoyao20258866
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,413subscribers
+603 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002929850600 |
|---|---|
| Type | Channel |
| Username | @yaoyao20258866 |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/yaoyao20258866 |
Other / unclassifiable — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 05:19 | 1,413 | +535 |
| 10 Sept 2026, 12:19 | 878 | +21 |
| 31 Aug 2026, 21:06 | 857 | +19 |
| 25 Aug 2026, 04:16 | 838 | +25 |
| 17 Aug 2026, 20:35 | 813 | +3 |
| 17 Aug 2026, 14:45 | 810 | first reading |
20 posts held, back to 5 June 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 13 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
39 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 84.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 33 | 84.6% | |
| 🍌 | 4 | 10.3% | |
| 😁 | 1 | 2.56% | |
| 🤮 | 1 | 2.56% |
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 15 of the 20 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 39 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 5 June 2026 to 13 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.
半岛嫩妹会报告模板： https://t.me/hangzhoubandao 【优势】气质绝佳，身材高挑，衣着品味很好 【不足】无 【妹子花名】：#玖璇 【联系方式】：@yaoyao202588 【妹子年龄】：26左右 【验证留名】：法师弗兰克@frank_1213 【验证时间】:8月10日 【大概位置】：东站附近 【修车水费】：800p 【高端服务】：有的打✅ ① 舌吻 ✅ ② 69舔逼 ✅ ③ 情绪价值 ✅ ④ 毒龙 ✅有，没做 【人照相似】：9分，真人更有气质，穿着打扮气质很好，衣品佳 【身高身材】：身高170，长腿细腰，脚脖处有纹身 【凶器罩杯】：胸型B+，乳头褐色，手感较软。 【湿度紧度】：人红白虎，脱毛彻底，水量适中，户型馒头。 【环境细节】：小区进出方便，车可以直接停进地下车库。房间环境干净整洁，法式装修。 【个人卫生】：老师抽烟，但嘴里没什么烟味，漱口水，牙刷都有 【时…
Signed 上城区 玖璇💗
半岛嫩妹会报告模板： https://t.me/hangzhoubandao 【优势】 【不足】 【妹子花名】：#玖璇 【联系方式】：@yaoyao202588 【妹子年龄】：26 【验证留名】：Humbert 【验证时间】：8月11日 【大概位置】：新塘 【修车水费】：800p 【高端服务】：有的打✅ ① 舌吻 ✅ ② 69舔逼 ✅ ③ 情绪价值 ✅ ④ 毒龙 【人照相似】： 【人照】：9 【颜值】：9 【身材】：10 【服务】：10 【态度】：10 【环境】：10（品味十足） 【综合】：9.5 【身高身材】：身材高挑大长腿，皮肤手感嫩滑。 【凶器罩杯】：胸部大概B,乳头粉色小小的，整体手感很好。 【湿度紧度】：紧致，馒头户型，人工白虎 【环境细节】：高档小区，教室很好找，无门禁。 【个人卫生】：上课中间不抽烟，有漱口水/牙刷/浴巾，事前事后有清洗。 【时间管理】：开课准时，排课宽松，…
Signed 上城区 玖璇💗
杭州一哥课堂 http://t.me/yigechat 🍀精英车评🌺,爽吃了 | yyds 【时间】： 2026-08-11 【老师】： 玖璇 【I D 】: @yaoyao202588 【留名】： Mark42 【人照】： 9 【颜值】： 9 【身材】： 9 【服务】： 10 【态度】： 10 【环境】： 10 【综合】： 9.5 【报告正文】 #课室环境 小区房，可直达车库，一室一厅，房间布置很雅致，课堂有落地镜 ----------------- #人之初印象 大长腿，邻家御姐范，170，估计不到100 皮肤滑溜，肩膀有小纹身，我说樱桃，老师说是车厘子，待狼友赏鉴 ----------------- #服务环节 浴室陪浴，水中箫 舌吻偏被动，但索取也积极配合，吻到窒息 口活很润，一直吃，管饱 反向服务：人工白虎，目前遇到最好吃的海鲜，水润禁止 ---------------- #嗯嗯体验 反馈度：做饭反馈真实 插…
Signed 上城区 玖璇💗
🈳🉑🈷️
❤2
Signed 上城区 玖璇💗
开课🚀
❤3🤮1
Signed 上城区 玖璇💗
本人已回杭州.这两天少量开课 约课要提前哦宝宝们
❤3
Signed 上城区 玖璇💗
这个月最后两天开课😘😘月课的宝宝们抓紧哦
Signed 上城区 玖璇💗
😘
❤2🍌1
Signed 上城区 玖璇💗
😘
❤5🍌1
Signed 上城区 玖璇💗
开课
❤2🍌1
Signed 上城区 玖璇💗
抽空做个检查也是有必要的
❤1
Signed 上城区 玖璇💗
明日开课，🉑🈷️
🍌1
Signed 上城区 玖璇💗
Showing the 12 most recent of 20 posts we hold for @yaoyao20258866. 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.
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.
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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“玖璇的频道” (@yaoyao20258866), 1,413 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/yaoyao20258866.
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.