Channel name was changed to «Lily🌸粉丝频道(开课中)»

Channel
Lily🌸粉丝频道(开课中)
@Lilysssll
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,867subscribers
+58 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002247590712 |
|---|---|
| Type | Channel |
| Username | @Lilysssll |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/Lilysssll |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 14:23 | 1,867 | +31 |
| 12 Aug 2026, 17:34 | 1,836 | +27 |
| 11 Aug 2026, 19:31 | 1,809 | first reading |
Engagement
16 posts held, back to 27 January 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 136.0%
- avg views ÷ 1,867 subscribers
- Avg views / post
- 2,540
- 2 posts measured
- Reaction rate
- 0.571%
- reactions ÷ views · ER floor
- Posts in window
- 3
- of 16 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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 16 (27 January 2026 – 7 August 2026) |
| Views total | 5,080 |
| Reactions total | 29 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 19:31 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
- 2s
- Average length
- 2s
Measured directly from 1 video 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
111 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 57.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 64 | 57.7% | |
| 🥰 | 30 | 27.0% | |
| 💯 | 5 | 4.50% | |
| 😘 | 4 | 3.60% | |
| 🤬 | 4 | 3.60% | |
| 🆒 | 3 | 2.70% | |
| 👍 | 1 | 0.901% |
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 12 of the 16 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 111reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 27 January 2026 to 7 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
Posted without readable text
🥰6❤3👍1💯1🆒1
最近遇到很多傻逼哥哥 请以后没有约过的哥哥提供跟老师约课的聊天记录或者定金两百口令红包 谢谢理解(我忍很久了)
❤11🤬4🆒2
Photo, posted without a caption
❤5😘4
Lily🌸粉丝频道(开课中) pinned a video
❤️
🥰9❤4💯4
Lily人照10分,所见即所得,天生好看。瓜子脸,小小一只,但是其实身高还行。 想约Lily好几个月了,中间有一搭没一搭的聊过天,但每次时间都不对,这次终于让我逮住Lily了,一见面就感觉很熟悉,像出差好久回家见到了心爱的女友。 Lily是小区房,黄埔一个地铁口的小区,交通便捷,安全性拉满。课室干净整洁,一看就是爱干净的小女生。清清爽爽没有风尘气。 见面很热情,主动递水,有一次性用品,还有漱口水,好评,感觉有🐍了,嘿嘿。 小黄文不写了,谈谈感受,一是情绪价值超高,洗完澡不是急切开始,而是先依偎在一起随便聊聊天,感觉熟悉了,开始接吻,水到渠成那种感觉。二是主动索吻小蟒🐍,很投入那种。三是过程中反馈很真实,有感觉了开始叫老公,要更多,满满的反差感。四是结束后不着急结束,继续抱抱聊天,满分💯。
❤4
认识lily老师有一年多了,已经记不清楚去过几次了,却一直没有给老师写过评价,现在抓紧补上。 对lily的总体评价就是:宝藏女孩&六边形老师。说一下我喜欢老师的点: 1,颜值,个人认为长的比较像she时期的hebe,秀气中透着机灵可爱,元气满满,喜欢这一款的兄弟应该不在少数。 2,全身上下纯天然,没有科技与狠活。曾经有人忽悠老师去整形,被老师拒绝了,这个要夸赞一下。 3,身材算是比较典型的山城妹子,腿细腰长比例好,局部不是丰满型但也凹凸有致。 4,不搞假照、美颜照欺骗感情。老师频道里的照片多是日常拍摄,一些艺术照也是写实风,并且真人比照片更好看,在电报榜单里也算是一股清流了。 5,不抽烟,没有纹身。本身老师也是偏文静的乖乖女样子,所以应该不会沾这些陋习。 6,老师由于皮肤有点敏感,日常基本素面朝天,黑长直发,最近好像连美甲也没有做。对于我这种讨厌浓妆系的人来说可真是太喜欢了,一来可以放心亲亲,不怕被化学物质“毒害”;二来不会在自…
❤11
女子清白不在罗裙之下 而在品行之间
❤5
lily老师是偶然看到的,加入收藏里也已经很久了,但却遗憾一直没有机会见面,这次看到老师更新了照片真的按耐不住,直接定下包时,但意外收获这么棒的体验。 按照老师的指示成功抵达,lily的安全意识很强,看到老师的第一眼真的被惊艳到了,老师穿着一身淡黄色的小裙子跑过来,纯真又带一丝甜美,就像是少年时的白月光,也像隔壁家暗恋许久的少女,带着一丝激动,和老师一起走进浴室,洗的很是认真,随即进入正题,带着一丝羞涩褪去了lily的外衣,lily身材很好,熊和她瘦弱的身躯不成比例,对于臀控的我来说,屁股堪称艺术品,lily的服务很好,口的也很认真,于是我也趁机上下其手,小妮子很敏感稍微一动,下面已经是汪洋一片,老师含情脉脉的望着,这谁能忍得住,马上切换战斗模式,先让小妮子自己在上面享受全自动小马达,随后改为传教士的姿势狠狠冲击,在老师的叫声中成功发射,成功解锁反差属性更是喜欢。中间休息的时候老师会和小猫一样躺在你怀里,和lily聊天你只会更喜…
❤5🥰2
@Lilyis003 妹子说她那里不是中高风险,她是二期是住宅。人照八分左右因为头课刚起基本素颜,但是十分耐看。情绪价值从进门开始就比较足,穿着衣服很瘦小腿很纤细,但是脱衣服有胸有屁股。黄皮。大蟒蛇,亲一下下面湿的很快,doi反馈很高很真实,后入更爽,特别会主动适应撞击角度。十分满意的出击 标签: @Lilyis003 Lily 1200p #黄浦 点击跳转原始报告【需先加群】 反馈狼友: m0neSy 时间:2026-04-08 16:31:15 报告ID:10085 当前进度:1/2
你准备哪一天和我见面~(明天开)
❤8🥰5
Showing the 12 most recent of 16 posts we hold for @Lilysssll. 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 — 667,638 of 1,549,704entries 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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“Lily🌸粉丝频道(开课中)” (@Lilysssll), 1,867 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/Lilysssll.
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.