头课可约

Channel
芝芝🍒🍒后花园
@zhizhi8366
On this record: Growth · Engagement · Posts · Citations · Cite this entry
449subscribers
-169 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003794300670 |
|---|---|
| Type | Channel |
| Username | @zhizhi8366 |
| Created | Between 1 February 2026 and 17 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/zhizhi8366 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 03:23 | 449 | -165 |
| 8 Aug 2026, 15:41 | 614 | -4 |
| 8 Aug 2026, 03:02 | 618 | no change |
| 8 Aug 2026, 02:18 | 618 | first reading |
Engagement
15 posts held, back to 17 May 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
- 4.68%
- avg views ÷ 449 subscribers
- Avg views / post
- 21.0
- 7 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 7
- of 15 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 July 2026 |
|---|---|
| Posts held | 15 (17 May 2026 – 28 July 2026) |
| Views total | 147 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 03:02 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.
Recent posts
Sticker, posted without a caption
💃老师:#芝芝 🤖链接: https://t.me/SZDAO2/2353 💒位置:#南山 ------------------ 💌出击报告: 进门后衣服一脱,三点粉得非常明显。白净的皮肤衬得那三点粉嫩扎眼,胸前的颜色和下面一致,光是看着就让人呼吸重了几分。她先上手做胸推。软肉把整根完全夹住,中间那道沟又热又紧,上下套弄的时候还会故意用力挤压,顶端一次次从乳肉里露出来又被吞没。她自己也看着,偶尔低头用舌尖舔一下,动作又骚又专注。真正坐上来时她选了泰山压顶。整个人的重量压下来,粉嫩的私处把整根一点一点吞进去,直到完全坐实。她不急着大幅动作,先用身体压着慢慢研磨,让人清楚感觉到被她又热又软的内部完全包裹。等适应了才开始有节奏地起伏,每次落下都又深又重,三点粉的视觉在这个姿势里被放大到极致。漫游的方便、三点粉的强烈视觉、胸推的扎实包裹、泰山压顶的重量与深度,整场过程被她做得又色又有冲击力。结束的时候她还保持着坐着的姿势喘了几口气,粉嫩…
要到7点才有位置噢
💃老师:#芳芳 🤖链接: https://t.me/SZDAO2/2465 💒位置: #宝安 ------------------ 💌出击报告:芳芳一靠近就伸舌头过来舌吻,又软又湿,亲得又深又久,津液交换得差不多了才松开。接着直接低头无套口,口腔温热真实,含住后认真吞吐,舌头灵活地缠绕,时而深吞时而轻舔顶端。没有隔阂的触感特别明显,她还时不时抬眼看我,又色又专注。舌吻的密和和无套口的真实,短短一场就很有感觉。 报告提交机器人:@BT888866bot 报告提交条件:需要提供约课记录及付款记录验证
Sticker, posted without a caption
💃老师:#芝芝 🤖链接: https://t.me/SZDAO2/2353 💒位置:#南山 ------------------ 💌出击报告:这次约了芝芝,体验非常棒。她主动抱住我,嘴唇柔软湿润,舌头灵活地伸进来深吻,缠绵热烈,吻得我呼吸都急促起来,双手也不停在身上游走,氛围很快被点燃。吻了大概十多分钟后,我们进入69环节。她转过身来,小嘴温柔地含住我的鸡巴,吸吮深喉技术熟练,舌头同时舔弄着蛋蛋,而她的下面粉嫩多水,我舔得她不停扭动腰肢,双方都爽得直哼哼,69玩得特别投入和谐。之后进入爱爱主戏,她骑乘位主动上下套弄,里面又紧又热,包裹感极强,配合她扭腰的动作,撞击声和水声此起彼伏。她时不时俯身舌吻我,胸部贴着我摩擦,感官刺激拉满。我们又换了几个姿势,她配合度很高,叫声甜美又诱人。过程芝芝服务主动热情,节奏把握得好,从前戏到正戏层层推进,安全措施也到位。芝芝的舌吻、69和爱爱组合服务让人回味无穷,推荐给喜欢全套激情体验的朋友! …
Photo, posted without a caption
准备有空
Sticker, posted without a caption
🧚♀️艺名:#芝芝 📍位置:#南山 👙身材:身高168体重49KG 胸 c 🎀价格: 1000p 1800pp 💌联系:@zhizhi836 @zhizhi836bot ✈️频道: https://t.me/zhizhi8366 🛌服务:69 舌吻 爱爱
8点可约
Showing the 12 most recent of 15 posts we hold for @zhizhi8366. 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 — 460,395 of 1,481,306entries 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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“芝芝🍒🍒后花园” (@zhizhi8366), 449 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/zhizhi8366.
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.