六点半以后有空的哦,想我的可以来看我啦

Channel
十一的日常
@li050love
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
788subscribers
+5 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003894789048 |
|---|---|
| Type | Channel |
| Username | @li050love |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/li050love |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 04:07 | 788 | +5 |
| 13 Aug 2026, 12:16 | 783 | first reading |
Engagement
20 posts held, back to 7 July 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
- 99.5%
- avg views ÷ 788 subscribers
- Avg views / post
- 784
- 8 posts measured
- Reaction rate
- 0.144%
- reactions ÷ views · ER floor
- Posts in window
- 8
- 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 3 of 8 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 August 2026 |
|---|---|
| Posts held | 20 (7 July 2026 – 13 August 2026) |
| Views total | 6,274 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 12:16 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
- 1m 57s
- Average length
- 29s
Measured directly from 4 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
14 reactions across 10 posts, in 2 distinct kinds. The most used accounts for 64.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 64.3% | |
| 🍌 | 5 | 35.7% |
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 10 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 14reactions 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 7 July 2026 to 13 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
#杭州肯德基 https://t.me/kdjqjt #好评 80-100 【出击时间】:8.10 【出击老师】:十一 【联系方式】: @lili050i 【出击留名】:蟹老板 【开课位置】:五堡 【修车水费】:工兵pp 【人照评分满分10】:9(人照9成) 【颜值评分满分20】:19(高颜值) 【身材评分满分10】:10(黄皮,无敌翘臀,无赘肉,隐约有马甲线) 【吊感评分满分20】:18(水多 紧) 【服务评分满分10】:8(嫩妹三件套) 【态度评分满分20】:20(主动询问/自觉服务) 【环境评分满分10】:8(小区) 【综合评分满分100】:92(以上相加) 情绪价值描述: 【过程描述】:有的打✅ 舌吻 ✅ 口活 ✅ 69舔穴 毒龙 【过程描述】:感谢肯德基,感谢🐔🐔,在我拔剑四顾心茫然的时候,突然发现肯德基上了十一的工兵,好久没cj了,果断抢下,直奔任务地点。 十一是去旅游刚回来,开课第一天,熟门熟路…
❤1
里面超多高颜值小姐姐 https://t.me/mzhn1314
#杭州肯德基 https://t.me/kdjqjt #好评 80-100 【出击时间】:8.11 【出击老师】:#十一 【联系方式】:@lili050i 【出击留名】:牛战士 【开课位置】:上城 【修车水费】:工兵p 【人照评分满分10】:10(人照一致,妆感不错) 【颜值评分满分20】:19(高颜值) 【身材评分满分10】:9(皮肤滑嫩,身材哇塞) 【吊感评分满分20】:19(户型蝴蝶,水多紧) 【服务评分满分10】:9(女友感拉满) 【态度评分满分20】:19(自觉服务) 【环境评分满分10】:10(高档小区) 【综合评分满分100】:95(以上相加) 情绪价值描述: 【过程描述】:有的打✅ 舌吻 ✅ 口活 ✅ 69舔穴 毒龙 【过程描述】:亲爱的十一老师强势回归,距离上次和十一做还是上次,忘不了那女友般的爱爱,也是顺利拿下工兵,和老师约好时间也是驱车直接前往,雨虽然大但阻止不了想十一老师的心,也是顺利…
开啦开啦有空的宝宝们
半岛嫩妹会报告模板: https://telegram.me/hangzhoubandao 【优势】颜值高,水多,屁股大,体质敏感,大蟒蛇,配合度高,情绪价值到位, 【不足】 【妹子花名】:#十一 【联系方式】:@lili050i 【妹子年龄】:21 【验证留名】:暴龙战士 【验证时间】:7月22日 【大概位置】:五堡 【修车水费】:900p 【高端服务】:有的打✅ ① 舌吻 ✅✅,管够,大蟒蛇 ② 69舔逼 ③ 情绪价值 ✅✅,到位了 ④ 毒龙 【人照相似】:人照相似9,颜值好看,气质偏御姐,穿搭休闲居家 【身高身材】:身高162腿长85,无纹身,皮肤光滑,嫩嫩的,白净 【凶器罩杯】:胸型大小A加,乳头颜色粉/大小适中,整体手感软软的,弹弹的 【湿度紧度】:比比户型小蝴蝶颜色粉,水多多紧度紧致,包裹感好,周围毛量适中 【环境细节】:交通/出入是方便,房间是整洁 【个人卫生】:不抽烟,有漱…
❤1
开啦开啦,有空可以预约的哦😁
半岛嫩妹会报告模板: https://telegram.me/hangzhoubandao 【优势】人照一致、活泼、反馈真实、态度好、敏感、大屁股 【不足】🈚️ 【妹子花名】:#十一 【联系方式】:@lili050i 【妹子年龄】:21 【验证留名】:火火 【验证时间】:7月19日 【大概位置】:上城 【修车水费】:竞拍500p 【高端服务】:有的打✅ ① 舌吻 ✅ ② 69舔逼 ③ 情绪价值 ✅ ④ 毒龙 【人照相似】:人照一致,颜值不错,气质好 【身高身材】:无纹身,无骨感,紧实,就像某些狼友说的可以当健身主播 【凶器罩杯】:A+,正常手感 【湿度紧度】:比比户型小🎀颜色褐粉,周围毛量适中,紧度适中,很湿 【环境细节】:交通方便,房间整洁 【个人卫生】:不抽烟,有漱口水/牙刷/浴巾,无陪浴但事前事后有清洗 【时间管理】:开课准时,排课宽松,课时做完 【服务点评】:服务到位,无少做,过程…
❤3
啦啦啦😝😝
❤1🍌1
有空宝子们,忙碌一周了,来找十一小护士解解乏吖🫣🫣
不听话 小心给你打针💉哦
🍌1
看着我的眼睛告诉我 你现在心里只有我😈
🍌1
Showing the 12 most recent of 20 posts we hold for @li050love. 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,267,834 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“十一的日常” (@li050love), 788 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/li050love.
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.