Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州学生会社区

Supergroup

杭州学生会社区

@xssqfff

Has discussion group

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

9,796members

-529 since we began measuring on 7 August 2026

56 online right now

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1004329477172
TypeSupergroup
Username@xssqfff
Description核对本群管理名称的每一个字母和数字!【社区管理】 @TC889966 【社区频道】 https://t.me/xssq617 【社区老群】 https://t.me/xssqfff 【社区报告】 https://t.me/xssq618
CreatedBetween 1 June 2026 and 23 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 August 2026
Last confirmed live23 August 2026
Measurements held15
On Telegramt.me/xssqfff

Growth

9,79610,39210,0947 August 2026 — 10,325 members8 August 2026 — 10,328 members9 August 2026 — 10,333 members10 August 2026 — 10,334 members12 August 2026 — 10,340 members12 August 2026 — 10,351 members14 August 2026 — 10,356 members16 August 2026 — 10,371 members17 August 2026 — 10,376 members18 August 2026 — 10,380 members19 August 2026 — 10,385 members20 August 2026 — 10,387 members21 August 2026 — 10,392 members22 August 2026 — 9,796 members23 August 2026 — 9,796 members7 August 202623 August 2026
15 measurements spanning 16 days, net -529. 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 9,707–10,481 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
23 Aug 2026, 10:469,796no change
22 Aug 2026, 16:459,796-596
21 Aug 2026, 08:1610,392+5
20 Aug 2026, 09:0410,387+2
19 Aug 2026, 10:1210,385+5
18 Aug 2026, 13:4410,380+4
17 Aug 2026, 12:2510,376+5
16 Aug 2026, 04:5610,371+15
14 Aug 2026, 11:3810,356+5
12 Aug 2026, 23:2410,351+11
12 Aug 2026, 00:3210,340+6
10 Aug 2026, 21:2110,334+1
9 Aug 2026, 20:1210,333+5
8 Aug 2026, 22:2110,328+3
7 Aug 2026, 20:0210,325first 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 3 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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“杭州学生会社区” (@xssqfff), 9,796 members as measured 23 August 2026. Telegram Register, tgregister.com/channel/xssqfff.

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.