Channel
@sunrow_music
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
309subscribers
+11 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002142669065 |
|---|---|
| Type | Channel |
| Username | @sunrow_music |
| Created | Between 1 December 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/sunrow_music |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 13:59 | 309 | +1 |
| 29 Aug 2026, 03:02 | 308 | +3 |
| 22 Aug 2026, 16:28 | 305 | +3 |
| 15 Aug 2026, 16:55 | 302 | +4 |
| 8 Aug 2026, 08:04 | 298 | no change |
| 7 Aug 2026, 17:54 | 298 | first reading |
16 posts held, back to 11 June 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 22 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
92 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 29.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5458908492687497206 | 27 | 29.3% | |
| custom 5213333038775151099 | 18 | 19.6% | |
| custom 5197585682918286193 | 11 | 12.0% | |
| custom 5217608395250485583 | 8 | 8.70% | |
| 🤪 | 7 | 7.61% | |
| 😍 | 6 | 6.52% | |
| 🦄 | 5 | 5.43% | |
| 🤯 | 4 | 4.35% | |
| 😭 | 3 | 3.26% | |
| 😱 | 3 | 3.26% |
Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 15 of the 16 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 92 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 11 June 2026 to 22 July 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @sunrow_music. 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 16 most recent posts we hold for this entry, published 11 June 2026 to 22 July 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.
о, яндекс таки вводит маркировку ИИ треков. вопрос лишь в том, что основываясь на указании автора и дистрибьютора при публикации) ну типо я могу нагенерить херни и скзаать что сам сделал, а там уже какая разница, главное что все будут видеть, что треки "не ИИ" ☺️ вообще есть мысль что надо "ИИ тайп биты" делать)
🤪4custom 51975856829182861932
смарите штука прикольная какая: можно интересную ритмику получить, если управлять осцилятором(ами) через другой с семплом чего угодно (тут луп перкуссионный) 🥳 просто саму оську перетягиваешь на громкость или что нужно и по ней автоматизируется (главное в матрице поставить что-то около (второй скрин), чтобы срабатывало ток на пиках, и не проскальзывало в тишине. в коментах пресетик скинул - поиграйтесь, покрутите чег…
custom 52133330387751510995custom 54589084926874972063😍1
первый бас это с начала такта каждого из видео выше. оба из видоса в ТТ, который сегодня выйдет 🥳 там макросики покрутить, автоматизировать и будет конфетка #vidsamples
custom 54589084926874972065custom 52133330387751510991custom 52176083952504855831
Video, posted without a caption
custom 54589084926874972063custom 52176083952504855832custom 52133330387751510991
Вот кстати накрутил, спасибо технике с поста выше, проект доделаю и залью. В целом тут каждый звук мой, включая драмки 👀 Бтв почти 2 луфса 😳
🤪3
ой, а если еще и фазы смешивать. и автоматизацию по положению фазы при этом делать...😩
в общем! если даже базовую синусоиду модулировать от любой волны (я чет нарисовал сам) с дсоффсетом (в данном случае с полунулевой волной ) очень интересные текстуры получаются. дальше уже можно играться разными волнами, и выводить полностью вторую волну, но только в плюс или минус - будет только интереснее. это так интересно происходит, потому что базово у синусоиды низкая частота, а модулируем мы от высокочастотн…
😱3
Я ж тут диджею на выпускных и свадьбах летом обычно, и вот что хочу сказать: не так сильно меня напрягает то, что люди заказывают ИИ музыку, а то, что они понимают, что это иишка. То есть челы подходят и такие "поставь вот этот трек, плиз, это иишка, но трек крутой" В итоге имеем, что среднестатистический человек вообще не парится ИИ это или реальный исполнитель, а стриминги не парясь пихают их в чарты и рекомендации…
😭3custom 51975856829182861932🤯1
вот собственно и пресетик! не забудьте клиппер в обработке и подрезать чуток верха 🥳 в коменты скину еще советик к концу недели проект немног доделаю и тоже закину
custom 52133330387751510994custom 54589084926874972063custom 52176083952504855831
скриллекс крутой, кстати
custom 54589084926874972065custom 51975856829182861932
Video message, posted without a caption
😍4custom 52176083952504855833🦄2
У лиздека альбом плотный такой вышел, что уже необычно для электрощиков, ибо все привыкли синглами. Но он ещё и мощный и очень жанрово разнообразный, - рекомендую! Но, драмнбаса нет, конечно 💥
custom 51975856829182861931
Showing the 12 most recent of 16 posts we hold for @sunrow_music. 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.
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“Sunrow на связи 🤪” (@sunrow_music), 309 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/sunrow_music.
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.