Telegram RegisterThe public register of Telegram
Telegram profile photo for 成都星辰公告栏

Channel

成都星辰公告栏

@xingchenggl

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1,120subscribers

+68 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002643198593
TypeChannel
Username@xingchenggl
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/xingchenggl

Growth

1,0521,1201,0866 August 2026 — 1,052 subscribers7 August 2026 — 1,054 subscribers10 August 2026 — 1,064 subscribers13 August 2026 — 1,068 subscribers16 August 2026 — 1,073 subscribers19 August 2026 — 1,079 subscribers23 August 2026 — 1,089 subscribers26 August 2026 — 1,101 subscribers29 August 2026 — 1,108 subscribers1 September 2026 — 1,117 subscribers6 September 2026 — 1,120 subscribers6 August 20266 September 2026
11 measurements spanning 30 days, net +68. 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 1,042–1,130 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 05:371,120+3
1 Sept 2026, 20:371,117+9
29 Aug 2026, 20:541,108+7
26 Aug 2026, 22:121,101+12
23 Aug 2026, 22:431,089+10
19 Aug 2026, 19:471,079+6
16 Aug 2026, 22:051,073+5
13 Aug 2026, 17:281,068+4
10 Aug 2026, 20:411,064+10
7 Aug 2026, 16:521,054+2
6 Aug 2026, 20:051,052first reading

Engagement

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

Reaction mix

25 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 84.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2184.0%
👍312.0%
😭14.00%

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 10 of the 18 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 25 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 26 October 2025 to 3 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

3 Aug 2026, 16:28 UTC143 viewsread 6 August 2026
Photo

报账格式 1 先确实时间 2 出发前说明星辰VIP来的 3 事后写报告,确认无误后报账 https://t.me/xingchenggl/133 #VIP

21 Jun 2026, 01:20 UTC≈5,540 views1 reactionsread 6 August 2026
Photo

【花名】 #VIP体验群 【车牌】 @tyvipxc 【地址】 #武侯区 #成华区 #高新区 #市中心 【标签】 #胸控 #成华区 #高新区 #市中心 #青羊区 #锦江区 #会所 #bt #VIP 专属福利重磅上线! 临时VIP答谢群,每月固定抽奖! 抽中任选福利:0元白嫖体验权益 OR 同等额度现金红包 实打实回馈一路帮忙的各位兄弟,榜单公正公开,人人有机会! 免费福利、现金红包随便拿,别错过每月薅羊毛机会,速进群占位 白嫖 红包 随你抽 每个月会在当月红牌榜提供一个白嫖或者等值现金红包,老师由群友选定 狼友进群条件:(任意一个) 方法1:3个不同星辰老师报告; 方法2:星光大于2; 管理认证后,即可进群。为保证普通狼友利益,群友只能是非实权狼友🫡🫡🫡,审核交 @xcbggj_bot https://t.me/tyvipxc 其他资料详https://t.me/xingchenggl/97 #VIP

1

12 May 2026, 06:18 UTC≈1,950 views2 reactionsread 6 August 2026
Photo

🎉 抽奖结果公布! 👥 参与人数:583 人 🏆 @sanbsd12s —— 一等奖 🏆 @ychhi7621 —— 二等奖 🏆 @8468982249 —— 三等奖 🏆 @Galhff —— 三等奖 🏆 @An_been —— 三等奖 🏆 @h3506096207 —— 三等奖 🏆 @leslie3899 —— 三等奖 🏆 @dilidilidida —— 四等奖 🏆 @az86520 —— 四等奖 🏆 @bsfgdcc —— 四等奖

2

4 May 2026, 15:43 UTC≈1,720 views1 reactionsread 6 August 2026
Photo

大群提交报告方法 1大群打 提交报告 2 按提示输入车牌,如图1 3 按照步骤12345,一步步提交即可(如图2) 4 待管理审核后,自然会加分 #提交报告 #报告 https://t.me/xingchenggl/129?single

1

18 Mar 2026, 14:36 UTC≈2,210 views6 reactionsread 6 August 2026
Forwarded from @cdxcxrckuVideo

《成都星辰百位新老师挂牌工作总结》(第7期)(编号:XC501-673) 为方便新进群友不盲目出击,对新老师有一个进一步了解,特推出月度老师总结(不一定刚好100位老师)⭐️ 综合友群或至少10个以上狼友反馈,排名在前列的有:(每项最多5个) 😍😍😍😍😍 颜值: #7p: #三上悠亚 @Ssyouya1314 ,#橘子 @jfbbfjf 嫩妹(22以下): #6p:#芭乐 @balebbo ;#棠果儿 @Tangguoer001;#可颜 @Keyan521;#欣欣 @Xinyue558 #7p:#芊芊 @qianq6868 ; 御姐(23-26): #6p: #蔡少芬遗失的妹妹 @yuqing11211 ; #7p:#小小 @xiaoxiao1079 ,#小羊 @CDXYSXS ,#小琪 @Yxcdmu10;#若晗 @rh88661, 少妇服务:#曲奇 @J9_Mzi 高评分(8.8以上): #6p:#yo

