NSFW涩涩预览群 pinned «📱宝子们,我们新做了会员预览群,简化了之前预览群的内容,后续会员群更新日志会发布到新频道里,大家看见后关注一下。 点击下方按钮加入⬇️⬇️⬇️ NSFW涩涩预览群»

Channel
NSFW涩涩预览群
@sese_shareVIP
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,165subscribers
-31 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002323077185 |
|---|---|
| Type | Channel |
| Username | @sese_shareVIP |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/sese_shareVIP |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 11 Oct 2026, 17:59 | 1,165 | -4 |
| 5 Oct 2026, 10:15 | 1,169 | -7 |
| 26 Sept 2026, 21:18 | 1,176 | -9 |
| 13 Sept 2026, 22:41 | 1,185 | -3 |
| 30 Aug 2026, 09:46 | 1,188 | -2 |
| 27 Aug 2026, 09:08 | 1,190 | -3 |
| 24 Aug 2026, 18:05 | 1,193 | +2 |
| 17 Aug 2026, 16:25 | 1,191 | -1 |
| 14 Aug 2026, 18:28 | 1,192 | -1 |
| 11 Aug 2026, 05:11 | 1,193 | -3 |
| 7 Aug 2026, 23:18 | 1,196 | no change |
| 7 Aug 2026, 19:45 | 1,196 | first reading |
Engagement
17 posts held, back to 9 July 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 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 17 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
43 reactions across 10 posts, in 2 distinct kinds. The most used accounts for 97.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 42 | 97.7% | |
| 🥰 | 1 | 2.33% |
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 10 of the 17 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 43 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 9 July 2025 to 4 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
📱宝子们,我们新做了会员预览群,简化了之前预览群的内容,后续会员群更新日志会发布到新频道里,大家看见后关注一下。 点击下方按钮加入⬇️⬇️⬇️ NSFW涩涩预览群
NSFW涩涩预览群 pinned «📱#会员群更新日志 新增三个会员群,可以下载转发 1.萝莉 白虎 幼态 软妹 甜妹 vip新群 2.网红Coser会员群无水印 VIP 3.微密圈 国产主播 VIP新群 新群刚建立,之前备份的时候老是封群,这次发布内容先慢一些,等群稳定后会加快内容发布。»
这三个群全部会放到总群里。 其中, 萝莉 白虎 幼态 软妹 甜妹 vip新群 网红Coser会员群无水印 VIP 这两个群会额外分别添加在cos写真会员群和福利姬会员群中,已经单独购买这两个会员群其中一个的请前往下单机器人中点击 /my_chat 可以直接加入新增会员群。 已购买总群的宝子们,直接在总群里面加入即可哦🥰
❤1
📱#会员群更新日志 新增三个会员群,可以下载转发 1.萝莉 白虎 幼态 软妹 甜妹 vip新群 2.网红Coser会员群无水印 VIP 3.微密圈 国产主播 VIP新群 新群刚建立,之前备份的时候老是封群,这次发布内容先慢一些,等群稳定后会加快内容发布。
❤1
💌前两天账号炸了,连带着私密预览群也炸没了,刚刚重新做了新链接,大家感兴趣的可以加一下,网盘群预览内容更加清晰
📱#会员群更新日志 总群新增9个 👑会员总群新增9个内部群,其中包括之前被封禁的福利姬VIP群。新群包括维度会员群(4个),少萝之家,微密圈原版文件(20000W+文件),网红主播,抖音快手主播私拍。 💌这些群只发布到会员群导航总站中,不用作单独出售,后续会员群新增信息都会发布在这里,大家可以关注此频道防止丢失哦。
❤1
💕欢迎宝贝们加入NSFW涩涩指南🥰 目前会员资源总量达300W视图 1、PIKPAK私密会员群 178元 24小时自助入群 资源总量达140TB+(持续更新中) 点击此处查看网盘群博主目录 点击查看预览群 PIKPAK资源预览 2、【SSVIP】Cos写真|福利姬 188元 24小时自助入群 预览套图的原图压缩包,累计40000+多个文件包,9000+多个花絮自拍视频,40T+的资源。 点击查看预览群 Cosplay|写真合集 3、萝莉福利姬内部频道 88元 24小时自助入群 点击查看预览群以及查看博主目录 推特福利姬分享 👑42群全部打包 388元 24小时自助入群 包含上面所有会员群,后续会不断增加新的会员群且完全免费,终身售后,无二次消费(会员群从建立之初由15个群到现在增加到42个) 点此查看全部会员群详情 ⭐️以上预览群为同步备份的资源群,大家可以关注一下,防止失联
❤7
📱会员群将在下月初做出调整。 1️⃣会员打包总群价格提升(后续增加新群免费入) 2️⃣支持PIKPAK网盘群,Cosplay博主合集打包群,推特福利姬群等内部群单独购买 具体内容更新将会在介绍群里发布,已经加入会员的宝子们不受影响。
📱#会员群更新日志 新增两个新群,COS图包原图资源群,会持续更新💌 SSVIP会员累计40000+多个文件包,9000+多个花絮自拍视频,40T+的资源 未流出专属套图打包群,全网最早更新 - 共计100+多套 专属合集打包群 320+多个模特写真合集 - 全网合集最全 💌3月6日,【详情】Cos合集打包 内容更新日志
❤7
推特原创博主合集更新中......
萝莉福利姬内部频道,持续更新中...... 👑6月3日,资源内容更新
❤1
Showing the 12 most recent of 17 posts we hold for @sese_shareVIP. 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
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
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@sese_shareVIP 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“NSFW涩涩预览群” (@sese_shareVIP), 1,165 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/sese_shareVIP.
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.