今天排满啦明天一点头课可约 定金50约客 谢谢大家

Channel
个人💕苏酥05嫩妹
@txt00210
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
262subscribers
+187 since we began measuring on 10 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004361964954 |
|---|---|
| Type | Channel |
| Username | @txt00210 |
| Created | 7 September 2026 — measured — dated from the channel’s first post |
| First recorded | 10 September 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/txt00210 |
Topic
Other / unclassifiable — 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 27 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 |
|---|---|---|
| 27 Sept 2026, 14:01 | 262 | +140 |
| 12 Sept 2026, 03:58 | 122 | +47 |
| 10 Sept 2026, 19:23 | 75 | no change |
| 10 Sept 2026, 02:47 | 75 | first reading |
Engagement
15 posts held, back to 7 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
- 107.5%
- avg views ÷ 262 subscribers
- Avg views / post
- 282
- 12 posts measured
- Reaction rate
- 0.326%
- reactions ÷ views · ER floor
- Posts in window
- 15
- 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. It is computed over the 3 of 12 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 September 2026 |
|---|---|
| Posts held | 15 (7 September 2026 – 10 September 2026) |
| Views total | 3,380 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Sept 2026, 19:23 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
- 11s
- Average length
- 6s
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.
Reaction mix
4 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 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 15 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 7 September 2026 to 10 September 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
Channel name was changed to «个人💕苏酥03嫩妹»
现在有空
Video, posted without a caption
个人💕苏酥03嫩妹 pinned «苏酥课表 本人年龄03年,23岁,未婚未育,真的大🐻,身高163,胸围36真大E,服务态度好,高端会所老师培训出生。哥哥们喜欢的话按照下面的套餐选择。 A套餐400/1p 洗吹做 情趣丝袜40分钟 B套餐500/1p 洗吹做 情趣丝袜AB面服务 🐍吻 漫游 水中萧50分钟 C套餐 800/2p 洗吹做 情趣丝袜 AB面服务 🐍吻漫游 水中萧80分钟 D套餐 1100不限次 无限火力 100分钟 洗吹做 情趣丝袜 🐍吻 莞式服务 水中萧 情趣玩具 双飞1000出水1p50分钟 1600出水2p100分钟…»
苏酥课表 本人年龄03年,23岁,未婚未育,真的大🐻,身高163,胸围36真大E,服务态度好,高端会所老师培训出生。哥哥们喜欢的话按照下面的套餐选择。 A套餐400/1p 洗吹做 情趣丝袜40分钟 B套餐500/1p 洗吹做 情趣丝袜AB面服务 🐍吻 漫游 水中萧50分钟 C套餐 800/2p 洗吹做 情趣丝袜 AB面服务 🐍吻漫游 水中萧80分钟 D套餐 1100不限次 无限火力 100分钟 洗吹做 情趣丝袜 🐍吻 莞式服务 水中萧 情趣玩具 双飞1000出水1p50分钟 1600出水2p100分钟 [双飞是2人的价格] 洗吹做 情趣丝袜AB面服务 🐍吻 漫游 水中萧 特价夜3-7点不限次 1800 包夜12-7点 不限次 2800 禁止 无套 吃药 醉酒 桩机 吸毒 皮肤病 吊太大劝退 05年嫩妹不耐草 哥哥温柔点 嫩妹水多 叫声销魂 温柔女友感
现在放鸽子比较多,课比较满,大家要排课就先交定金50,谢谢
所在城市:大亚湾恒大 出击者名:小新 老师名称:苏酥 上课价格:400 妹子年龄:25以下 妹子容貌:照片相似度7-8分吧、白皮、微胖DS 妹子身材:9分,扣掉0.5分是因为有个勾八先我之前把老师桩损伤了,还有0.5后面会说 服务态度:不错的 环境设备:恒大小区,环境不错,紫色氛围灯 自由评论: 下午两三点刚睡醒,起来看了看榜单,没什么特别大性趣,到了晚上九点多 突然看到榜单更新了个莞式小嫩妹,看到没有双向机器人,换个小号打招呼 加上了老师微信,约个尾课一点左右,然后就去玩游戏了,到了十二点多直 接出发老师所在地,到了之后以为这个价估计会踩雷,没想到本人确实不错, 年轻,嫩,身材一流,话不多说,哈啦两句交了水费就开始洗澡,老师会陪 同,前后弄满沐浴露,老师手也很嫩,在身上前后滑来滑去,老二就不争气 的站了起来,老师身上也擦上沐浴露,擦出泡沫后,就冲水,冲完我忍不住 就在浴室抱着老师滑蹭,不得不说老师身体确实很嫩滑,老师有些抗拒,…
下课了,明天中午12点开课
【妹子花名】:#苏酥 【所在位置】:#大亚湾 【 标签 】:#服务型 #莞式 #69 #毒龙 #双飞 【修车费用】: #400-1/500-1 【凶器罩杯】:C 【身高身材】: 163/55kg 【大概年纪】: 24 【服务内容】: 莞式.洗吹做…. 【联系方式】:@txt020210 【频道课表】:https://t.me/txt00210 【备注双向】:
❤1
所在城市:大亚湾 出击者名:秀 老师名称:苏酥 上课价格:600/2p*工兵价 妹子年龄:23-24 妹子容貌:人照8分 妹子身材:微胖,C胸左右 服务态度:4.7/5 环境设备:4.5/5 自由评论:看到排雷贴,嫩妹服务控还是同一个小区,果断报名。老师原本明天才开课,看见我排雷于是收拾一下单开一节,真头课。遥控上楼,开门一瞬间就知道这次没踩雷。人照基本一致,抛去美颜滤镜,所以就八分吧。由于是单开课,就坐在沙发聊了,主播出身,会所92现在自己单做,于是对服务有更大期待了。 脱衣洗澡,仔细调了水温,然后一起水乳交融。在后面双手在胸前涂满沐浴露,双乳不停地在背后磨蹭着。乳头划过背上的每一寸肌肤,嫩手从上胸抚摸到胯下。转过身,与老师面对面看着,看着那粉嫩,忍不住向前吻了起来。舌头在双方的口腔打转,双手也不能停着,上下抚摸着那肉感的肌肤。戛然而止,老师往下一蹲便含住了那坚挺。水中之箫,如那高山流水,流连忘返。 共浴结束,该上战场了。仔细…
❤3
Photo, posted without a caption
Showing the 12 most recent of 15 posts we hold for @txt00210. 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.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“个人💕苏酥05嫩妹” (@txt00210), 262 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/txt00210.
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.