Channel
@ChengDuXueShengHuiQuanZhi
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,032subscribers
-35 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003652640179 |
|---|---|
| Type | Channel |
| Username | @ChengDuXueShengHuiQuanZhi |
| Created | Between 1 December 2025 and 31 December 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/ChengDuXueShengHuiQuanZhi |
Local community — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 11:39 | 2,032 | +12 |
| 13 Sept 2026, 09:41 | 2,020 | +4 |
| 9 Sept 2026, 10:59 | 2,016 | -8 |
| 4 Sept 2026, 00:58 | 2,024 | -10 |
| 31 Aug 2026, 23:27 | 2,034 | +2 |
| 29 Aug 2026, 04:24 | 2,032 | -5 |
| 26 Aug 2026, 10:24 | 2,037 | -8 |
| 23 Aug 2026, 07:38 | 2,045 | -7 |
| 20 Aug 2026, 01:23 | 2,052 | -10 |
| 16 Aug 2026, 18:56 | 2,062 | -5 |
| 13 Aug 2026, 14:06 | 2,067 | +1 |
| 10 Aug 2026, 18:36 | 2,066 | -1 |
| 8 Aug 2026, 01:14 | 2,067 | no change |
| 7 Aug 2026, 15:17 | 2,067 | first reading |
6 posts held, back to 31 December 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 6 posts for this entry, the most recent from 31 December 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
59 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 96.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 57 | 96.6% | |
| 💩 | 1 | 1.69% | |
| 😁 | 1 | 1.69% |
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 6 of the 6 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 59 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 31 December 2025 to 31 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
2025年9月25日 成都学生会十万人的老车库又炸了 我万万没想到老频道在完全封闭化私密运营后也被炸掉了，不得不说电报真牛逼。 这个老的车库频道见证了成都学生会2年多的成长历程，也硬抗了2年多的举报攻击，没想到最后还是顶不住，直接没了。 所幸曾经挂牌的老数据备份过，所以能得到还原。 最新的车库链接是 https://t.me/ChengDuXueShengHuiCheKu ，欢迎各位同学点上关注，不迷路！后续该频道里每天会发布部分历史数据，直到所有的历史记录都发布完毕。 另外还是强烈推荐各位同学使用学生会H5版， https://xueshenghui.org ，网页版的功能更加齐全，并且永不迷路！
❤5
不知不觉中成都学生会已经历经了3年风风雨雨了，所幸，纯公益的学生会在这3年的各种打击下并没有倒下，同时也保持初心，没有为利益所妥协。 在此，学生会管理组感谢各位老师同学的陪伴和支持，也感谢各位老师同学的信任！ 3年中，学生会经历了3次主群炸群，4次车库频道被炸，侥幸存活至今，但十万人大群和十万人频道业已不在了，这其实对于一个公益群来说是打击很大的，不管是从实际上还是管理员的心态上。 前路漫漫，明枪暗箭难防，所以今年学生会才开始探索学生会自己的边界，开始往电报之外扩展，由此迎来了学生会H5—— https://xueshenghui.org 3年之际，曾经的一些管理方式可能也当有所改变，过去的学生会，太佛系了，也太死板了。 不是说佛系不好，也不是说死板不好，毕竟学生会的诞生就是运营佛系的产物，而学生会在发展中保持初心也得益于对规则执行的死板。 但是，学生会的问题在于过分佛系，过分死板了。 学生会的初心只是作为一个纯公…
❤38💩1😁1
【成都学生会全职认证】 【花名】 #十七 【编号】 #B460 【标签】 #7p #嫩妹车 #颜值车 #兼职车 #巨乳 #排骨精 #感觉车 #态度车 #蛇蛇精 #可上门 #包夜 #代聊 #新人 #贡献折现 【硬件】 真人20岁，身高160+，体重85，身材属于是排骨精的类型，皮肤光滑，较白，无任何赘肉，无任何纹身，如图所示；胸c+，摸起来挺拔而柔软；下面毛量中等，紧度适中，湿润度适中；妹儿真人妆后和照片以及视频去美颜后9成相似度，人照一致。 【服务】 服务有 嫩妹三件套 （ 陪洗 + 口 + 做 ） + 舌吻 （无口臭） + 69 （舔批） 【费用】 700一次，50分钟；1200两次，90分钟；包夜3000，限3次 【联系方式】 @shiqi06789 【全职榜评价】 外围中大转楼凤，非精神小妹，良家感非常充裕，颜值好看并且耐看，身材更是牛，人苗条，奶子大且挺。因为年龄的问题，妹儿态度很好，同时服务很好，调情非…
❤5
【成都学生会全职认证】 【花名】 #乐乐 【编号】 #B707 【标签】 #6p #嫩妹车 #态度车 #蛇蛇精 #感觉车 #自聊 #新人 #贡献折现 【硬件】 妹儿自述20岁，工兵认为是23左右，身高162，体重98，身材属于是匀称的类型，无纹身；胸a~b；下面毛量偏多，紧度稍紧，有包裹感和收缩感，湿润度适中；妹儿妆后和图片以及视频去美颜后7~8成相似度。 【服务】 服务有 嫩妹三件套 （ 陪洗 + 口 + 做 ） + 舌吻 （ 无口臭 ）+ 69 （ 舔批 ） 【费用】 600一次，50分钟；900两次，90分钟 【联系方式】 @lele208 【全职榜评价】 自己做的妹儿，非精神小妹。妹儿态度很好，听话，日批有反馈，昆感也不错，屁股很软，很适合后入。。根据大量狼友报告反馈，经受了时间的检验，全员一致好评（无任何差评）。
❤6
学生会H5今日正式上线！ 永久域名为 https://xueshenghui.org 欢迎各位使用
❤2
学生会官网更新了！更新功能如下： 1.优化首页大屏展示 2.展示老师具体地址，支持搜索地点，比如搜索龙光世纪中心、春熙路 3.支持注册和登录、支持电报一键注册。（绑定电报后才会同步电报号已有积分） 4.提交报告通过后会自动加信誉积分 5.新增我的收藏和我的报告，可以收藏老师并且可以查看已收藏老师和已提交的报告 6.新增娱乐板块 7.新增勋章功能，100信誉积分解锁狼中之王 https://xueshenghui.org
❤1
Showing the 6 most recent of 6 posts we hold for @ChengDuXueShengHuiQuanZhi. 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.
Named by 1 registered channel — 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“成都学生会全职” (@ChengDuXueShengHuiQuanZhi), 2,032 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/ChengDuXueShengHuiQuanZhi.
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.