舌吻茶话会报告:https://t.me/SHSWCHH 【妹子花名】:#桃桃 【联系方式】: @vi_tao05 【水费】:1600p 【正文】: #硬件分析 【颜值气质】人照8分,参考照片。真人有点新疆长相,应该是妈生脸,和一位故人『白虎苏苏』有些相似。自述05年广东人,大四文科生,没口音,有牙套。 【身材细节】162,90斤,细枝硕果。天然c罩杯,挺拔柔软,略外扩可手动聚拢,乳头乳晕大小适中,颜色粉。细腰无赘肉,有腰窝,腿长适中,足底嫩,翘臀有肉。下体有毛,一线天馒头逼,颜色粉。 【皮肤细节】黄偏白,很滑。无纹身。 #流程黄文 【服务体验】进门第一眼气质比照片差一些,对比五官,确是本人无疑,多看几眼,越发顺眼,是耐看型没错了,如果没有牙套笑起来会更好看。她身着小白裙,胸前沟渠亮眼。 付费落座,拖鞋矿泉水都已备好,另有红牛可饮用。妹子主动坐身边,头枕过来,挺会来事。简单kiss,爱抚调情,同去洗澡,她让我帮她脱衣服,小狐…

Channel
舌吻报告集
@SHSWBG
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
4,182subscribers
+3,878 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003930380256 |
|---|---|
| Type | Channel |
| Username | @SHSWBG |
| Created | Between 1 April 2026 and 30 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/SHSWBG |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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, 00:17 | 4,182 | +16 |
| 12 Sept 2026, 15:41 | 4,166 | -309 |
| 9 Sept 2026, 00:39 | 4,475 | +10 |
| 4 Sept 2026, 01:55 | 4,465 | +9 |
| 31 Aug 2026, 09:23 | 4,456 | -379 |
| 27 Aug 2026, 23:48 | 4,835 | +272 |
| 24 Aug 2026, 22:29 | 4,563 | +3,852 |
| 18 Aug 2026, 07:56 | 711 | +407 |
| 18 Aug 2026, 05:15 | 304 | first reading |
Engagement
6 posts held, back to 30 July 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 18 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 1 of the 6 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 30 July 2026 to 18 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
🎰 上海舌吻茶话会开群福利 📮 参与条件 🎫 加入-上海舌吻茶话会 🎫 加入-上海舌吻认证频道 🎫 加入-舌吻报告集 🎫 加入-舌吻老师开课群 🎁 奖品名单 💰️ 888元现金红包 × 1 💰️ 300元现金红包 × 1 💰️ 200元现金红包 × 1 💰️ 100元现金红包 × 5 📜 抽奖说明 🐍 开群福利 · 首轮抽奖 给全上海蛇蛇爱好者一个家, 汇聚优质资源,打造上海精品舌吻榜单。 新群初见,当然也要有点见面礼。 特此开启首轮开群福利抽奖,感谢每一位蛇蛇党的加入与支持。 好内容慢慢沉淀,好福利也不会缺席。 欢迎入群,也祝各位蛇蛇好运。🐍 一件加入蛇教👇 https://t.me/addlist/L3k7jvJtMSdmOTc8 📆 开奖时间 • 北京时间 2026-08-26 09:00
舌吻茶话会报告:https://t.me/SHSWCHH 【妹子花名】:#艺名 【联系方式】: 【水费】: 【正文】: #硬件分析 #流程黄文 #课后感 #综合评价(超级好评/好评/中评/差评) 写完请投递给 @SWBGTD_bot(投递时请把此句删除) 出击结束请在十日内出报告,过时不加积分(投递时请把此句删除) 投递时请附带出击记录(投递时请把此句删除)
❤1
Channel photo updated
Messages in this channel will no longer be automatically deleted
Messages in this channel will be automatically deleted after 1 day
Showing the 6 most recent of 6 posts we hold for @SHSWBG. 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 7 registered channels — 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@SHSWBG 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 19 August 2026 – 19 August 2026 · confirmed gone 9 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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.
“舌吻报告集” (@SHSWBG), 4,182 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/SHSWBG.
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.