Telegram RegisterThe public register of Telegram
Telegram profile photo for cymusic

Channel

cymusic

@gyc_123

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

3,579subscribers

-51 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002437384363
TypeChannel
Username@gyc_123
CreatedBetween 1 September 2024 and 28 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/gyc_123

Topic

Music — 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 14 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

3,5793,6333,6067 August 2026 — 3,630 subscribers8 August 2026 — 3,630 subscribers11 August 2026 — 3,628 subscribers15 August 2026 — 3,627 subscribers18 August 2026 — 3,629 subscribers21 August 2026 — 3,633 subscribers25 August 2026 — 3,631 subscribers27 August 2026 — 3,627 subscribers30 August 2026 — 3,628 subscribers2 September 2026 — 3,624 subscribers6 September 2026 — 3,619 subscribers11 September 2026 — 3,617 subscribers15 September 2026 — 3,609 subscribers19 September 2026 — 3,602 subscribers28 September 2026 — 3,588 subscribers6 October 2026 — 3,584 subscribers12 October 2026 — 3,579 subscribers7 August 202612 October 2026
17 measurements spanning 66 days, net -51. 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 3,571–3,641 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 19:073,579-5
6 Oct 2026, 02:393,584-4
28 Sept 2026, 19:383,588-14
19 Sept 2026, 02:383,602-7
15 Sept 2026, 01:203,609-8
11 Sept 2026, 09:563,617-2
6 Sept 2026, 09:213,619-5
2 Sept 2026, 11:343,624-4
30 Aug 2026, 17:243,628+1
27 Aug 2026, 22:443,627-4
25 Aug 2026, 04:243,631-2
21 Aug 2026, 13:493,633+4
18 Aug 2026, 07:223,629+2
15 Aug 2026, 12:283,627-1
11 Aug 2026, 14:433,628-2
8 Aug 2026, 11:463,630no change
7 Aug 2026, 15:013,630first reading

Engagement

18 posts held, back to 28 September 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 6 March 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

518 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 53.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤27853.7%
👍22743.8%
🥰71.35%
🍾30.579%
💔20.386%
😁10.193%

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 16 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 518 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 28 September 2024 to 6 March 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

6 Mar 2026, 14:13 UTC≈3,490 views31 reactionsread 7 August 2026
File

[refactor: 更新浅色和深色主题切换] [refactor: 优化性能]

👍27❤4

6 Mar 2026, 14:12 UTC≈3,110 views1 reactionsread 7 August 2026
File

[feat: 支持分享音源文件导入,支持 url和脚本导入] [feat: 添加歌词延迟控制功能,支持调整和重置歌词显示延迟]

❤1

4 Mar 2026, 04:33 UTC≈3,470 views30 reactionsread 7 August 2026
File

[feat: 支持导入洛雪音源] [feat: 添加音源测试功能,优化音源状态管理]

❤22👍8

10 Jan 2025, 09:06 UTC≈18,300 views69 reactionsread 7 August 2026
File

[feat: 搜索歌手和歌曲分開] [fix: APP启动图片不适配不同屏幕的机子] [fix:导入歌单输入栏被键盘遮挡] [fix:音源文件导入更新逻辑,如果第一次导入,则自动选择] 有什么建议或bug可以提issues。点点star🌟支持开发

❤63🥰6

9 Jan 2025, 11:17 UTC≈13,000 views29 reactionsread 7 August 2026
File

来自 https://github.com/gyc-12/Cymusic/issues/104 https://github.com/gyc-12/Cymusic/issues/103

❤28🥰1

1 Dec 2024, 10:55 UTC≈12,700 views50 reactionsread 7 August 2026
File

[feat: 遇到无高音质的音乐自动尝试切换低一级音质播放] [feat: 支持创建自定义歌单] [feat: 设置首页播放歌曲数量] [feat: 首页分页加载300 首] [fix: 部分国际化拼写错误] [fix:手动下载缓存路径错误导致读取不到本地缓存缓存歌曲后提示 #78 #81 ] 有什么建议或bug可以提issues。点点star🌟支持开发

❤41👍9

30 Nov 2024, 02:06 UTC≈10,400 views18 reactionsread 7 August 2026
File

来自 ikun 佬的分享,频道:@ikunshare_channel

👍12❤6

24 Nov 2024, 09:54 UTC≈9,830 views29 reactionsread 7 August 2026
File

[feat: 设置增加是否显示缓存图标] [feat: 增加已缓存歌曲标识issue: #70 ] [feat:部分弹窗提示改为Toast 提示] [fix: 搜索音乐会点不到第一首歌曲,issue: #60 ] 有什么建议或bug可以提issues。点点star🌟支持开发

👍22❤7

11 Nov 2024, 11:09 UTC≈9,630 views25 reactionsread 7 August 2026
File

出处(文件里面也写了),https://apii.lolimi.cn/ 可以支持大佬的收费 api

❤18👍4🍾3

7 Nov 2024, 11:14 UTC≈12,800 views26 reactionsread 7 August 2026
File

[chore: 电台-->广播] [fix: app位于后台时避免频繁Alert] [chore:doc] [feat: 点击正在播放曲目弹出播放界面] [fix: 部分机型搜索页面第一条不显示] 最近比较忙,更新慢,见谅。有什么建议或bug可以提issues。欢迎star🌟https://github.com/gyc-12/Cymusic

👍21❤5

20 Oct 2024, 01:55 UTC≈8,840 views29 reactionsread 7 August 2026
File

[fix: 一些List性能优化] [feat: 搜索页支持下滑翻页] [feat: 支持状态栏进度条拖动快进] [feat: 支持多语言(英语+中文)选择] [fix:下载按钮逻辑] [doc: readme] 注:1、新加了一个carplay支持分支,在xcode模拟器上测试能正常运行,但是打包出来手机上用不了,大概需要🍎付费开发者证书?暂时放弃了。2、欢迎star、pr

👍26❤3

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

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

“cymusic” (@gyc_123), 3,579 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/gyc_123.

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.