22 measurements spanning 23 days, net -165. 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 21,167–21,382 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)
Subscribers
Change
30 Aug 2026, 18:46
21,192
-10
29 Aug 2026, 15:24
21,202
+6
28 Aug 2026, 12:38
21,196
-7
27 Aug 2026, 15:25
21,203
-1
26 Aug 2026, 18:03
21,204
-13
25 Aug 2026, 15:53
21,217
-26
24 Aug 2026, 15:16
21,243
-38
22 Aug 2026, 23:22
21,281
-6
21 Aug 2026, 13:18
21,287
+5
20 Aug 2026, 11:22
21,282
+2
19 Aug 2026, 11:46
21,280
+6
18 Aug 2026, 12:55
21,274
+3
17 Aug 2026, 10:33
21,271
-17
15 Aug 2026, 16:28
21,288
-1
14 Aug 2026, 01:08
21,289
-7
12 Aug 2026, 17:03
21,296
-18
11 Aug 2026, 15:31
21,314
-14
10 Aug 2026, 17:37
21,328
-12
9 Aug 2026, 19:55
21,340
-4
8 Aug 2026, 23:30
21,344
first reading
Engagement
21 posts held, back to 3 September 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 48 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
11.4%
avg views ÷ 21,192 subscribers
Avg views / post
2,410
1 post measured
Reaction rate
3.20%
reactions ÷ views · ER floor
Posts in window
1
of 21 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
Window
Rolling 30 days · latest post in window 22 August 2026
Posts held
21 (3 September 2025 – 22 August 2026)
Views total
2,410
Reactions total
77
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
30 Aug 2026, 10:37 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
1,269 reactions across 19 posts, in 17 distinct kinds. The most used accounts for 59.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
751
59.2%
👍
230
18.1%
👏
127
10.0%
🔥
77
6.07%
🫡
15
1.18%
😁
13
1.02%
🤯
10
0.788%
👌
8
0.63%
😢
8
0.63%
😎
7
0.552%
🥰
6
0.473%
❤🔥
5
0.394%
🗿
5
0.394%
☃
3
0.236%
🙏
2
0.158%
⚡
1
0.079%
🕊
1
0.079%
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 19 of the 21 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 1,269reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 3 September 2025 to 22 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.
I am currently on a planned vacation and I just got to know, the yt repo is having issues, I will check and see what is the issue in next few days, please allow me sometime.
Update (28 Aug):
I am actively working on this now
Rather than a quick dirty fix, I am gonna take some time and release a new build with more core fixes and improvements so it works and keeps on working in the longer term along with many more q…
Quiet for months. Head down, Building.
> 330 commits. 2,519 files, +198k / -76k Lines of Code, above screenshot.
You can probably work out the rest.
Just a sneak peak, still a lot of things to do, no hard ETA, but soon™.
Stay Tuned!
Seems it was a gitlab issue, since our extensions are hosted there,
Although I will be migrating away, but I think the extensions are loading now, please check.
Whatever happened on their end got fixed for now, will be doing the migration in coming days.
Windows Fixed Release v2.0.6 was released in morning, forgot to mention here, do test it out, should work now:
https://github.com/Shabinder/soundbound-extensions-lib/releases/download/2.0.6-windows/Soundbound-2.0.6.msi
[BETA] v2.0.6 Desktop Release:
I was able to test the macOS arm64 DMG, but not the windows and linux releases after updating and refactoring a lot of the things, since I didn't had a desktop handy, please try out, and lemme know if the release works on said platforms.
https://github.com/Shabinder/soundbound-extensions-lib/releases/tag/2.0.6
Sources v0.29.43 Released:
- Spotify Extension fixes for a few failing links, and missing album image and tags.
- If anything else is missed / not working, do lemme know.
- I am now working on the Desktop Release, making equalizer and in-app browser related changes, hence taking a little while.
Thanks, for staying tuned.
🎧 Soundbound v2.0.5 Release
Changelog:
- Update now available for Android.
- Soon an update for Windows, Linux, and MacOS in a few days!
- Brand New 11 band in-app equalizer for Android.
- Many Many fixes and improvements across player, if still errors, try queue clear or a perhaps a clean install might help in rare cases.
I’m incredibly grateful for all the love and support you folks show! and I sincerely apologiz…
v0.26.38 Sources released, fixes not fetching more than 50 tracks.
Let me know if it works now.
You might need to reopen the platform link and favourite / save it again.
Guys just pushed and released v0.26.37 Sources, should fix ongoing issues and errors majorly.
Please check, do make sure to let the extensions update.
Thanks for staying tuned, life has been keeping too busy this year start.
❤60👍14🔥10😁2🙏2
Showing the 12 most recent of 21 posts we hold for @soundboundofficial. 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
@soundboundofficial edited 1 post 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
28 August 2026
Most recent edit
28 August 2026
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 30 August 2026 — this
entry's latest reading, not the date you are reading this.
“Soundbound official” (@soundboundofficial), 21,192 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/soundboundofficial.
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.