Telegram RegisterThe public register of Telegram
Telegram profile photo for 舒舒的小🏠

Channel

舒舒的小🏠

@shushu5216

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

452subscribers

+320 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003692876528
TypeChannel
Username@shushu5216
Created7 April 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live11 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/shushu5216

Topic

Giveaways & airdrops — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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

132513322.513 August 2026 — 132 subscribers14 August 2026 — 446 subscribers20 August 2026 — 513 subscribers27 August 2026 — 492 subscribers2 September 2026 — 489 subscribers11 September 2026 — 452 subscribers45213 August 202611 September 2026
6 measurements spanning 29 days, net +320. 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 75–570 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 12:21452-37
2 Sept 2026, 18:28489-3
27 Aug 2026, 06:13492-21
20 Aug 2026, 12:18513+67
14 Aug 2026, 09:16446+314
13 Aug 2026, 15:47132first reading

Engagement

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

Reaction mix

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.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 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 2 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 April 2026 to 13 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

13 Aug 2026, 14:00 UTC208 views2 reactionsread 13 August 2026
Photo

🎉 联邦~禅城舒舒💃🏻福利抽奖🎰 🎁 奖品清单 • 1p半价券 × 1 📢 参与条件 • 加入 广州佛山联邦出击群(重生版) • 加入 广州佛山联邦老师榜 • 加入 广州佛山邦女郎动态榜 • 加入 广州佛山联邦老师打卡群 • 加入 广州佛山联邦抽奖榜 • 加入 舒舒的小🏠 ⌛ 开奖时间 • 2026-08-15 22:00:00 📜 抽奖说明 舒舒 :https://t.me/Gzffol/41769 1,本活动由舒舒老师赞助,私聊 @shushu1241 兑奖。 2,开奖后请老师七天内兑券,转让需老师同意。 3,中半价券先拉黑抽奖30天,出击交报告即解。 ✨ 愿好运常伴大家,祝大家好运!点击下方按钮参与抽奖。

2

13 Aug 2026, 12:59 UTC219 viewsread 13 August 2026
Photo

🎰 【府上 舒舒抽奖活动】 🎫 加入的前置频道: 🎫 加入 —— 佛山嫩妹甄选府 🎫 加入 —— 佛山嫩妹甄选榜 🎫 加入 —— 佛山嫩妹【备用榜】 🎫 加入 —— 佛山嫩妹甄选轮播群 🎫 加入 —— 佛山嫩妹备用榜单 🎫 加入 —— 嫩妹名探府【备用】 🎫 加入 —— 舒舒的小🏠 🎟️ 要求活动期间群内发言数 30 🎁 奖品内容: 半价/p × 1 💡 活动说明: 👉🏿1 自开奖时间起 3天内有效 ∴ 请在3日内约课(7天内兑奖) 👉🏿❷炸号中奖作废! 👉🏿❸出击完7日内提供详细的报告提交: @@Fndxbgbot (否则拉黑挂榜) 👉🏿❹ 严禁转让,买卖 发现后永久拉黑! 老师兑奖严格按照 开奖信息 跳转兑奖!跳转兑奖 📅 开奖日期: (UTC + 8) 2026年08月16日 20时58分52秒 ⚡️ 加成说明: ⚡️ 加成消耗:5个嫩妹币🎖 ⚡️ 加成次数:20 ⚡️ 额外消耗:每次

13 Aug 2026, 12:26 UTC191 viewsread 13 August 2026
Photo

🎰 【骑士团☆舒舒 半价活动】 🎫 加入的前置频道: 🎫 加入 —— 佛山少女御姐骑士团 🎫 加入 —— 佛山少女御姐榜 🎫 加入 —— 佛山少女御姐甄选 🎫 加入 —— 佛山少女御姐预备群 🎫 加入 —— 佛山少女御姐预备榜 🎫 加入 —— 舒舒的小🏠 🎟️ 要求活动期间群内发言数 15 🎁 奖品内容: 半价p × 1 💡 活动说明: 👉① 自开奖时间起 3天内有效 ∴ 请在3日内约课(7天内兑奖) 👉② 炸号中奖作废![老师可以拒绝兑奖] 👉③ 出击完7日内提供详细的报告提交: 「马如龙」 @QST_mrlbot (否则拉黑挂榜⚠️) 👉④ 严禁转让/买卖,发现后永久拉黑! 📢为保证老师的利益,请老师兑奖严格按照 开奖信息 跳转兑奖! 📅 开奖日期: (UTC + 8) 2026年08月16日 12时00分00秒 ⚡️ 加成说明: ⚡️ 加成消耗:8个少女币🎖 ⚡️

12 Aug 2026, 09:31 UTCviews —

舒舒的小🏠 pinned «个人兼职请多多关照 👠净身高1.65体重48.杯罩C 人照一致(可验证)性感气质五官精致,性格活泼开朗温柔体贴 上课费用 500P课时40分钟 1000PP课时90分钟 包夜2888限四次八小时 外出课费➕1张 注‼️需先收路费(口令) 包夜定金:200 可提前预约收定金见面不喜欢可以退 服务:鸳鸯浴 🛀🏻调情 无套口 情趣内衣 丝袜诱惑 舌吻 69 各种姿势激情啪啪❤️‍🔥 哥哥有自己喜欢的制服可以自带 🈲️禁:桩机 无🍑 口嗨 低素质醉酒 吃药 吸毒 后庭 狐臭 拍视频 🈲️:撩骚勿扰,素质至上,理解第一…»

12 Aug 2026, 09:31 UTC334 viewsread 13 August 2026

个人兼职请多多关照 👠净身高1.65体重48.杯罩C 人照一致(可验证)性感气质五官精致,性格活泼开朗温柔体贴 上课费用 500P课时40分钟 1000PP课时90分钟 包夜2888限四次八小时 外出课费➕1张 注‼️需先收路费(口令) 包夜定金:200 可提前预约收定金见面不喜欢可以退 服务:鸳鸯浴 🛀🏻调情 无套口 情趣内衣 丝袜诱惑 舌吻 69 各种姿势激情啪啪❤️‍🔥 哥哥有自己喜欢的制服可以自带 🈲️禁:桩机 无🍑 口嗨 低素质醉酒 吃药 吸毒 后庭 狐臭 拍视频 🈲️:撩骚勿扰,素质至上,理解第一 @shushu1241

Showing the 12 most recent of 15 posts we hold for @shushu5216. 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 2 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.

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

“舒舒的小🏠” (@shushu5216), 452 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/shushu5216.

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.