Telegram RegisterThe public register of Telegram
Telegram profile photo for 不要糖醋放椒盐

Channel

不要糖醋放椒盐

@saltplayerupdate

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

17,202subscribers

+182 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001404299449
TypeChannel
Username@saltplayerupdate
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/saltplayerupdate

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

17,02017,20217,1117 August 2026 — 17,020 subscribers7 August 2026 — 17,020 subscribers8 August 2026 — 17,026 subscribers9 August 2026 — 17,035 subscribers10 August 2026 — 17,046 subscribers11 August 2026 — 17,050 subscribers12 August 2026 — 17,052 subscribers13 August 2026 — 17,061 subscribers14 August 2026 — 17,064 subscribers15 August 2026 — 17,070 subscribers17 August 2026 — 17,068 subscribers18 August 2026 — 17,069 subscribers19 August 2026 — 17,076 subscribers20 August 2026 — 17,085 subscribers21 August 2026 — 17,087 subscribers22 August 2026 — 17,099 subscribers24 August 2026 — 17,102 subscribers25 August 2026 — 17,113 subscribers26 August 2026 — 17,119 subscribers27 August 2026 — 17,125 subscribers28 August 2026 — 17,123 subscribers29 August 2026 — 17,131 subscribers30 August 2026 — 17,134 subscribers31 August 2026 — 17,147 subscribers1 September 2026 — 17,159 subscribers2 September 2026 — 17,169 subscribers3 September 2026 — 17,171 subscribers5 September 2026 — 17,178 subscribers8 September 2026 — 17,197 subscribers11 September 2026 — 17,202 subscribers7 August 202611 September 2026
30 measurements spanning 35 days, net +182. 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 16,993–17,229 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
11 Sept 2026, 03:0117,202+5
8 Sept 2026, 07:3717,197+19
5 Sept 2026, 02:5617,178+7
3 Sept 2026, 09:3417,171+2
2 Sept 2026, 05:4317,169+10
1 Sept 2026, 08:1517,159+12
31 Aug 2026, 05:1317,147+13
30 Aug 2026, 05:3517,134+3
29 Aug 2026, 03:3817,131+8
28 Aug 2026, 05:1417,123-2
27 Aug 2026, 05:1717,125+6
26 Aug 2026, 04:4817,119+6
25 Aug 2026, 06:5217,113+11
24 Aug 2026, 08:5417,102+3
22 Aug 2026, 19:1317,099+12
21 Aug 2026, 11:5417,087+2
20 Aug 2026, 08:3617,085+9
19 Aug 2026, 07:2417,076+7
18 Aug 2026, 09:4817,069+1
17 Aug 2026, 10:5517,068first reading

Engagement

105 posts held, back to 1 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 54 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
22.8%
avg views ÷ 17,202 subscribers
Avg views / post
3,920
61 posts measured
Reaction rate
1.37%
reactions ÷ views · ER floor
Posts in window
62
of 105 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 September 2026
Posts held105 (1 August 20263 September 2026)
Views total239,163
Reactions total3,272
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 09:29 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.

What this channel posts

Video runtime
20s
Average length
10s

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.

Reaction mix

5,324 reactions across 101 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🎉5,324100.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 101 of the 105 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 5,324 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 105 most recent posts we hold, published 1 August 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.

Telegram Stars

Stars received
14
across the posts below
Posts paid on
10
of 101 we hold a reading for · 10%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @saltplayerupdate. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 105 most recent posts we hold for this entry, published 1 August 2026 to 3 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

3 Sept 2026, 07:20 UTC528 views15 reactionsread 3 September 2026

https://sj.qq.com/appdetail/com.salt.music 现已上线腾讯应用宝平台

🎉15

3 Sept 2026, 03:10 UTC≈1,170 views47 reactionsread 3 September 2026
Photo

整理图库,看到了一张 2020 年底在宿舍写 Dso Music 的照片......

🎉47

3 Sept 2026, 01:38 UTC≈1,310 views41 reactionsread 3 September 2026

糖醋音乐商标在手上,不能浪费了,搞点东西

🎉41

2 Sept 2026, 11:06 UTC≈2,030 views47 reactionsread 3 September 2026
File

12.3.1-release-2026090201 优化软件内存占用 修复 Salt Player 均衡器保存异常的问题

🎉47

1 Sept 2026, 09:42 UTC≈2,630 views59 reactionsread 3 September 2026

根据上游 Android 官方库,应该不久后 Salt Player minSDK 要升级到 24(Android 7)

🎉59

1 Sept 2026, 08:54 UTC≈2,630 views46 reactionsread 3 September 2026

Morvanium 设计的时候的智能更多考虑到的是过渡方式和实际,而非混音 但是收到了很多反馈希望更类似乐队编排,比如加些低频下潜这些 这边打算改一下,小作坊下料得猛一些

🎉46

1 Sept 2026, 08:42 UTC≈2,590 views38 reactionsread 3 September 2026

混淆配置写错了,均衡器保存存在问题,晚些会再发布一个版本 延期

🎉38

1 Sept 2026, 03:03 UTC≈2,940 views64 reactionsread 3 September 2026
File

12.3.0-release-2026090101 *对比 12.2.2 全新 Salt Player 均衡器(PRO) - 8000+ AutoEQ 配置参数 - 20+ 内置均衡预设 - 图形化,至高 32 段参数均衡器 - 支持自定义,导入导出 新增 Morvanium 智能过渡(Audiophile Pack 包) 新增迷你播放条至播放界面的封面过渡动画 新增支持播放队列拖拽排序歌曲 新增支持 FLAC ID3 标签头封面 新增歌词获取顺序调整(SPL、LRC、内嵌) 新增支持 .spl 拓展歌词文件 新增艺术家页面按数量排序的功能 新增专辑页面在年份排序显示快速滚动条 优化 USB 独占稳定性 优化歌曲扫描流程 优化 USB 独占音量进度条为 100 等级 优化侧边栏手势滚动处理 修复系统音量条无法控制 USB 独占音量的问题

🎉64

1 Sept 2026, 00:20 UTC≈2,950 views61 reactionsread 3 September 2026
Photo

早上打开酷安,我是不是没睡醒......

🎉61

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

Posts edited after publishing

@saltplayerupdate edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
2 September 2026
Most recent edit
2 September 2026

Forward network

Republished by

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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Nagram Tips
@NagramTips · 45,897
Telegram ranks this channel #28 of 49 here — alongside 48 others — read 30 August 2026
Legado|开源阅读|频道
@Legado_Channels · 92,960
Telegram ranks this channel #44 of 61 here — alongside 60 others — read 17 August 2026
Surfboard News
@surfboardnews · 28,405
Telegram ranks this channel #46 of 64 here — alongside 63 others — read 9 September 2026
LSPosed
@LSPosed · 192,028
Telegram ranks this channel #54 of 57 here — alongside 56 others — read 17 August 2026
Voyla 搜书 | 推书| 求书
@voyla · 89,649
Telegram ranks this channel #56 of 56 here — alongside 55 others — read 17 August 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“不要糖醋放椒盐” (@saltplayerupdate), 17,202 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/saltplayerupdate.

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.