Telegram RegisterThe public register of Telegram
Telegram profile photo for 小梨的朋友圈🍐

Channel

小梨的朋友圈🍐

@qi3719

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

265subscribers

+88 since we began measuring on 25 August 2026

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

Register entry

Telegram ID-1003880079988
TypeChannel
Username@qi3719
Created6 July 2026measured — dated from the channel’s first post
First recorded25 August 2026
Last confirmed live9 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/qi3719

Growth

17726522125 August 2026 — 177 subscribers25 August 2026 — 177 subscribers25 August 2026 — 185 subscribers1 September 2026 — 244 subscribers9 September 2026 — 265 subscribers25 August 20269 September 2026
5 measurements spanning 15 days, net +88. 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 164–278 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 21:19265+21
1 Sept 2026, 03:49244+59
25 Aug 2026, 21:09185+8
25 Aug 2026, 11:45177no change
25 Aug 2026, 11:30177first reading

Engagement

15 posts held, back to 6 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
70.2%
avg views ÷ 265 subscribers
Avg views / post
186
1 post measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
1
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 August 2026
Posts held15 (6 July 202625 August 2026)
Views total186
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Aug 2026, 11:45 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
47s
Average length
16s

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

15 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 86.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1386.7%
🔥213.3%

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 8 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 15 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 6 July 2026 to 25 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

4 Aug 2026, 23:39 UTC≈1,100 viewsread 25 August 2026

哥哥们 今天我回中山考科目一了 到时候在回来😘

2 Aug 2026, 09:00 UTC≈1,290 views5 reactionsread 25 August 2026
Video

Video, posted without a caption

5

30 Jul 2026, 05:18 UTC≈1,190 views0 reactionsread 25 August 2026
Forwarded from @CCJJYLSF888Photo

【妹子花名】:小梨 【联系方式】:@qi0617719 【验证留名】:糊涂老头 【验证时间】:7.29凌晨 【是否中介】:没看 【颜值皮肤】: 黄皮肤 【年龄凶器】:A 【身高身材】:很瘦小一个小嫩妹 【服务内容】:🐍 69xcz 【总体感受】:闲的睡不着就找了小梨,到了之后看见很瘦很瘦,小巧,到了房间交了水费开始宽衣解带去洗澡,我是刚洗完又简单的冲了一下,冲的时候小牙签就翘起来了,冲完后擦拭干进去房间开始调情。此处省略.....................接下来你们也知道,女上位传教式速度20码到50码,妹子说慢一点不急然后我就减速,时慢时快,水越来越多都流到屁股上了听到这个以后又是一个加速在妹子的浪叫中出水,接下来就是一起冲个澡穿好衣服结束,嫩妹八十斤左右纹身比较多,看个人眼缘,喜欢嫩妹骨感的可以尝试哦,很配合不催钟。 报告频道:@CCJJYLSF888

29 Jul 2026, 15:17 UTC≈1,050 viewsread 25 August 2026
Forwarded from @CCJJYLSF888Photo

【妹子花名】:小梨 【联系方式】:@qi0617719 【验证留名】:少女杀手 【验证时间】:7.25 【是否中介】:否 看过设备 【颜值皮肤】: 黄皮肤 符文女战士 【年龄凶器】:A+ 18岁卜卜脆 【身高身材】:1.60左右 【服务内容】:课表都有 【总体感受】:新上的老师 领下任务 马不停蹄出发 到目的地 上楼 老师开门 躲在门后面 可能比较害羞 交上水费 老师帮忙洗澡 擦干净躺床上 抚摸着小弟弟 然后一口含住,口了好一会 实在受不了 叫老师戴帽子,直进老师的秘密基地,好紧 果然18岁卜卜脆,然后换后入,抓着老师的腰部出力,冲冲冲,不秒 快射了 换姿势,抬起老师的脚,猛猛进进出出,最后射出 舒服 洗澡聊了一会天 看了一下老师的设备 完美离开 报告频道:@CCJJYLSF888

26 Jul 2026, 18:26 UTC≈1,290 views3 reactionsread 25 August 2026
Forwarded from @CCJJYLSF888Photo

【妹子花名】:小梨 【联系方式】:@qi0617719 【验证留名】:孤独的狗 【验证时间】:7.26 【是否中介】:否 【颜值皮肤】: 真人比照片好看 【年龄凶器】:18,我喜欢的胸 【身高身材】:160这样 【服务内容】:写上的都有 【总体感受】:约好时间之后老师吃饭化好妆美美的来了,等到的过程饥渴难耐,到了之后我赶紧去开门给老师,看到她我的心怦怦跳,太喜欢了,比照片好看多了,点了一杯咖啡给老师喝,天气这么热,必须空调开最大,我洗过澡了,让老师去洗澡,脱下衣服的时候我的二弟不争气的敬礼了,这时候二弟你必须给我坚持住,老师洗完澡之后就给我口,很舒服,然后女上位,疯狂进出,全程老师服务我,我心疼她,还出汗了,换了很多姿势,我的眼睛一直盯着老师的胸,我太爱了,终于坚持不住全部交代给老师了。然后就闲聊一会,我还抽了老师一支烟,就不舍的送别老师了。我们下次相约会很快的,你们要温柔对待老师,我迫不及待的等待下次了 报

3

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

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 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.

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

“小梨的朋友圈🍐” (@qi3719), 265 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/qi3719.

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.