Ги́кай - быть счастливым Новый сингл от Воронежских инди-рокеров. Энергичный и меланхоличный трек о тревожности бытия и стремлении к простому человеческому счастью. СЛУШАТЬ

Channel
ги́кай
@gikaiband
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
75subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002237439633 |
|---|---|
| Type | Channel |
| Username | @gikaiband |
| Description | гы |
| 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/gikaiband |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 21:15 | 75 | no change |
| 9 Aug 2026, 11:02 | 75 | first reading |
Engagement
11 posts held, back to 10 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 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 11 posts for this entry, the most recent from 15 June 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 58
- Videos
- 9
- Links
- 22
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.
- Video runtime
- 39s
- Average length
- 39s
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.
Reaction mix
78 reactions across 10 posts, in 11 distinct kinds. The most used accounts for 34.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 27 | 34.6% | |
| 🔥 | 16 | 20.5% | |
| 💔 | 8 | 10.3% | |
| custom 5217466996337165348 | 7 | 8.97% | |
| custom 5427232022252764138 | 7 | 8.97% | |
| ❤ | 5 | 6.41% | |
| ⚡ | 2 | 2.56% | |
| 🗿 | 2 | 2.56% | |
| 😁 | 2 | 2.56% | |
| 🍾 | 1 | 1.28% | |
| 🤪 | 1 | 1.28% |
Custom emoji. 2 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 10 of the 11 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 78reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 10 September 2025 to 15 June 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.
Recent posts
https://band.link/gikaibehappy
❤🔥7🔥3
Как было не трудно догадаться-выйдет песня "быть счастливым". Релиз запланирован на 12 июня! Пока ждём ссылочек на пресейв-вот вам грустный человечек!
❤🔥7🔥5
Привет, друзья! Мы снова здесь, и "не с пустыми руками". В начале июня выйдет сингл! Скоро обязательно расскажем подробнее о нëм и других планах на будущее! Стэй тунед.Би хэппи.
💔8❤🔥3🗿1
БЕЗОСТРЕЛКА в Воронеже 11/10 🎵ги́кай 🎵скандал 🎵Ломоносова Штрассе 🎵птица синица 🎵это электробус. КОТЕЛЬНАЯ Все фото в альбоме или на диске
custom 52174669963371653483custom 54272320222527641383🗿1
Гиг в Котельной уже сегодня! Играем первые, а так же мы сегодня трио с немного иным звуком! Всех ждём!
❤🔥6custom 52174669963371653484custom 54272320222527641384⚡1
Мы плавно приближаемся к завершению рабочей недели, поэтому самое время заняться планированием выходных! В субботу в стенах Котельной пройдёт БЕЗОСТРЕЛКА – шоукейс черноземного лейбла БЕЗОСТАЯ100. В этот вечер на сцене окажутся целых пять команд из разных городов: 🔴 это электробус. – инди-рок (Белгород → Москва) 🔴 птица синица – нойз-поп (Курск) 🔴 Ломоносова Штрассе – пост-рок (Курск) 🔴 скандал – инди-рок/брекзитко…
🔥2❤1🍾1
Уже в эту субботу встречаем делегацию из Курска в Котельной! https://vk.com/club232869864
❤2🔥2
Отправляемся с нашим шоукейсом по родным краям Черноземья 26/09 Курск, Скворечник птица синица Dozire reee eisheba 11/10 Воронеж, Котельная это электробус. птица синица Ломоносова Штрассе скандал ги́кай 12/10 Белгород, Смирись это электробус. Dozire Стельки park dubá republik disco БИЛЕТЫ
🔥2⚡1❤1
Video, posted without a caption
🔥2😁2🤪1
Первое мероприятие прошло отлично! Спасибо коллективам «-1», ги́кай, Питомник и истлело. за замечательные сеты, команде Котельной за профессионализм и, конечно же, каждому, кто посетил концерт, за поддержку. Мы рады, что вы провели этот классный вечер вместе с нами! Фотоотчёт уже доступен в альбоме и на диске, за снимки сердечно благодарим Максима Калинина 🌹 Увидимся совсем скоро, 4 октября, на следующем концерте …
❤🔥4❤1
Showing the 11 most recent of 11 posts we hold for @gikaiband. 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.
Citation-graph rank
Citation-graph rank — 1,071,149 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
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.
Mentions
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.
Names
Channels on the register whose handles appear in this channel's posts.
@kotelnaya_inc · 1,6443 postsБЕЗОСТАЯ100
@bezostaya100 · 2042 postsптица синица
@birdtitmouse · 1162 postsчто это?!
@electrobusband · 4302 postsломоносова штрассе
@lomonosovastreet · 1412 postsскандал
@scandalal · 1032 posts"СМИРИСЬ" бар 🌚
@cmirisoriginals · 1221 postСкворечник
@dkskvorechnik · 1,0551 postDOZIRE
@dozire_dozire · 1791 postистлело.
@istlelo · 471 postpark dubá 🎠
@parkduba · 581 postpitomnique archive
@pitomnique · 941 postреспублика дискотека
@republikdisco · 4111 postСтельки
@stelki46 · 1211 post
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“ги́кай” (@gikaiband), 75 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/gikaiband.
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.