Telegram RegisterThe public register of Telegram
Telegram profile photo for 雅莉的朋友圈

Channel

雅莉的朋友圈

@yalipyq1

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

593subscribers

+156 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1004327784206
TypeChannel
Username@yalipyq1
CreatedBetween 1 June 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live10 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/yalipyq1

Growth

43759351515 August 2026 — 437 subscribers15 August 2026 — 437 subscribers16 August 2026 — 450 subscribers24 August 2026 — 465 subscribers31 August 2026 — 486 subscribers10 September 2026 — 593 subscribers15 August 202610 September 2026
6 measurements spanning 25 days, net +156. 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 414–616 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 05:16593+107
31 Aug 2026, 09:37486+21
24 Aug 2026, 22:24465+15
16 Aug 2026, 18:05450+13
15 Aug 2026, 19:00437no change
15 Aug 2026, 18:45437first reading

Engagement

20 posts held, back to 31 July 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
102.4%
avg views ÷ 593 subscribers
Avg views / post
607
2 posts measured
Reaction rate
0.161%
reactions ÷ views · ER floor
Posts in window
2
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 1 of 2 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 14 August 2026
Posts held20 (31 July 202614 August 2026)
Views total1,214
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 19: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
59s
Average length
7s

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

19 reactions across 11 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
19100.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 13 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 19 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 31 July 2026 to 14 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

14 Aug 2026, 03:14 UTC621 views1 reactionsread 15 August 2026

【工兵报告】 『推荐指数:⭐️⭐️⭐️ ⭐️』 【日期】:2026-08-03 【美女昵称】:雅莉 【验证人】:韦小宝 【地 区 】:鄞州 【联系方式】:@yali99999 【见面感觉】:9 【室内光线】:明亮 【属性标签】:服务性 【身材曲线】:苗条 【技术含量】:10 【价格 】:500/P(优惠券200) 【安 全 性】:公寓 【年龄】:31 【身高】:160 【体重】:105 【凶器,是否假奶】:C 真 【肤色,手感】:白皮 【B内温】:热 【BB户型】:蝴蝶 【BB味道】:无 【三点】:正常 【课表,特色】:服务性 【人照相似】:9 【服务过程】: 首先感谢凌晨兄弟的优惠券!今日份水群聊着聊着有人转送优惠券,那可以啊正好好久没出击了。 轻车熟路到达地地目,开门一见ls穿着黑色一套脚踩黑色高跟鞋,随即交钱脱衣洗澡,全程帮洗帮擦还有水中萧,床上铺了一次性浴巾趴在上面先是B面服务,还

1

10 Aug 2026, 14:28 UTC≈1,270 viewsread 15 August 2026
Video

台风没事扎着玩!一月自测的一天😂😂🈷️

8 Aug 2026, 09:24 UTC≈1,730 views1 reactionsread 15 August 2026
Photo

宝贝最近捅了鸽子窝!来个夜课宝宝安慰我😂😂😂

1

6 Aug 2026, 13:42 UTC≈2,060 views4 reactionsread 15 August 2026

(活跃群友,可信度高) 『推荐指数:⭐️⭐️⭐️⭐️』 【日期】:260806 【修车编号】:#NBTG1052 【美女昵称】:#雅莉 【验证人】:白灼开水 【地 区 】:高新区 【联系方式】:@yali99999 【见面感觉】:8 【室内光线】:明亮 【属性标签】:痴女系 【身材曲线】:身材标准,臀围较小 【技术含量】:8 【价格 】:500p 【安 全 性】:公寓 【年龄】:30左右 【身高】:156 【体重】:50kg 【凶器】:34B 【胸型】:水滴状 【肤色,手感】正常黄色,光滑 【B内温】:热 【BB户型】:蝴蝶 【BB味道】:无味 【三点】:虽然和粉搭不上,但也不是很黑。 【课表,特色】:会喷,热情,礼貌,亲近,骚话多 【人照相似,真人打几分】:7-8分 【服务过程】: 因为没有中到雅莉老师的抽奖,心一狠,牙一咬,头发花散,原价出击。到了地方,老师开门,进去之后,雅莉老师穿着一袭紫色薄纱情趣睡

4

5 Aug 2026, 07:09 UTC≈2,310 views3 reactionsread 15 August 2026
Photo

换新战袍啦!来个会撕丝袜的宝贝

3

5 Aug 2026, 05:07 UTCviews —

雅莉的朋友圈 pinned «雅莉老师 服务系会所老师 身高156体重100🐻36b年龄31 服务:69 🐍吻(口臭拒绝)胸推 无套口吹 吸皮刮痧 鸳鸯浴 水中潇 深🐒毒🐲(真毒龙)臀推 可情趣制服多套 丝袜 高跟鞋 pp 可口爆一次做一次 P服务中出水算一次 课费:5p-45分钟 9pp85分钟 夜课2000八小时 禁:无套 皮肤病 后花园 桩机 醉酒 嗑药 变态 双向回复:@Yaligggbot 约课:@yali99999»

5 Aug 2026, 05:07 UTC≈2,320 views1 reactionsread 15 August 2026

雅莉老师 服务系会所老师 身高156体重100🐻36b年龄31 服务:69 🐍吻(口臭拒绝)胸推 无套口吹 吸皮刮痧 鸳鸯浴 水中潇 深🐒毒🐲(真毒龙)臀推 可情趣制服多套 丝袜 高跟鞋 pp 可口爆一次做一次 P服务中出水算一次 课费:5p-45分钟 9pp85分钟 夜课2000八小时 禁:无套 皮肤病 后花园 桩机 醉酒 嗑药 变态 双向回复:@Yaligggbot 约课:@yali99999

1

4 Aug 2026, 13:59 UTC≈2,320 views1 reactionsread 15 August 2026
Video

来个夜客宝宝一醉方休呀!

1

Showing the 12 most recent of 20 posts we hold for @yalipyq1. 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 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.

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

“雅莉的朋友圈” (@yalipyq1), 593 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/yalipyq1.

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.