Telegram RegisterThe public register of Telegram
Telegram profile photo for 涩聊

Channel

涩聊

@sange333888

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

203subscribers

-13 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002593878931
TypeChannel
Username@sange333888
Created17 April 2025 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live4 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/sange333888

Topic

Hacking & security — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 47% 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

2032192117 August 2026 — 216 subscribers8 August 2026 — 216 subscribers14 August 2026 — 219 subscribers20 August 2026 — 217 subscribers26 August 2026 — 215 subscribers2 September 2026 — 211 subscribers11 September 2026 — 210 subscribers19 September 2026 — 209 subscribers4 October 2026 — 203 subscribers7 August 20264 October 2026
9 measurements spanning 58 days, net -13. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 201–221 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 09:37203-6
19 Sept 2026, 00:18209-1
11 Sept 2026, 16:40210-1
2 Sept 2026, 16:55211-4
26 Aug 2026, 22:48215-2
20 Aug 2026, 19:43217-2
14 Aug 2026, 14:55219+3
8 Aug 2026, 10:47216no change
7 Aug 2026, 16:50216first reading

Engagement

9 posts held, back to 17 April 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 9 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤150.0%
👍150.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 2 of the 9 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 9 most recent posts we hold, published 17 April 2025 to 6 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

6 Aug 2026, 15:18 UTC44 views1 reactionsread 8 August 2026

说一下基本流程:事项 1:需要打粉各种社交app引流把鱼引流到app,app上面有全国各地的虚拟妹妹,同城小妹,鱼可以自己选择妹妹主动私聊,然后谈好价格,时间地点, 2:也可以自己立妹子人设,兼职小妹,把鱼引到到平台,说自己在平台做兼职,然后在平台上面选择一个同城同人设的妹妹和鱼聊天,快鲨慢鲨都可以的,只要鱼不卸载,机会都是有的,粉不会流失,不用担心死号掉粉 3:平台自带各种客服,轮换各种方式角色鲨鱼,告别一个人鲨鱼多次打抢的单一性,轮换身份鱼会更加相信,更加信任, 4:平台自带位置共享,语音包,提供鲨鱼话术,提供打粉渠道,提供出金通道,自己只需要安心聊天鲨鱼即可, 5:自己拿后台,自己打的粉都是到自己的后台上面,所有角色自己控制,知己知彼 百战不殆,从开始到结束都是你一个在换个方式和鱼聊天,能上台子成功率极高, 6:可以陪跑,不懂的都会教,白嫖资源话术的勿扰,寻找志同道合的朋友合作共赢

👍1

8 Feb 2026, 12:31 UTC418 views1 reactionsread 8 August 2026

我们需要的粉是精准的嫖娼用户。首先需要确定的是。用户已经在酒店开好房间如果是在家用户或者要去小妹公寓的话支付了定金。 流程1 您这边跟客户聊天聊好了之后,客户确认要小妹了,开好酒店,宾馆,民宿,旅馆之后,您让客户提供房卡或者门牌号,民宿入住指南,您确认好了,客户选好小妹,套餐了,由我这边提供qq群二维码,发酒店位置电话号码,剩下的由我这边的人员操作(用户开了酒店。如果不收定金入金成功率50%。收了定金了入金成功率90%以上) 流程2 客户要求去他个人住宅住宿小区,您这边需要让客户提前发100块钱定金才能给他安排,客户不肯发定金,您就让他去开酒店,如果客户发完定金,选好套餐,选好小妹了,您让客户提供个人住宅详细地址:比如小区:(几号楼几单元几号房)提供好了之后,由我这边发qq群,剩下的由我这边操作 (发定金的意义就在于用户如果在家。不需要房间费用。就完全没有付出任何成本。很难处理) 流程3 客户要求去小妹公寓的您让他先发10…

❤1

Showing the 9 most recent of 9 posts we hold for @sange333888. 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.

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 4 October 2026 — this entry's latest reading, not the date you are reading this.

“涩聊” (@sange333888), 203 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/sange333888.

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.