Telegram RegisterThe public register of Telegram
Telegram profile photo for 思瑶个人日常频繁

Channel

思瑶个人日常频繁

@siyao170

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

67subscribers

+3 since we began measuring on 17 August 2026

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

Register entry

Telegram ID-1004426967494
TypeChannel
Username@siyao170
CreatedBetween 1 June 2026 and 15 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 August 2026
Last confirmed live18 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/siyao170

Growth

646765.517 Aug 2026, 19:00 — 64 subscribers17 Aug 2026, 19:15 — 64 subscribers18 Aug 2026, 04:11 — 67 subscribers17 Aug 2026, 19:0018 Aug 2026, 04:11
3 measurements taken within a single day, net +3. 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 64–67 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 04:1167+3
17 Aug 2026, 19:1564no change
17 Aug 2026, 19:0064first reading

Engagement

20 posts held, back to 15 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
326.2%
avg views ÷ 67 subscribers
Avg views / post
219
20 posts measured
Reaction rate
0.209%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 20 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 17 August 2026
Posts held20 (15 August 202617 August 2026)
Views total4,371
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Aug 2026, 19:15 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
55s
Average length
18s

Measured directly from 3 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.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 2 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 1reactions 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 15 August 2026 to 17 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

16 Aug 2026, 14:24 UTC254 views1 reactionsread 17 August 2026

杭州日报报告 https://t.me/hz_news9 【评分标准】:9 【妹子花名】:#思瑶 【联系方式】:@siyao172 【妹子年龄】:20 【验证留名】:Turn 【验证时间】:8月14日 【大概位置】:拱墅区 【修车水费】:工兵 【服务内容】:有的打✅ ① 陪浴 ✅ ② 舌吻 ✅ ③ 69舔逼 ✅没要 ④ 情绪价值 ✅ ⑤ 毒龙 【人照相似】:人照8.5 【身材皮肤】:170黄白皮 【凶器罩杯】:B,很软 【户型湿紧】:水多,又紧 【课室环境】:小区楼 【个人卫生】:一次性用品齐全 【时间管理】:满意 【服务总结】:满意,都有 【过程描述】:在榜上一眼就看见长腿,符合审美。预约见到本人,和照片差不多。而且是我最爱的淡妆上课,底子非常好。身材很苗条,胸在B左右,手感挺好,软噗噗。到她口技还是不错的,而且不说停她是真不停啊……拍拍屁股让她呈上美食,原本不多的毛量她

1

16 Aug 2026, 12:23 UTC243 viewsread 17 August 2026

杭州日报报告 https://t.me/hz_news9 【评分标准】:9 【妹子花名】:思瑶 【联系方式】:@siyao172 【妹子年龄】:20+ 【验证留名】:巴斯光年 【验证时间】:8月16日 【大概位置】:拱墅 【修车水费】:工兵p 【服务内容】:有的打✅✅ ① 陪浴 ✅ ② 舌吻 ✅ ③ 69舔逼(不喜欢没问) ④ 情绪价值 ✅ ⑤ 毒龙 【人照相似】:9分 【身材皮肤】:身高170,皮肤光滑,黄皮 【凶器罩杯】:B➕奶头淡粉色 手感不错 【户型湿紧】:水超多 很紧做起来可以感觉到里面的形状 【课室环境】:小区房 环境还不错 【个人卫生】:有一次性浴巾 无漱口水 【时间管理】:宽松无摧课 【服务总结】:长的好看,服务仔细,无可挑剔 【过程描述】: 进门发现老师身材高挑,颜值很高。 本人与照片没有什么区别,手上皮肤小麦色但是脱掉衣服之后发现身上会更白一点,乳晕

16 Aug 2026, 10:48 UTC225 views0 reactionsread 17 August 2026

#杭州肯德基 https://t.me/kdjqjt #好评 80-100 【出击时间】:8月16日 【出击老师】:思瑶 【联系方式】:@siyao172 【出击留名】:美式要加冰 【开课位置】:拱墅 【修车水费】:工兵 P 【人照评分满分10】:(人照相似度/妆容)8,真人比照片好看 【颜值评分满分20】:(耐看/高颜值/一般)18,耐看,颜值在 8P 属于高颜值 【身材评分满分10】:(皮肤/身材/罩杯)18,小麦色,身材苗条,B 【吊感评分满分20】:(户型/紧度/水量/包裹感)18 【服务评分满分10】:(流程化/女友感/三件套)7 【态度评分满分20】:(主动询问/自觉服务)18 【环境评分满分10】:(日租房/公寓/高档小区)7 日租房,浴室小了点 【综合评分满分100】:(以上相加)84 情绪价值描述:话较少,偏内向 【过程描述】:有的打✅ 舌吻 ✅ 口活 ✅ 69舔穴 毒龙 【过程描述】: 周

Showing the 12 most recent of 20 posts we hold for @siyao170. 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,265,889 of 1,548,671entries 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 18 August 2026 — this entry's latest reading, not the date you are reading this.

“思瑶个人日常频繁” (@siyao170), 67 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/siyao170.

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.