6

3 Dec 2025, 12:56 UTC≈3,660 views2 reactionsread 6 August 2026

每月推荐榜单: 1期 https://t.me/xingchenggl/70 2期 https://t.me/xingchenggl/71 3期 https://t.me/xingchenggl/88 4期 https://t.me/xingchenggl/91 5期 https://t.me/xingchenggl/102 6期 https://t.me/xingchenggl/113 7期 https://t.me/xingchenggl/124 8期 https://t.me/xingchenggl/126 9期 10期 说明 https://t.me/xingchenggl/73 链接 https://t.me/xingchenggl/125 #VIP #推荐

2

3 Dec 2025, 04:32 UTC≈25,000 views8 reactionsread 6 August 2026
Video

《成都星辰百位新老师挂牌工作总结》(第6期)(编号:XC421-500) 为方便新进群友不盲目出击,对新老师有一个进一步了解,特推出月度老师总结(不一定刚好100位老师)⭐️ 综合友群或至少10个以上狼友反馈,排名在前列的有:(每项最多5个) 😍😍😍😍😍 颜值: #6p: #芊萌 @qianmende511,#无忧 @yycc7799 嫩妹(22以下): #6p:#婷婷 @TT2598q,#小琪大王 @yy502121,, #雨雨 @tm999911; #7p:#柠檬 @lyaassb , #可可 @kekekecd; 御姐(23-26): #6p: ,#小团子 @XTZ173z; #7p:#小丸子 @Wz05a ,#琪琪酱 @qqj028;#允恩 @yun05y #9p:#思念 @JudeRock 少妇服务: 高评分(8.8以上): #6p:#玲珑 @fe0288s ,#诗颖 @siingr, #盈盈

6👍2

1 Dec 2025, 05:52 UTC≈3,170 views1 reactionsread 6 August 2026

如何约课 1 车库选择中意老师,点车牌私聊 2 说明时间 地点 价格,直接可以约课 3 说明 星辰看到资料的,这样才有售后😎 注: 1 看老师一个月内有没有上线,一般没上线的要注意 2 一般不要定金,定金一般也不能超100 车库链接 :https://t.me/cdxcxrcku https://t.me/xingchenggl/123 #约课

1

24 Nov 2025, 06:35 UTC≈5,710 views0 reactionsread 6 August 2026
Photo

目前,成都星辰涉及的疑似天下色快餐诈骗案例,群已经提前赔付定金。后续款项会配合狼友追回。 还剩经费 1800 请注意定金赔付条件😓😓 大群打VIP,有相应条款

23 Nov 2025, 16:27 UTC≈15,300 viewsread 6 August 2026
Photo

【狼友定金赔付计划】 1 为保证狼友利益,打造安全上课氛围,星辰管理委员会特开启定金赔付专项款; 2 每人限额 100元/次,VIP用户150元/次; 3 每月专款 2000元; 4 符合条件; 赔付条件:🎓 1 有且只能有一个群名: 事前有提及:我是成都星辰群看到你的资料来约课的;(编辑后补无效); 2 所有老师和赞助商定金上限100元,超过上限狼友可以选择不去; 3 需提供完整交易记录、沟通截图等凭证 ; 4 欺诈行为经管理核查确认为真实 ; 5 仅限本群公示的认证老师,且最近一个月有上线记录。 经核实后,3天内会以口令或者u的形式发您🌈 最后: 每月基金虽然不多,愿这份保障让您更安心探索,也提醒大家交易时务必留存凭证,防患未然。👍👍👍 tips: 1 建议优先选择不要定金老师 2 不见真人,不结尾款🕯🕯 https://t.me/xingchenggl/120

23 Nov 2025, 13:23 UTC≈6,270 viewsread 6 August 2026
Photo

成都星辰已暂停天下色广告商合作,目前已有群友被骗案例。 待天下色处理好后,再恢复运行 希望星辰群友不要给定金,不要给定金,不要给定金。 重要的事情说3遍😡😡😡 1 定金不要超过100。 2 没见到人,坚决不给钱

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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

“成都星辰公告栏” (@xingchenggl), 1,120 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/xingchenggl.

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.