Telegram RegisterThe public register of Telegram
Telegram profile photo for 成都学院日报社

Channel

成都学院日报社

@ChengDuXueYuanRiBaoShe

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

2,532subscribers

+2,493 since we began measuring on 3 September 2026

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

Register entry

Telegram ID-1003970087346
TypeChannel
Username@ChengDuXueYuanRiBaoShe
Created3 September 2026 — measured — dated from the channel’s first post
First recorded3 September 2026
Last confirmed live25 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/ChengDuXueYuanRiBaoShe

Topic

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

392,5321,285.53 September 2026 — 39 subscribers3 September 2026 — 39 subscribers4 September 2026 — 127 subscribers12 September 2026 — 852 subscribers25 September 2026 — 2,532 subscribers3 September 202625 September 2026
5 measurements spanning 22 days, net +2,493. 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
25 Sept 2026, 08:582,532+1,680
12 Sept 2026, 13:59852+725
4 Sept 2026, 03:38127+88
3 Sept 2026, 07:4539no change
3 Sept 2026, 07:3039first reading

Engagement

7 posts held, back to 3 September 2026 — 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.

ERR · 30 days
3.71%
avg views ÷ 2,532 subscribers
Avg views / post
94.0
6 posts measured
Reaction rate
0.962%
reactions ÷ views · ER floor
Posts in window
7
of 7 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 6 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 September 2026
Posts held7 (3 September 2026 – 3 September 2026)
Views total564
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 07:45 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

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 7 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 7 most recent posts we hold, published 3 September 2026 to 3 September 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

3 Sept 2026, 05:06 UTC208 views2 reactionsread 3 September 2026

成都学院群聊午报|2026-09-03 覆盖时间:2026-09-02 22:00~2026-09-03 12:00(北京时间) 数据状态:完整读取,未截断 今晨速览 昨晚的晚报发布后,群友开始讨论“少爬楼”和AI工具;午夜围绕首次沟通需要过往记录、个人体验与预期差异聊得最热。赶版本、远程处理工作和“玩AI上头”的自嘲穿插其中。凌晨2点后消息明显减少,8点起逐渐恢复,上午又聊到网上争论、工作对接,以及一则人员去向传闻。相关传闻截至12点仍缺乏可核实的结论。日报的新发布频道也在今早公布。 主要话题 1. 首次沟通就要过往记录,群友经历并不一致 00:22~00:34,一位群友回忆首次约课被要求提供历史记录,引来“第一次哪来记录”的追问。有人称自己也遇到类似要求,也有人表示没有。对话从核验要求延伸到群内熟悉程度与身份认同;这些是个人经历,不是本群统一规则。该起点共有51条后续回复,包含分支闲聊。 参考消息:讨论起点 ·…

❤2

3 Sept 2026, 01:44 UTC180 viewsread 3 September 2026

成都学院群聊晚报|2026-09-02 覆盖时间:2026-09-02 12:00~22:00(北京时间) 数据状态:完整读取,未截断 今晚速览 午后,一句“老师直接叫我真名”引出熟悉感与隐私边界的讨论,刚发布的午报也成了群友围观的新素材。下午在“想上岸”和消费预算之间来回拉扯,傍晚接连出现体验投诉、定金联系不上和疑似假群主私信的反馈。20点后,话题逐渐转向健身社交、体重、卧推和饮食,21:00~22:00成为本期最活跃时段。 主要话题 1. 被叫出真名,熟悉感也会让人“出戏” 12:44,一位群友分享被直接叫出真名的感受。回复围绕对方如何知道名字、信任与熟悉程度展开,之后又分叉到其他闲聊。这条起点的完整回复链有49条,但不等于49条都在讨论隐私;本报不摘录任何真实姓名。 参考消息:讨论起点 · 对称呼的追问 2. 午报发布,群友开始“在报纸里找自己” 13:47,公告账号发布今日午报。有人评价“有点东西”,也…

3 Sept 2026, 01:44 UTC89 viewsread 3 September 2026

