Telegram RegisterThe public register of Telegram
Telegram profile photo for 姗姗秘密花园

Channel

姗姗秘密花园

@shanshan01201

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

1,417subscribers

+1,377 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-1004478986023
TypeChannel
Username@shanshan01201
Description私聊 @shanshan0212 双向 @SSjqrtetris_bot
First recorded29 September 2026
Last confirmed live29 September 2026
Measurements held10
On Telegramt.me/shanshan01201

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 29 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

401,4187297 August 2026 — 40 subscribers7 August 2026 — 100 subscribers15 August 2026 — 235 subscribers22 August 2026 — 437 subscribers28 August 2026 — 320 subscribers5 September 2026 — 371 subscribers13 September 2026 — 1,411 subscribers17 September 2026 — 1,418 subscribers26 September 2026 — 1,417 subscribers29 September 2026 — 1,417 subscribers1,4177 August 202629 September 2026
10 measurements spanning 53 days, net +1,377. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Sept 2026, 17:111,417no change
26 Sept 2026, 07:381,417-1
17 Sept 2026, 07:191,418+7
13 Sept 2026, 07:361,411+1,040
5 Sept 2026, 11:56371+51
28 Aug 2026, 22:25320-117
22 Aug 2026, 07:28437+202
15 Aug 2026, 00:46235+135
7 Aug 2026, 18:20100+60
7 Aug 2026, 12:3340first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Mentions

Named by 6 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.

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

“姗姗秘密花园” (@shanshan01201), 1,417 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/shanshan01201.

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.