【时间】:2026-08-30 【老师】:昭昭 【留名】:马嘉祺2.0 【人照】:8.5 【颜值】:8.5 【身材】:9.5 【服务】:9.5 【态度】:9.5 【环境】:9.5 【综合】:9.17 【过程】:🐶颜值:人照8-9分,照片有美白和磨皮,正常黄皮肤,化着妆 🐶身材:163/90的样子,正常黄皮肤,比较瘦,肚子无赘肉,🐻部是b,乳头较大,下面毛发正常量,蝴蝶户型,掰开里面有点粉 🐶态度:昭昭线上很能聊天,线下去了也是很能聊天,很热情,线上线下一致,会主动和你说话 🐶服务:陪浴 口 做 舌吻 舔盘子都有,舌吻是大蟒蛇管够,陪浴会帮你洗 🐶环境:位置在地铁站附近,交通比较便利,也有指引图引导。教室是日租的酒店民宿,进门空气比较清新,有香薰的味道,地面整洁无垃圾,一次性浴巾,漱口水都有,但没有一次性床单,可以准备一下 🐶过程:昭昭在群里聊的嗨皮,于是在下午跟昭昭约好时间cj,进门后昭昭主动打招呼,很热情,聊了一会之…

Channel
昭昭的城堡🏰
@zzybf8888
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,767subscribers
+374 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003497038319 |
|---|---|
| Type | Channel |
| Username | @zzybf8888 |
| Created | Between 1 November 2025 and 30 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/zzybf8888 |
Topic
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 77% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 15:41 | 1,767 | +58 |
| 13 Sept 2026, 04:19 | 1,709 | +52 |
| 8 Sept 2026, 23:20 | 1,657 | +128 |
| 3 Sept 2026, 12:37 | 1,529 | +123 |
| 31 Aug 2026, 13:13 | 1,406 | +13 |
| 31 Aug 2026, 03:15 | 1,393 | first reading |
Engagement
20 posts held, back to 21 August 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
- 56.8%
- avg views ÷ 1,767 subscribers
- Avg views / post
- 1,000
- 20 posts measured
- Reaction rate
- 0.156%
- reactions ÷ views · ER floor
- Posts in window
- 20
- of 20 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 12 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 20 (21 August 2026 – 30 August 2026) |
| Views total | 20,063 |
| Reactions total | 21 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Aug 2026, 03:15 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.
Reaction mix
21 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 47.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 47.6% | |
| 🤣 | 4 | 19.0% | |
| 🕊 | 3 | 14.3% | |
| 😁 | 2 | 9.52% | |
| 🥰 | 2 | 9.52% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 12 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 21 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 21 August 2026 to 30 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
好男人都去哪了,都去哪了咩😕
上课,今天开课晚,还有少量位置……
上课吧家人们,今天嗯……就这样吧哈哈哈哈哈哈
⚔ 宝可梦训练家对战报告 ⚔ 【👾 宝可梦代号】:昭昭 【🎰 综合表现得分】:9.33 【💰 性价比得分】:10 【人照】:9 【颜值】:9 【身材】:9 【态度】:10 【对战过程】:进门先白嫖了一瓶水,坐着聊了两句才去洗的,有陪浴,服务过程就是嫩妹三件套,要好评的是她的态度,我今天时间比较长,有点桩,但是妹妹没有不耐烦也没有催,也没有像其他ls那样说给我打出来啥的,直到后面实在累的不行才结束。 全程没有催,不机车,整体好评,等我调整好状态再来。 【推荐|一般|拉胯】:👍 好评 【👤 训练家留名】:buridan l 【🪖 工兵车评】:否
好好好放鸽子的全给我变短5cm🙂
🕊3🤣2
讨厌的下雨天🐻
😁2
【时间】:2026-08-27 【老师】:昭昭 【留名】:花吃 【人照】:9 【颜值】:9 【身材】:8.5 【服务】:9 【态度】:10 【环境】:8 【综合】:8.92 【过程】:老师的人照可以打9分,照片的美颜会显得美白一些,实际老师是小麦色皮肤。然后身材属于偏瘦的体型了,🐻能够触碰一下b的门槛,不过是挺软和的(当时捏了捏跟果冻一样Q),身上也挺滑溜的。见了面还是老师更为健谈的打起招呼,老师的性格会更大方些,让老师去服侍洗澡,因为比较急就只清洁了下追追(如果想要老师帮你洗一洗身上的话提一嘴老师也会帮的),擦干净后老师就会让你躺着去进行服务,一直亲到追追去进行挑逗。然后让老师来进行69,对着老师的洞口就是一阵探索,用舌头探进洞里的时候老师身体颤抖会比较大一些,老师的口活也很好,感觉不到任何的齿感,之后变为女上位的姿势,前后摇晃着我的追追,因为老师比较瘦,所以女上不会压的人很难受,还说着不会那么快把我秒了😭,动了没一会就赶忙让…
❤4
【时间】:2026-08-24 【老师】:昭昭 【留名】:蝙蝠侠 【人照】:9 【颜值】:9 【身材】:8.5 【服务】:9 【态度】:9.5 【环境】:9 【综合】:9 【过程】:探花阁工兵出击。首先感谢AL哥的工兵转让和私人赞助,让我有幸体验到东北妹妹。拿到工兵名额,立即联系妹妹,由于没得到回复,大中午一直兴奋,午觉都没睡。后来妹妹说今天起来晚,大概4点左右开课,中间发生点小插曲,4.30到妹妹房间。公寓式酒店,摆设陈列很整洁,妹妹人照基本一致,进去闲聊几句,交水费,妹妹有陪浴,可是哦大老远来,有点累,便算了,轮流洗浴。洗完特意让妹妹穿上衣服,抱着舌吻,互啃好一阵子,跟妹妹抱在一起,爽得很。想着单手揭开妹妹的罩子,奈何手法不行,有待训练。缠绵一会,让妹妹先躺下,开始欣赏妹妹的妹妹,发量较多,管他呢,上嘴开舔就是,舔一会就进去摸索人体的基本构造。感觉差不多了,于是让妹妹帮我口,分分钟就硬了,妹妹取套开始女上,妹妹女上表现很专业…
❤1
哥哥好想你呀,隔着屏幕好想钻进你的怀里蹭蹭🥰
落枕小昭已上线🤪
❤1
上~课~了😋
Showing the 12 most recent of 20 posts we hold for @zzybf8888. 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“昭昭的城堡🏰” (@zzybf8888), 1,767 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/zzybf8888.
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.