成都学院群聊晚报|2026-09-02 覆盖时间:2026-09-02 12:00~22:00(北京时间) 数据状态:完整读取,未截断 今晚速览 午后,一句“老师直接叫我真名”引出熟悉感与隐私边界的讨论,刚发布的午报也成了群友围观的新素材。下午在“想上岸”和消费预算之间来回拉扯,傍晚接连出现体验投诉、定金联系不上和疑似假群主私信的反馈。20点后,话题逐渐转向健身社交、体重、卧推和饮食,21:00~22:00成为本期最活跃时段。 主要话题 1. 被叫出真名,熟悉感也会让人“出戏” 12:44,一位群友分享被直接叫出真名的感受。回复围绕对方如何知道名字、信任与熟悉程度展开,之后又分叉到其他闲聊。这条起点的完整回复链有49条,但不等于49条都在讨论隐私;本报不摘录任何真实姓名。 参考消息:讨论起点 · 对称呼的追问 2. 午报发布,群友开始“在报纸里找自己” 13:47,公告账号发布今日午报。有人评价“有点东西”,也…

3 Sept 2026, 01:43 UTC43 viewsread 3 September 2026

成都学院群聊午报|2026-09-02 覆盖时间:2026-09-01 22:00~2026-09-02 12:00(北京时间) 数据状态:完整读取,未截断 今晨速览 昨夜22点后,讨论先围绕单次支出、加价选择、健身饮食和身体状态展开;23点至凌晨1点,话题逐渐转向交易关系之外是否可能形成朋友关系,以及闲聊、陪伴和持续联系的边界。凌晨1点至3点出现较多陌生场景和安全经历分享,3点后群聊明显转静。早上8点后活跃度恢复,9点至12点集中讨论了群聊日报、Telegram数据接口、投票奖励、账号与定金风险,以及“砂舞”“床砂”等新名词。10点至11点是本期最活跃时段。 主要话题 1. 单次预算、加价选择与“请假式算法” 22:30以后,多位群友围绕是否加价、体验时长和个人预算交流。23:37的一条消息把日工资与单次支出作比较,并以“理论上应该请假”作结,引出持续回复。相关表达主要是群内玩笑和个人消费感受,不构成财务建议。 …

3 Sept 2026, 01:43 UTC27 viewsread 3 September 2026

成都学院群聊午报|2026-09-02 覆盖时间:2026-09-01 22:00~2026-09-02 12:00(北京时间) 数据状态:完整读取,未截断 今晨速览 昨夜22点后,讨论先围绕单次支出、加价选择、健身饮食和身体状态展开;23点至凌晨1点,话题逐渐转向交易关系之外是否可能形成朋友关系,以及闲聊、陪伴和持续联系的边界。凌晨1点至3点出现较多陌生场景和安全经历分享,3点后群聊明显转静。早上8点后活跃度恢复,9点至12点集中讨论了群聊日报、Telegram数据接口、投票奖励、账号与定金风险,以及“砂舞”“床砂”等新名词。10点至11点是本期最活跃时段。 主要话题 1. 单次预算、加价选择与“请假式算法” 22:30以后,多位群友围绕是否加价、体验时长和个人预算交流。23:37的一条消息把日工资与单次支出作比较,并以“理论上应该请假”作结,引出持续回复。相关表达主要是群内玩笑和个人消费感受,不构成财务建议。 …

3 Sept 2026, 01:43 UTC17 viewsread 3 September 2026

成都学院群聊晚报|2026-09-01 覆盖时间:2026-09-01 12:00~22:00(北京时间) 数据状态:完整读取,未截断 今晚速览 今天下午的讨论从住房和个人财务开始,14点后明显转向婚姻家庭、家务和生育成本。15点至18点是全天最活跃的阶段,群友集中交流临时取消、体验时长和选择标准。晚间的话题更多围绕健身健康、陪伴感与直接服务的差异,以及如何利用历史报告归纳个人偏好。 主要话题 1. 住房、房价与个人财务选择 12点前后一轮较完整的讨论围绕成都及周边房价展开。群内主要有三类看法:有能力时可以购买;资金不足时租房更轻松;人口继续向成都集中,可能使价格难以出现极端下跌。讨论随后延伸到银行、土地财政、拆迁补偿以及是否应该继续等待价格调整。 参考消息:租房与买房:https://t.me/chengduxueyuan/3094013 · 房价下跌预期:https://t.me/chengduxueyuan/…

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

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.

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

“成都学院日报社” (@ChengDuXueYuanRiBaoShe), 2,532 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/ChengDuXueYuanRiBaoShe.

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.