Channel
@omutcore
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
99subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001871518486 |
|---|---|
| Type | Channel |
| Username | @omutcore |
| Description | Nu-Metalcore банда из Екатеринбурга |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/omutcore |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 11:02 | 99 | no change |
| 7 Aug 2026, 10:55 | 99 | first reading |
20 posts held, back to 1 August 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 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 20 posts for this entry, the most recent from 8 August 2025. 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 9 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.
240 reactions across 19 posts, in 11 distinct kinds. The most used accounts for 32.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 79 | 32.9% | |
| 🔥 | 54 | 22.5% | |
| custom 5319066444883828666 | 30 | 12.5% | |
| custom 5202146135027753003 | 22 | 9.17% | |
| custom 5460929352109661725 | 19 | 7.92% | |
| custom 5884152268361567570 | 13 | 5.42% | |
| custom 5217608395250485583 | 6 | 2.50% | |
| custom 5235640209852343235 | 5 | 2.08% | |
| custom 5456164124549454257 | 5 | 2.08% | |
| custom 5460994085856747166 | 4 | 1.67% | |
| custom 5237843575319829807 | 3 | 1.25% |
Custom emoji. 9 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 19 of the 20 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 240reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 1 August 2024 to 8 August 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Ровно год прошел с нашего последнего релиза «Не важно». Для нас это был большой шаг: съемка клипа с приглашенным артистом, смена звучания, новый стиль. Хотелось бы немного прервать тишину и отметить годовщину этого знакового для нас трека, гитарным плейтру от Лёши, которое снял @bxzlxv Ждете ли вы нашего возвращения? Напишите пару ласковых слов.
🔥9❤5custom 53190664448838286662custom 52176083952504855831
Posted without readable text
❤8🔥3custom 53190664448838286662custom 52176083952504855831
Год назад у ВИА ОМУТ и солиста эстрадно-рокового направления Юры Насоса вышла пластинка Союз - помним, гордимся? https://band.link/omutcore_union
🔥12
Сегодня День Рождения отмечает наш фронтмен aka передний чел - Саша За эти два года, мы вместе с ним прошли большой путь и стали семьей не только объединив участников группы, но и всех к ней причастных. А чтобы эта звездочка продолжала гореть для нас и вас, напишите ему пару приятных слов. 🖤
custom 53190664448838286669custom 54609293521096617255custom 58841522683615675705❤1🔥1
Соскучились? Мы тоже ☺️ Готовим для вас что-то новенькое 🙂
custom 520214613502775300311❤4custom 53190664448838286661custom 58841522683615675701
«Не важно» на НАШЕМ радио 🤘😎🤘
❤16🔥4custom 52176083952504855831custom 53190664448838286661
ОМУТ pinned a photo
Вы спасли Илью кстати, у него перестала гореть жопа 🤪
custom 58841522683615675707custom 53190664448838286662custom 54609293521096617251
По этому случаю кидаем еще один клип 🤨
custom 52021461350277530037❤1custom 52176083952504855831custom 54561641245494542571
Вы вообще видели цифры в Яндекс Музыке? 😳
custom 53190664448838286666🔥3custom 52176083952504855832custom 54561641245494542572
Video message, posted without a caption
❤5custom 54609940858567471664custom 52378435753198298073
Пока в ВК вышел формальный опрос, от своих хотелось бы послушать ваше РАЗВЕРНУТОЕ мнение, как вам наш трек "Не важно"? Прямо в комментарии можно написать, прямо не пожалеть абзац текста :) Тут можно переслушать на всякий, перед рецензией)
❤5
Showing the 12 most recent of 20 posts we hold for @omutcore. 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.
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.
“ОМУТ” (@omutcore), 99 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/omutcore.
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.