#艺名: #王富贵 #定位: #龙岗坂田 年龄18岁.身高168Cm. 体重45kg胸围34C, 课费:p1600/pp2800 包时三个小时4000 包时五个小时6000 私信: @kk586935 双向: @kk586935bot 个人频道: t.me/Ff56235 个人报告榜: t.me/xx586935 个人群: t.me/kk5869358
❤3

Channel
@sz88888a
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
23,106subscribers
+19,460 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001824082426 |
|---|---|
| Type | Channel |
| Username | @sz88888a |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/sz88888a |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 00:01 | 23,106 | -24 |
| 16 Sept 2026, 14:18 | 23,130 | -5 |
| 14 Sept 2026, 16:58 | 23,135 | -9 |
| 13 Sept 2026, 02:00 | 23,144 | -19 |
| 11 Sept 2026, 02:36 | 23,163 | -4 |
| 8 Sept 2026, 04:40 | 23,167 | -11 |
| 5 Sept 2026, 00:21 | 23,178 | +19,998 |
| 1 Sept 2026, 09:44 | 3,180 | -85 |
| 28 Aug 2026, 22:58 | 3,265 | -20 |
| 25 Aug 2026, 17:06 | 3,285 | -44 |
| 23 Aug 2026, 02:14 | 3,329 | -8 |
| 19 Aug 2026, 22:02 | 3,337 | -125 |
| 16 Aug 2026, 16:54 | 3,462 | -54 |
| 13 Aug 2026, 07:53 | 3,516 | -79 |
| 10 Aug 2026, 14:41 | 3,595 | -52 |
| 7 Aug 2026, 12:12 | 3,647 | +1 |
| 7 Aug 2026, 11:16 | 3,646 | first reading |
3 posts held, back to 26 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 3 posts for this entry, the most recent from 14 February 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
12 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 12 | 100.0% |
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 3 of the 3 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 26 December 2025 to 14 February 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.
#艺名: #王富贵 #定位: #龙岗坂田 年龄18岁.身高168Cm. 体重45kg胸围34C, 课费:p1600/pp2800 包时三个小时4000 包时五个小时6000 私信: @kk586935 双向: @kk586935bot 个人频道: t.me/Ff56235 个人报告榜: t.me/xx586935 个人群: t.me/kk5869358
❤3
#定位: #福田 #艺名: #shame 个人开课 拒绝中介 假免单 职业平面模特 shame 来自四川 02年 净身高:166 体重:45KG 胸围36D🙈天然未改动 个人特点:粉嫩肤白,温柔可人,年轻有活力,萝莉控 敏感体质,易高潮,配合度高,后入感极佳 服务内容: 鸳鸯浴 、无套口、深、胸推、臀推、情趣丝袜、 制服诱惑、私密️调情、等等 🉑69 🉑蛇纹 🉑外出上门 姿势配合:老汉推车,观音坐莲,蚂蚁上树,花式调情,期待哥哥解锁各种姿势 课费 1800/ p (60分钟) 3000/pp (90分钟) 下午茶4000(三小时) 夜课6000(8小时) 私聊个人:@Shamebb4468 个人频道: t.me/sha…
❤3
#深圳 #(全区)#按摩 位置不同,价格有点偏差,私我了解价格㊙️ 先收定金的都是骗子,本人的是到店付费,不收任何定金 东莞94也可安排 95 时间60分钟 口💋爆 🈶️独立的卫生间🛁口爆👅射嘴里 真舌毒🐉,真🐼调情,舌尖漫游👅,舔蛋蛋,蛇绕缠身🐍,69🔥式互口,环游口👄69式互口💋躺着口👄横着口💋竖着口👄站着口👄深喉口,最后无套射妹妹嘴里,95包括94的项目 会所SPA94 时间70分钟 背部头部放松按摩,蚂蚁上树🐜十指弹琴👏丝袜诱惑👠,背部舌尖漫游👅,胸推臀推,高山流水💦,真舌毒龙🐉,69式互舔💋蛋蛋吃鲍鱼,🦎蛇绕全身,舌尖画太阳☀️,等等各种绝技,最后,🌺式调情,手推出水, 独家96口爆2次 96服务如下 梦幻联动艳舞挑逗💃🏼 吸🍳舔🍳深🐒🫦爆(爆第一次) 🐻推🐼压🫦罐拔痧 🇯🇵日式毒🐲倒挂金钩🪝 🧊🔥吐珠,🐻滑全身 🇺🇸美式毒🐲🐻推🐻打 👅扫禁区🧹抓🐲筋 爱的…
❤6
Showing the 3 most recent of 3 posts we hold for @sz88888a. 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.
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.
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.
@sz88888a named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳老师榜” (@sz88888a), 23,106 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/sz88888a.
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.