明天开

Channel
心妍咖啡厅
@xinyanmvp
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
33subscribers
+3 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004499250195 |
|---|---|
| Type | Channel |
| Username | @xinyanmvp |
| Description | 美丽大方 |
| Created | Between 1 June 2026 and 21 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| On Telegram | t.me/xinyanmvp |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 01:01 | 33 | no change |
| 10 Aug 2026, 20:47 | 33 | +3 |
| 10 Aug 2026, 13:45 | 30 | first reading |
Engagement
16 posts held, back to 21 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
- 373.1%
- avg views ÷ 33 subscribers
- Avg views / post
- 123
- 15 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- 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.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 16 (21 July 2026 – 10 August 2026) |
| Views total | 1,847 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 01:01 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
- Photos
- 9
- Videos
- 7
- Links
- 4
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 54s
- Average length
- 11s
Measured directly from 5 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
📊 0条车评,综合评分 好评 0% |人照 |服务 中评 0% |颜值 |态度 差评 0% |身材 |环境 艺名:心妍 地区:徐汇区 资料:-1 165 44 C 拍摄费用:11p 22pp 电报:@xinyanqqww 频道:https://t.me/xinyanmvp 通过此链接评价: https://t.me/shxcxw_bot?start=commentTeacher-TE178636056290 查看详细资料: https://t.me/shxcxw_bot?start=teacherContact-TE178636056290 🔰 Powerd by 泡芙: 闲聊群 上课群 真实作业 会员群(提交作业获取进群链接)
‼️‼️展览会福利群: 免费拿5折6折7折优惠 和抽奖 白嫖 现金红包 本群专属手势认证高质量老师 上海艺术展览会福利群: https://t.me/+nFnE0wANtSRkMjEx 点击进去备用群 上海艺术展览会总榜单:https://t.me/+2i_egsiBxNFlNmJh 上海艺术展览会人气推荐榜 https://t.me/+vOj1VuT48NE3MDc1 上海艺术展览会中转平台 https://t.me/+-sIwH2NalFw2MzEy 展览会老师广告群 @shanghaiyishu 个人推荐频道88🧧 📡 上榜管理:@yishuja_bot 📡 管理秘书:@Yishujia798_bot
上海奶茶妹高质量福利群: 主打嫩妹福利,抽奖竞拍半价6折。 现金红包🧧 上榜管理: @Naichacbot 上海奶茶妹交流群 https://t.me/+iSwJ-vAcG902N2E1 上海奶茶妹备用群 https://t.me/+38a0Y7pTMccyZjUx 上海奶茶妹高质量榜单 https://t.me/+PHc3J4BHv4pmMzg1 上海奶茶妹老师广告群 https://t.me/+VZrekuT90f5mN2Zl
还有🈳位置
开课了头课可以约
Video, posted without a caption
心妍咖啡厅 pinned «💘 名字,心妍 👠 身高:165 🌸 体重:93斤 👙 胸围: c 🌼 年龄:20 位置 黄浦徐汇交接处 高颜值 嫩妹💖 甜美纯新人 🌺小巧可爱 初恋女友感觉🍒 课表内容:陪浴 水中萧 指划 胸推 69 舔咪咪 无🍑口 激情啪 啪 姿势全方位 任由哥哥操控 课费:1100p(45分钟) 2100pp(80分钟) 联系 @xinyanqqww 双向 @xinyanqw_bot 🈲桩机 变态 拔套 吃药 低素质»
还有🈳
Photo, posted without a caption
开课了头课可以约
下班了
Showing the 12 most recent of 16 posts we hold for @xinyanmvp. 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 — 940,092 of 1,480,688entries 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 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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“心妍咖啡厅” (@xinyanmvp), 33 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/xinyanmvp.
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.