28 Aug 2026, 09:01 UTC6 viewsread 29 August 2026
Photo
Photo, posted without a caption
Channel
樱樱的后宫
@malimali9900
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
592subscribers
-2 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003115581350 |
|---|---|
| Type | Channel |
| Username | @malimali9900 |
| Created | Between 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/malimali9900 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 05:26 | 592 | -2 |
| 29 Aug 2026, 16:30 | 594 | first reading |
Engagement
16 posts held, back to 4 March 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
- 1.86%
- avg views ÷ 592 subscribers
- Avg views / post
- 11.0
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- 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 28 August 2026 |
|---|---|
| Posts held | 16 (4 March 2026 – 28 August 2026) |
| Views total | 22 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 16:30 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
- 14s
- Average length
- 14s
Measured directly from 1 video 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
17 Aug 2026, 09:11 UTC16 viewsread 29 August 2026
Forwarded from @SHDD333
💃老师：#樱樱 🤖链接： https://t.me/shanghaidadao/11747 💒位置：#普陀 ------------------ 💌出击报告：自己穿着丝袜进来，还特意说想让人把丝袜撕破。 刚开始她就把腿抬起来，用脚蹭了蹭，眼神带着点期待。真撕开的时候她明显颤了一下，裂口处的皮肤和黑丝对比很明显，她反而更兴奋，主动把腿缠上来。 波推是她主动做的，软肉夹着上下磨，力道比较实。吹箫接着上，含进去后吸得挺认真，舌头会动，偶尔用喉咙轻轻收缩。临近结束她没有退，而是继续含着，最后直接口爆全部收下，一点没漏。 丝袜被撕破后一直没脱，做爱的时候破口刮着皮肤，她里面还会夹。吹箫、口爆、波推都做了，再加上她自己求着撕丝袜的反应，整场比较有感觉。结束的时候她躺在那儿喘气，破丝袜还缠在腿上，看起来挺色的。
4 Aug 2026, 15:34 UTC28 viewsread 29 August 2026
💃老师：#樱樱 🤖链接：https://t.me/shanghaidadao/11231 💒位置： #普陀 ------------------ 💌出击报告：已经知道LS很久了，开门看到她的时候只见她穿着白色T，牛仔裤。大长腿暴露无疑，十分养眼。到了房间，LS以为是要先来一次，作为老SB的我倒是没那么着急。第一次，就好好欣赏这躯体就好了。聊了很久，很有女友感。脱掉上衣，曲线凹凸有致简直了。LS最美的时候就是坐在沙发上，有点近有点远和你一言一语慢慢拉进距离的时候，一颦一笑能感受到LS的呼吸的时候。慢慢洗完澡，LS还是娇嫩，细看可以看出老师没怎么化妆，素颜也是那么让人陶醉。约好了下次再好好玩儿，应该就是非常好的体验了。 聊地开心，初见养眼，作为小时女友陪伴很好。第一次就当认识，只好好啪啪了一次。约好下次时间充裕再好好开发。
27 Jul 2026, 15:35 UTC38 viewsread 29 August 2026
Forwarded from @SHDD333
💃老师：#樱樱 🤖链接： https://t.me/shanghaidadao/11231 💒位置： #普陀 ------------------ 💌出击报告：老师自己把黑丝穿好，还特意选了超薄款。刚开始她就带着点期待的眼神说“想要你把丝袜撕破…”，边说边把腿抬高，用脚轻轻蹭过来。我撕开的瞬间她明显颤了一下，裂口处白皙的皮肤和黑丝对比强烈，她反而更兴奋，主动把腿缠上来。真正做爱的时候丝袜一直没脱，破掉的边缘随着动作刮过皮肤。她里面又会夹又会缩，每一次顶进去都能感觉到明显的收缩，像是在主动往里吸。节奏稍微加快她就夹得更紧，嘴里还不停地求“再撕多一点…用力…”。丝袜被撕破时的反差、她自己求着被撕的反应、再加上会夹会缩的真实反馈，整场又色又有互动感。结束时她躺在那儿喘气，破丝袜还缠在腿上，裂口处全是水光。
22 Jul 2026, 09:26 UTC35 viewsread 29 August 2026
Forwarded from @SHDD333
💃老师：#樱樱 🤖链接：https://t.me/shanghaidadao/11231 💒位置：#普陀 ------------------ 💌出击报告：丝袜是樱樱自己要求穿的，还特意选了超薄黑丝。刚开始她跪在面前吹箫，含得又深又湿，舌头灵活地缠着柱身上下滑动，偶尔用喉咙轻轻收缩，眼睛却一直看着我，又乖又色。丝袜腿跪在地毯上发出细微的摩擦声，视觉已经先赢了。吹到最爽的时候她突然停下来，声音带着点喘地说“想要你把丝袜撕破…”，边说边自己把腿抬高，用期待的眼神催促。我撕开的瞬间她轻轻叫了一声，裂口处白皙的皮肤和黑丝对比强烈，她反而更兴奋，主动把腿缠上来求插入。做爱过程她很会配合，被撕破的丝袜一直没脱，每次顶进去都能感觉到丝袜边缘刮过皮肤的触感。她会主动扭腰迎合，时而把破掉的丝袜脚踩在我胸口，时而抬高双腿让我看清楚结合的地方，嘴里还不停地求“再撕多一点…用力…”。整场又湿又紧，节奏完全被她的反应带着走，最后一起到了高潮。吹箫的细致、…
17 Jul 2026, 14:41 UTC39 viewsread 29 August 2026
Forwarded from @SHDD333
💃老师：#樱樱 🤖链接： https://t.me/shanghaidadao/10198 💒位置：#普陀 ------------------ 💌出击报告：一进门就跪在我面前，乖乖开始深喉。樱樱的口活真是一流，直接全根吞入，喉咙紧紧收缩按摩龟头，吸得又深又狠，口水拉得老长，顺着下巴滴到丝袜上。她边深喉边用媚眼看我，骚得不行。深喉之后，她把奶子挤出来给我波推（胸推）。一对又软又弹的奶子夹住鸡巴用力上下套弄，奶肉包裹得特别紧实，还低头吐很多口水润滑，推得又滑又爽。玩到最兴奋的时候，她主动求我丝袜求撕破。她跪趴在床上，高高翘起屁股，娇喘着说：“哥哥……把樱樱的黑丝撕破，用力操我……”我抓住丝袜用力一撕，“刺啦”一声裆部彻底破开，露出湿透的粉嫩骚穴。我直接挺腰狠狠插进去，抓着她腰疯狂抽插，一边操一边继续撕扯她大腿上的丝袜，把黑丝撕得一条一条挂在身上。她被干得浪叫不止，屁股还主动往后顶：“撕得好爽……哥哥操烂樱樱的骚逼……”丝袜破损的样…
14 Jul 2026, 05:34 UTC47 viewsread 29 August 2026
正常营业
14 Jul 2026, 05:33 UTC46 viewsread 29 August 2026
Photo
Photo, posted without a caption
8 Jul 2026, 14:15 UTC48 viewsread 29 August 2026
Forwarded from @SHDD333
💃老师：#樱樱 🤖链接： https://t.me/shanghaidadao/10198 💒位置： #普陀 ------------------ 💌出击报告：一进来就很懂规矩，直接开始服务。先是吹箫，深喉技术非常专业，吞得又深又顺，舌头灵活绕着吸吮，口活又骚又舒服。波推（胸推）也做得顶，D杯夹得又软又热，滑动顺滑，视觉效果爆棚。后面正式做爱，她小穴会夹会缩，插进去后肉壁像小嘴一样疯狂收缩吸吮，骑乘位的时候主动猛扭腰，爽得我直吸气。各种姿势都随便配合，后入、观音坐莲、侧入等都玩得很开，叫床声又浪又真实。她还玩了丝袜求撕破环节，我把黑丝撕开直接干，视觉和触感双重刺激。情趣内衣和高跟鞋全程穿着，制服诱惑玩得特别过瘾。最后口爆，她深喉到底让我射在嘴里，全部吞下，服务态度很懂规矩，不洗不事直接搞定。
5 Jul 2026, 08:55 UTC50 viewsread 29 August 2026
Forwarded from @SHDD333
💃老师：#樱樱 🤖链接： https://t.me/shanghaidadao/10198 💒位置： #普陀 ------------------ 💌出击报告：老师服务态度很好，一进门给我水喝，全程态度都是尽可能满足配合。进门之后帮洗澡，床上的时候口，老师也不会有脾气，舔🐔真的一流然后又口受不了就开始干他的小烧逼，反而老师的口活是我遇到最好的，没有之一，全部吃进去之后，舌头还可以动，很舒服。口完之后，就是各种姿势，逼逼很紧，老师很敏感，随便动一下都会发出那种令人听着就享受的叫声。 自由评论：必反！！！
3 Jul 2026, 11:22 UTC43 viewsread 29 August 2026
Forwarded from @SHDD333
💃老师：#樱樱 🤖链接： https://t.me/shanghaidadao/10198 💒位置： #普陀 ------------------ 💌出击报告：进门先来了个贴贴抱抱，果然是香香软软的，抱在怀里像揣了只大奶猫。寒暄了一会，她便领着我去洗浴。 洗漱完毕，上了床，开始前戏，相比较感官上的感受，氛围感和情绪反而更为强烈。感觉差不多了，开始攻守转换，对着大葡萄和小蝴蝶同步进攻，感受手指开始渐渐湿润。 “就让我用这几分钟喜欢你”。接着开始正戏，进去的那一瞬，紧窄得几乎寸步难行，像是被一股温热的力量密密匝匝地包裹住。轻轻一动，她便开始低低地轻吟起来，声音细细的，像风吹过琴弦。身体与身体的对话不需要翻译，每一次进退都合着彼此的律动，呼吸渐渐搅成一股。最后让夏沫来结束，她骑得很激烈，腰肢像一条被驯服的蛇，我被她摇得意识松散，最后还是缴械投降。 今夜的感觉很特别，美得像一场梦，后面还会再来的。
5 Jun 2026, 06:05 UTC67 viewsread 29 August 2026
Photo
合你胃口吗？
Showing the 12 most recent of 16 posts we hold for @malimali9900. 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 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“樱樱的后宫” (@malimali9900), 592 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/malimali9900.
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.