http://t.me/Aili04bot

Channel
南京江宁 爱莉 服务型
@aili04
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
21subscribers
+10 since we began measuring on 10 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004308715620 |
|---|---|
| Type | Channel |
| Username | @aili04 |
| Created | Between 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 November 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/aili04 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 20:40 | 21 | +10 |
| 10 Nov 2026, 16:22 | 11 | first reading |
Engagement
16 posts held, back to 2 November 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 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 161.6%
- avg views ÷ 21 subscribers
- Avg views / post
- 33.9
- 14 posts measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 16
- 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. It is computed over the 1 of 14 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 16 (2 November 2026 – 10 November 2026) |
| Views total | 475 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Nov 2026, 16: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.
What this channel posts
- Video runtime
- 1m 00s
- Average length
- 20s
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.
Recent posts
Telegram’s own ‘edited’ marker: 1 of 16 posts held from the last 30 days (6.25%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
😛 名称:#爱莉 📍 地区:#南京 #江宁 💰 价格:#10P #14PP 😒 认证:#视频认证 ✈️ 联系:@Rabin2001 💟 频道:@aili04 🤖 双向: 🏷 标签:#69式 #角色扮演 #69式
https://t.me/nanjingpd/7425
✌️❤️ @mamxx1104
📜🖌️ 【老师艺名】 #爱莉 点击查看 【联系方式】@njnj168 【所在位置】江宁 【验证留名】 【验证时间】 【修车费用】1400 【颜值身材】美人胚子、漂亮、端正 【服务态度】热情、配合 【优点缺点】还不错 【推荐程荐】8 【体验细节】第一次约菲总家的,选的爱莉,人不错,下面挺紧的,就是第二次没出来很难受,总体感觉还不错的,可以推荐 ♥️温馨提示: 以上仅代表个人体验,报告仅供参考! 报告提交:
🙈🙈🙈
【验证留名】: 【验证日期】:5.25 【妹妹花名】:小雨伞亲妹 #爱莉 点击查看 【妹妹类型】:软妹 【人照几成】:8 【目测年纪】:26上下 【身高身材】:160 苗条 【优点缺点】:颜值不错 皮肤尚可 态度好 配合 主动 健谈 服务不错 个儿不高 🐻不大 腿对比姐姐略粗一点 【过程报告】:今天约小雨伞,开门的不是姐姐本人,甚至以为约错了人,后来了解一下,是雨伞亲妹妹,雨伞本人回老家了。妹妹对比姐姐双眼皮割得更自然一些,一度以为是原生双眼皮,颜值和姐姐不相上下吧,不过🐻也不大,腿略微粗一点点。然后询问了一下有没有情趣,老师有女仆和护士两种,选了护士套装,加上丝袜和高跟,立马来劲了。洗完澡开始正式上课,老师口得比较猛,差点给我弄出来,然后69了好一会儿,小穴无异味很紧致。之后传教士开始互动,老师会夹,本来想换个姿势,由于被夹得爽直接出水了,之后还被夹了好一会儿才拔出,体验感非常好,但是不如姐姐那样会说骚话。走之前和老师聊天很长…
Channel name was changed to «南京江宁 爱莉 服务型»
Channel name was changed to «南京江宁 个人兼职 爱莉»
希望压得我喘不过气的是你,而不是生活哦😚
【验证留名】:匿名 【评价时间】:2026-11-02 【服务评分】:10 【人照评分】:10 【描述过程】:教室比较好找,停车方便,妹妹耐心指路,进门给完修车费,一起洗完澡后,换上了性感的黑丝,没想到妹妹的口活特别好,非常非常棒,让我欲罢不能,蛋蛋都给添了,很有感觉,接着又是亲咪咪,听着她那淫叫声不断着勾引我。随后后入,随着我抽插的越来越快,越来越强烈的刺激感直接出水了,事后还帮我洗了,走之前,最后给了一个拥抱,满意的离开了。 【老师名字】:爱莉
哥哥来找我玩阿
Showing the 12 most recent of 16 posts we hold for @aili04. 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 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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“南京江宁 爱莉 服务型” (@aili04), 21 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/aili04.
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.