Channel
@shibaiband
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Declared links · Cite this entry
35subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003756497033 |
|---|---|
| Type | Channel |
| Username | @shibaiband |
| Created | Between 1 February 2026 and 16 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/shibaiband |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 19:25 | 35 | -1 |
| 24 Aug 2026, 16:58 | 36 | +1 |
| 10 Aug 2026, 23:45 | 35 | no change |
| 8 Aug 2026, 10:06 | 35 | first reading |
19 posts held, back to 16 April 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 19 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 10 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.
97 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 59.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 58 | 59.8% | |
| ❤ | 18 | 18.6% | |
| 🍾 | 8 | 8.25% | |
| 🤣 | 7 | 7.22% | |
| 👏 | 3 | 3.09% | |
| 👍 | 2 | 2.06% | |
| ✍ | 1 | 1.03% |
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 18 of the 19 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 97 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 16 April 2026 to 4 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.
Новый трек наконец-то залили! 20 августа релиз Пресейв, чтобы не пропустить: https://band.link/shibai_3 Горят, что эти пресейвы помогают. Мы примерно поняли в каком направлении идём, поэтому уже задумываемся и об EP. Да и демо уже много накопилось
🔥4
Один трек полностью готов! Рад сообщить, что сведение - ВСЁ! На днях анонсируем Долго вышло, но зато по мере записи набросали ещё пару демо, а сам трек вышел даже злее, чем планировался
🔥8
Вокал и инструменты записаны на два трека. Сейчас дело осталось за сведением💀
❤3🔥2
Спасибо «Ушам в огне», уже во второй раз попали в народный плейлист.
Вы думаете трейлер новых Мстителей - это самое грандиозное событие лета? А вот и нет, ведь вышло обновление самого народного плейлиста ВСЕ СВОИ! В этот раз у нас целых два победителя - ЗАЧЕМ ДУША с песней "Тени" и "Чёрно белое" от УДМУРТСКАЯ ТОСКА. Поздравляем всей редакцией! Своими новинками поделились - 7EMPEST - Смотрители - марево - CHUPALAH - SHIBAI - Bleedwork - Astrosail - СДНХ - Ad Nihil - MAKAURI PIE - Joy…
👏3
Друзья, привет! Рад, что потихоньку канал растёт, спасибо, что подписались! Работа над следующими треками идёт активно, правда медленнее, чем хотелось бы. Пока мы в поиске себя и стараемся делать интересно. Поэтому если трек не работает для нас, то начинаем с нуля. Короче, не халтурим :) Два следующих трека мы уже выбрали, они в основном на стадии записи вокала, а инструментально почти готовы. Постараюсь наорать о…
❤3🔥3
Говорят, что Яндекс Музыка продвигает ИИАртистов, может и наш шелест нейроговна пропушит. Слушайте, распространяйте.
🤣7✍1
Друзья, мы так же приготовили и клип! Уже можно смотреть на Youtube: https://youtu.be/bLi6SK-_l50 https://youtu.be/bLi6SK-_l50 https://youtu.be/bLi6SK-_l50 Будем рады вашему просмотру и комментарию!
🔥7❤1
Shibai — Коллапс «Собери всю свою ярость» СЛУШАТЬ НА ВСЕХ ПЛОЩАДКАХ ПОДДЕРЖАТЬ ЛАЙКОМ, КОММЕНТАРИЕМ, РЕПОСТОМ
🍾8🔥3
До нового трека уже несколько дней! Пока хотел поделиться рецензией на МИМО от Ави Тяжело всегда слушать критику, но критика помогает расти над собой. Очень полезный отзыв, который помог при работе над следующим треком, так что Ави - спасибо!
🔥5
собери всю свою ты ярость «Коллапс» — 12 июня яростно делаем пресейв
❤4🔥2
С 12 июня нас ждет Коллапс Пресейв : https://band.link/colapse
🔥7
Showing the 12 most recent of 19 posts we hold for @shibaiband. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
2 URLs this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“SHIBAI” (@shibaiband), 35 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/shibaiband.
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.