🈶️🈳️

Channel
普陀 彩禾
@caihe22557
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
76subscribers
+64 since we began measuring on 11 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003654222101 |
|---|---|
| Type | Channel |
| Username | @caihe22557 |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 3 |
| On Telegram | t.me/caihe22557 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 15:22 | 76 | no change |
| 12 Sept 2026, 14:37 | 76 | +64 |
| 11 Sept 2026, 12:47 | 12 | first reading |
Engagement
11 posts held, back to 11 September 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
- 306.2%
- avg views ÷ 76 subscribers
- Avg views / post
- 233
- 10 posts measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 11
- of 11 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 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 September 2026 |
|---|---|
| Posts held | 11 (11 September 2026 – 12 September 2026) |
| Views total | 2,327 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Sept 2026, 15: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
- 14
- Videos
- 5
- Links
- 4
Lifetime counters from Telegram’s own channel header, read 12 September 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
- 48s
- Average length
- 10s
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
【所在位置】:#普陀 【老师艺名】:#彩禾 【老师榜单】:https://t.me/shkccj/22075 【验证留名】:老表 【验证时间】:2026.9.12 【课程费用】:1800p 【颜值身材】:顶级欧美身材 【服务内容】:有写 【服务态度】:非常给力10分 【优点缺点】:全优 【推荐程度】:10分 【体验细节】: 刷榜单看到新上的彩禾老师,很符合我的口味,提前约好课程一进门,一双大眼睛、高鼻梁的美人胚子就直勾勾地盯着我,搞得我都有点害羞了。 人还没坐下呢,进门就牵着我坐在沙发上,开始唠嗑,把我这个社恐整得不知所措。既然妹子这么主动,那就话不多说,直接拉我进浴室开始她的表演。 先是骚气十足地用大屁股在我小弟弟上使劲磨蹭加上沐浴露泡泡的加持太舒服了,接着一回头来了一发水中箫,那刺激感,下面立马硬到不行。 洗完赶紧擦干上床,简直把我当金主爸爸伺候,浑身上下、前前后后都给舔了个遍。 有一说一,她那灵动的舌头加上快慢有致的节奏…
昨天无聊在榜单上刷到的老师,老师说刚来上海,今天来试试,路上还在想不是本人就转头就走,到了一开门还好是本人,人照差距不大,老师身材确实是丰满型的,胸也好大,我就喜欢有肉感的,老师很热情,服务好,她的深喉很厉害👍可以整根吞到底,有很多情趣内衣可以挑,还会按摩,做完了在按摩真的很放松,老师也很会聊天,兄弟们可以放心冲,服务是真的好,也不催
开课啦 哥哥们滴滴我❤️❤️
艺名:#彩禾 #己验证 位置:#普陀 #欧美身材 身高:167cm 体重57kg 胸E 课费:1800p 3000pp 📱联系:@caihe257 🤖双向:@caihe22557_bot ♥️联系老师说明来自:上海出击大队 ⛔️文明出击 ————————————————— 📣广播台 🔗报告榜 💥管理员
(总入口) https://t.me/shmdgmd (主榜单和评价) https://t.me/moduguangmingding2 (镜像榜单) https://t.me/moduguangmingding1
https://t.me/laoahihaixuan/28422
普陀 彩禾 pinned a photo
可以来找姐姐吗 第一次来上海🌹
Video, posted without a caption
💐💐💐彩禾 普陀开课 个人开课 本人真人真照 四川人 性格好 热情主动 聊天不冷场 真胸E奶 屁股大 身材微胖丰满型 喜瘦勿扰 💐💐💐 身高:167 胸围:36E 体重:57kg 年龄:25 💐💐💐 服务:陪浴 🐍吻 69 调情 胸推 无套吹箫 吸蛋蛋 深喉 口爆 按摩 丝袜制服诱惑 口活好 💐💐💐 课费:一课50分钟 1800/p 两课90分钟 3000/pp 包时:2小时 4000 3小时 5000 🧧定金100预留位置 不外出 不包夜 💐💐💐 🈲️无套 🈲️后花园 🈲️酒驾 🈲️暴力 🈲️嗑药 🈲️拍照 🈲️口嗨勿扰 会直接拉黑 理解第一 素质至上 私信:@caihe257 双向机器 @caihe22557_bot
Showing the 11 most recent of 11 posts we hold for @caihe22557. 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 4 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 September 2026 — this entry's latest reading, not the date you are reading this.
“普陀 彩禾” (@caihe22557), 76 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/caihe22557.
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.