Впервые на ТО
custom 52244605345349161028🕊4custom 57804966944162486354custom 52219497353083763433👻2custom 52336015950353707361

Channel
@muzpr1ton
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
110subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002153372210 |
|---|---|
| Type | Channel |
| Username | @muzpr1ton |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/muzpr1ton |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 07:30 | 110 | no change |
| 7 Aug 2026, 17:54 | 110 | first reading |
16 posts held, back to 17 October 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 1 pageof 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 14 April 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 3 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.
333 reactions across 16 posts, in 12 distinct kinds. The most used accounts for 30.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5224460534534916102 | 100 | 30.0% | |
| 🏆 | 79 | 23.7% | |
| 👻 | 32 | 9.61% | |
| custom 5447367030799877537 | 24 | 7.21% | |
| custom 5211047849885710934 | 22 | 6.61% | |
| custom 5221949735308376343 | 16 | 4.80% | |
| custom 5780496694416248635 | 16 | 4.80% | |
| ⚡ | 12 | 3.60% | |
| custom 5314529245727307762 | 10 | 3.00% | |
| 🖕 | 10 | 3.00% | |
| custom 5233601595035370736 | 6 | 1.80% | |
| 🕊 | 6 | 1.80% |
Custom emoji. 7 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 areTelegram’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 16 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 333reactions 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 17 October 2025 to 14 April 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 @muzpr1ton. 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 17 October 2025 to 14 April 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.
Впервые на ТО
custom 52244605345349161028🕊4custom 57804966944162486354custom 52219497353083763433👻2custom 52336015950353707361
Video message, posted without a caption
custom 52244605345349161029custom 52219497353083763436custom 54473670307998775375👻1🖕1custom 52110478498857109341
Новогоднее поздравление президентов (народных избранников) шушарской демократической республики С наступающим, друзья. Оставайтесь с нами. Stay with us. Stay with Kryx!
🏆9custom 52244605345349161025custom 53145292457273077624custom 52336015950353707362👻1
Друзья, записал новый видос на Ютуб. Не кавер, так, чисто, практика соло. Любимый Яри, любимые Винтерсан Пожалуй, одно из самых сложных соло, что я вообще когда-либо играл ▶️ ЮТУБ
⚡8custom 52219497353083763436🏆5custom 52244605345349161021custom 54473670307998775371
Поистине легендарный человек собственной персоной сегодня прибыл в Санкт-Петербург. Не мог упустить такую возможность. Кто знает, тот знает)
🏆10custom 57804966944162486353🕊2
Друзья, я наконец-то нашел время и сделал новый кавер ▶️ ЮТУБ 📱 ИНСТА Я обожаю Джейсона Бэккера. Никогда не думал, что мне удастся сыграть его материал. Но сегодня сел и разобрал это. Держите)
🏆12custom 52244605345349161027custom 54473670307998775374🖕1
Слушайте, друзья. Пишите свои мысли. Мы делали это очень долго, сами знаете)
custom 522446053453491610213👻6🏆4⚡1🖕1
KryX - "Lost & Betrayed" (2025) Genre: Melodic death metal Music by: Артём Коган Mixing & Mastering: Андрей Клюшников, Артём Коган Cover by: Андрей Плескевич
custom 52244605345349161026custom 54473670307998775376🏆3
File, posted without a caption
custom 522446053453491610211🏆7👻6⚡2🖕1
Господа, у нас есть обложка на епишку. И даже задник. Но нужно много актива. Всё-таки, про альбом речь идёт уже очень давно ‼️Название EP - "Lost & Betrayed"‼️ Завтра мы сольем обложку. И дату релиза Давайте обеспечим много актива😇😇😇
custom 52110478498857109349custom 52244605345349161025🏆3🖕1custom 52219497353083763431custom 53145292457273077621
Ну, что, друзья. Вчера нам сделали обложку для епишки. Так что, все готово. Вообще все. Проделан огромный путь. Теперь осталось только выпустить, и всё. Я знаю, что кормил обещаниями много времени, но теперь уже точно релиз на носу. На днях объявим дату выпуска)
🏆13custom 52244605345349161026👻4🖕1custom 52336015950353707361
Наш новый логотип!!! Художник - Андрей Плескевич (В комментариях прикрепим ещё несколько вариантов, чтоб вы рассмотрели всякие разные версии)
custom 52244605345349161026🏆5👻4🖕1
Showing the 12 most recent of 16 posts we hold for @muzpr1ton. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“♪Музпритон𝄞” (@muzpr1ton), 110 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/muzpr1ton.
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.