Telegram RegisterThe public register of Telegram
Telegram profile photo for 秦淮小艺打卡频道

Channel

秦淮小艺打卡频道

@xiaoyispa

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

28subscribers

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

Register entry

Telegram ID-1003784563102
TypeChannel
Username@xiaoyispa
First recorded17 November 2026
Last confirmed live17 November 2026
Measurements held1
On Telegramt.me/xiaoyispa

Growth

Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Nov 2026, 08:2228first reading

Engagement

9 posts held, back to 14 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
472.6%
avg views ÷ 28 subscribers
Avg views / post
132
6 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
9
of 9 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 6 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held9 (14 November 2026 – 17 November 2026)
Views total794
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 08: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

Photos
2
Links
1

Lifetime counters from Telegram’s own channel header, read 17 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 9 posts held from the last 30 days (11.1%) 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).

17 Nov 2026, 01:48 UTC53 viewsread 17 November 2026
Forwarded from @chepingqu

【妹妹花名】:小艺 @xysspa 【报告署名】:匿 【验证时间】:11.15 【验证地点】:夫子庙老小区 【服务类别】:95,98都有 【修车水费】:600p,500kb 【妹妹类型】:服务型少妇 【颜值身材】:长相不错,身材不错,大奶 {年龄}:29 {颜值}:8 {皮肤}:黄皮 {罩杯}:c纯天然 {身高}:165 {体重}:100 {赘肉}:腹部少许赘肉 {颜值综合打分}:8 {身材综合打分}:8.5 【服务质量】:会所级别 {服务内容}:会所级qt服务 {服务水平}:会所老师级 {服务态度}:态度好无机车行为 {服务综合打分}:9 【纹身疤痕】:无纹身和无明显疤痕 【是否吸烟】:无烟味 【课室卫生】:一次性用品齐全,室内、床褥整洁。 【周边环境】拉:老小区环境一般,出入自由 【综合打分】:8.2 【综合评述】:颜值身材不错服务也不错在5这个价格里非常能打,属于老a8 {优势}:奶大服务好,颜值尚可 {不足}:身…

17 Nov 2026, 01:48 UTC50 viewsread 17 November 2026
Forwarded from @chepingqu

【妹妹花名】:小艺 @xysspa 【报告署名】:匿名 【验证时间】:2026.11.16 【验证地点】:夫子庙 【服务类别】:95 【修车水费】:500p(工兵300) 【妹妹类型】:少妇 【颜值身材】:7.5 {年龄}:28 {颜值}:8 {皮肤}:黄皮 {罩杯}:C {身高}:162 {体重}:95 {赘肉}:肚子无赘肉,有小肚子 {颜值综合打分}:8 {身材综合打分}:7.5 【服务质量】:服务态度很好,很细致 {服务内容}:指划,过皮吸水,毒龙 {服务水平}:挺好 {服务态度}:细致耐心 {服务综合打分}:8 【纹身疤痕】: 无 【是否吸烟】:无 【课室卫生】:一次性床单 【周边环境】:老小区 【综合打分】:8 【综合评述】:服务系少妇 {优势}:毒龙,舔蛋技术很好 {不足}:老小区入口不好找 【过程概述】:老师课室在老小区,很绕,小区不同入口居然不通。好不容易找到了,打开门,感觉老师真人可能会更好看点。洗完澡…

17 Nov 2026, 01:48 UTC57 viewsread 17 November 2026
Forwarded from @chepingqu

【妹妹花名】:小艺 @xysspa 【报告署名】:匿 【验证时间】:2026.11.14 【验证地点】:夫子庙 【服务类别】:95 【修车水费】:500kb(工兵-200) 【妹妹类型】:服务型 【颜值身材】: {年龄}:27 28 {颜值}:照片8成像,实际要好看一点,但是妆也浓一点 {皮肤}:黄白皮 {罩杯}:C {身高}:165 {体重}:90,很瘦 {赘肉}:比较瘦,基本没有 {颜值综合打分}:7.8 {身材综合打分}:8.5 【服务质量】: {服务内容}:课表上基本都有,浴室小,无陪浴 {服务水平}:会所老师 {服务态度}:态度很好,有想法可以直接说,基本都会配合 {服务综合打分}:8.2 【纹身疤痕】:未见纹身和明显疤痕 【是否吸烟】:无烟味 【课室卫生】:一次性床单,浴巾 【周边环境】:老小区周边楼道环境一般,但是课室环境还比较干净,楼下有门禁,可以输密码进入,下水道稍微有点反味 【综合打分】:8.3 【…

17 Nov 2026, 01:48 UTC52 viewsread 17 November 2026
Forwarded from @chepingqu

【妹妹花名】:小艺 @xysspa 【报告署名】:匿名 【验证时间】:11月16日 【验证地点】:秦淮区(夫子庙地铁旁) 【服务类别】:95(中项)98(大项) 【修车水费】:700p、500kb(工兵500半价) 【妹妹类型】:服务型少妇 【颜值身材】: {年龄}: 25-30 {颜值}:8成像 {皮肤}:黄皮,皮肤很滑溜,没有纹身 {罩杯}:C➕,圆润有弹性 {身高}:163 {体重}:100不到,小骨架 {赘肉}:腹部有赘肉,趴着能看出来 {颜值综合打分}:8分 {身材综合打分}:8分 【服务质量】: {服务内容}:课表上的都有,要跟老师说一下,额外的需要商量 {服务水平}:会所老师级,之前一直在其它地方 {服务态度}:服务很细致耐心,一点也不敷衍 {服务综合打分}:9分 【纹身疤痕】:未注意纹身疤痕 【是否吸烟】:课室没有烟味 【课室卫生】:一次性用品齐全,室内、床褥很干净整齐 【周边环境】:夫子庙地铁口小区,出…

14 Nov 2026, 07:41 UTC401 views0 reactionsread 17 November 2026
Photo

😇哥哥好啊、我是 小艺 😇年龄:26身高163体重:96 🐻D 😇开课地址:秦淮夫子庙 😇身材苗条,皮肤白皙,乖巧懂事,温柔体贴,服务内容(助🛀、指滑、胸滑、鼻滑、猴子偷🍑、臀滑、口活、毒龙💋69 臀推、胸推、丝足、口💥配合度高、不矫情、)有特殊爱好者可以提前沟通,不过分的要求都可以满足哈。 🥰中项💰:500KB 一次,50 分钟 🩷中项💰:600KB一次➕手推一次60 分钟 😍中项💰:700KB两次 70分钟 大项98 :700 全套服务60分钟 请尽量提前备好现金 谢谢❌❌❌❌🈲酒🈲💊拒接㊙️ ㊙️电报号: @xysspa ㊙️双向机器人 @Xiaoyisao_bot ㊙️交流群:https://t.me/xiaoyisa ㊙️频道 https://t.me/xiaoyispa

Showing the 9 most recent of 9 posts we hold for @xiaoyispa. 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.

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

“秦淮小艺打卡频道” (@xiaoyispa), 28 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/xiaoyispa.

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.