Telegram RegisterThe public register of Telegram
Telegram profile photo for 青瑶4T的频道

Channel

青瑶4T的频道

@qingyaooo

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

1,536subscribers

+66 since we began measuring on 5 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003990947276
TypeChannel
Username@qingyaooo
CreatedBetween 1 April 2026 and 16 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 September 2026
Last confirmed live16 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/qingyaooo

Growth

1,4701,5361,5035 September 2026 — 1,470 subscribers5 September 2026 — 1,470 subscribers8 September 2026 — 1,483 subscribers12 September 2026 — 1,504 subscribers16 September 2026 — 1,536 subscribers5 September 202616 September 2026
5 measurements spanning 10 days, net +66. 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 1,460–1,546 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 03:551,536+32
12 Sept 2026, 13:371,504+21
8 Sept 2026, 16:001,483+13
5 Sept 2026, 22:221,470no change
5 Sept 2026, 21:471,470first reading

Engagement

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

ERR · 30 days
61.9%
avg views ÷ 1,536 subscribers
Avg views / post
952
10 posts measured
Reaction rate
0.119%
reactions ÷ views · ER floor
Posts in window
10
of 15 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 6 of 10 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 5 September 2026
Posts held15 (16 August 20265 September 2026)
Views total9,515
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Sept 2026, 22: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.

Reaction mix

10 reactions across 6 posts, in 1 kind.

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

Measured over the 15 most recent posts we hold, published 16 August 2026 to 5 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

5 Sept 2026, 07:30 UTC298 viewsread 5 September 2026

看群里小雅回来了,立即预约。去的稍微有点早,点的头钟,她也刚吃完饭,还没化妆。但是实际看下来的话,是非常可以的了, 有一点我觉得特别好的,这次我洗完澡之后,她乖乖的趴在床上等着我。做背部按摩的时候,她是真真正正的在做的,说实话有点手法,有力道的按,也会帮你松松骨,按的很舒服,这个是加分项。接着你就会感受到她的两个巨大的山峰在你的背上、大腿、小腿上轻轻蹭滑,37度的皮肤体温在空调房里显得格外的温暖。接着就是期待已久的阴推项目,闭眼享受。一边大胸也狠狠的压制着我,最后也是缴枪投降。园满结束! 总的来说配合度非常高话痨情绪价值也给的足服务内容是很丰富多彩的 建议兄弟们亲自体验,可返食

4 Sept 2026, 14:51 UTC463 views3 reactionsread 5 September 2026

【技师照片】:自愿拍摄不强求 【店名服务】:青瑶4T 【妹子花名】:小雅 【验证时间】:2026-9-4 【所在位置】:龙首原 【身高身材】:身高164差不多吧,体重看着有个100左右 属于紧实饱满那种类型 【颜值皮肤】:皮肤不错 很滑嫩的 颜值还可以过程中有些表情很迷人 。 【优点推荐点】:妹妹服务态度没问题,整个过程中也是非常的配合,不机车不催课。 【服务流程】:正常ab面 挑逗q耳后吹起我很喜欢 很会制造氛围感,会在胸滑的时候弱弱的划过你的嘴边,樱桃小嘴也会似有若无的往你嘴巴附近走,让你有种想亲上去的冲动,后续也是配合的不错,我比较慢出,也是体验了很多姿势,最后狠狠出货 【一句话点评】:服务配合都还可以,很有耐心 挺不错的。 【推荐人群】:(适合人群)喜欢氛围感 🐻控 【是否独家车评】:是

3

4 Sept 2026, 14:49 UTC451 views1 reactionsread 5 September 2026

一直想来体验一下YT,之前没听说过,过来选的菲菲,妹妹和照片比较像,感觉相对无风尘气,身材匀称,正常肤色,皮肤光滑,全过程很配合。 性格挺好的,全程不会让话掉地上,推荐,喜欢良家感的狼友出击,挺适合新手的(我本人)

1

4 Sept 2026, 03:53 UTC561 viewsread 5 September 2026
Photo

今天恢复正常营业啦 📣 小雅 菲菲老师也回归啦 想预约的私信哦🎉

3 Sept 2026, 09:52 UTC747 viewsread 5 September 2026

在啦营业中 上午老师体检去了,这会可以约课啦💌

30 Aug 2026, 08:53 UTC≈1,380 views2 reactionsread 5 September 2026

【技师照片】:自愿拍摄不强求 【店名服务】:青瑶4T 【妹子花名】:小七 【尊姓大名】:波波 【验证时间】: 8.29 【所在位置】:龙首原 【身高身材】:微胖 【颜值皮肤】:尚可 【瑕疵缺点】: 【优点推荐点】:乖 【服务流程】:客服指引上楼,冲澡后开始,先按正面,后按背面,最后开始y推,下面水多。总体还不错,小七好评 【一句话点评】:凶大推荐

2

28 Aug 2026, 03:03 UTC≈1,610 views2 reactionsread 5 September 2026

小七好评,胸大尺度大,会聊天,会帮忙擦背,没问题冲就完了

2

27 Aug 2026, 05:39 UTC≈1,660 views1 reactionsread 5 September 2026
Photo

小七 小雅 菲菲 📍龙首原 💌 全果4T 给哥哥们准备了很多情趣衣服哦👙

1

24 Aug 2026, 09:49 UTC≈2,000 views0 reactionsread 5 September 2026

昨天晚上在群里看到这家的项目是不熟悉的领域,私信问了客服具体的项目流程蠢蠢欲动恨不能立刻cj,但是第二天才能到西安,提前预约了头课,付了一张定金,客服说可以当天约确定时间当天不需要定,我怕没有头课了,就提前约了。 进到包间后先洗了个澡,出来就看到了小雅,那一刻居然有点紧张,好漂亮好温柔的妹妹。比较听指挥,态度也OK。问有没有制服,她出去重新拿了一些让我挑,我选了黑色的蕾丝款,谁懂,好性感!!!(小雅屁屁摸起来很有感觉。 还可以拍视频 这里我就不放图了,小雅真的很不错,满意的一次cj。 总结:体验不错,瑕不掩瑜

21 Aug 2026, 05:01 UTC≈2,390 viewsread 5 September 2026
Photo

菲菲有空位哦(菲菲身材真的不错,不愧经常健身 今日在岗三位,小七 小雅 菲菲 📍龙首原 💌 全果4T 给哥哥们准备了很多情趣衣服哦👙

20 Aug 2026, 08:53 UTC≈2,290 viewsread 5 September 2026

总是在电报当中看到,刚好有时间去体验了一番。 遥控上楼,不用怕找不到位置,接待也很热情, 我选择了菲菲,老师看上去原要比照片上看到的漂亮,在洗完澡后就开始进行了服务,菲菲老师的语气非常的柔软,因为我是第一次进行这些,有些害羞,但是老师并不会冷场,很照顾我的感受。 老师的身材也很棒,很白,并且皮肤也很好。绝对是一次满意的体验,下次还会再来的

Showing the 12 most recent of 15 posts we hold for @qingyaooo. 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 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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“青瑶4T的频道” (@qingyaooo), 1,536 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/qingyaooo.

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.