Telegram RegisterThe public register of Telegram
Telegram profile photo for Балака Aelnis`а

Channel

Балака Aelnis`а

@balakaelnisa

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

380subscribers

+21 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001621151098
TypeChannel
Username@balakaelnisa
Created13 November 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live17 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/balakaelnisa

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

3583803697 August 2026 — 359 subscribers8 August 2026 — 359 subscribers8 August 2026 — 358 subscribers15 August 2026 — 361 subscribers24 August 2026 — 366 subscribers1 September 2026 — 371 subscribers9 September 2026 — 377 subscribers17 September 2026 — 380 subscribers7 August 202617 September 2026
8 measurements spanning 40 days, net +21. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 355–383 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 03:00380+3
9 Sept 2026, 11:00377+6
1 Sept 2026, 03:07371+5
24 Aug 2026, 04:13366+5
15 Aug 2026, 16:48361+3
8 Aug 2026, 13:33358-1
8 Aug 2026, 06:34359no change
7 Aug 2026, 19:47359first reading

Engagement

17 posts held, back to 5 August 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 17 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

46 reactions across 17 posts, in 4 distinct kinds. The most used accounts for 91.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4291.3%
👍24.35%
🌚12.17%
🤯12.17%

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 17 of the 17 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 46 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 5 August 2026 to 7 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.

Recent posts

7 Aug 2026, 23:46 UTC85 views3 reactionsread 8 August 2026

Team Lynx спокійно закривають третю мапу і проходять у наступний раунд верхньої сітки. Ми їх побачимо уже завтра о 21:00 в матчі проти lvlup. А PuckChamp зустрінуться проти fts в рамках зустрічі на виліт о 15:00

❤2🤯1

7 Aug 2026, 23:46 UTC76 views4 reactionsread 8 August 2026
Forwarded from @teamlynxuaPhoto

Є ПЕРЕМОГА!🔥 У напруженій серії переграємо😈PuckChamp з рахунком 2-1 та забираємо наш перший матч у плей-оф ASGARD CHAMPIONSHIP🏆 Продовжуємо боротьбу за чемпіонство. Дякуємо всім, хто вболівав та підтримував нас до останнього! 🐾 Рухаємось далі по сітці! Ваші Team Lynx 🇺🇦💚 📸 Instagram | 📹 Youtube | 🕺 TikTok

❤2👍2

7 Aug 2026, 22:49 UTC99 views3 reactionsread 8 August 2026
Photo

Друга мапа absolute cimema І все ж зрівняли рахунок Team Lynx. Очікуємо третю вирішальну. Тут теж Енігма для Кроляша і тепер навіть сейву немає у Lynx. Скажу що драфт знову за PuckChamp!

❤3

7 Aug 2026, 21:22 UTC119 views2 reactionsread 8 August 2026
Photo

Забирають собі першу мапу PuckChamp. Будемо дивитись що на другій буде. Поки драфт виглядає краще у Radiant знову. Не вірю в Аліхіміка

❤2

7 Aug 2026, 20:12 UTC140 views3 reactionsread 8 August 2026
Photo

Драфти першої мапи. Поки драфт краще у Пакчемпів. Комба Ларго+Ембер, є чим ловити Пака тобто ульта Гріма і в опонента жодного спелу проти Енігми. Та ще й Кез б'є Тайда на лінії

❤3

7 Aug 2026, 19:51 UTC84 views4 reactionsread 8 August 2026
Forwarded from @bafikkPhoto

Відкриваємо новий дружній збір! Хлопці збирають кошти на доукомплектування важливими засобами козаків, які боронитимуть наше небо від ворожих «пташок» і «шахедів». Підрозділ непублічний, тому після збору вони закуплять все необхідне і обов’язково нададуть фото- та відеозвіт. А згодом результати їхньої роботи ви побачите у публікаціях. Прохання підтримати — кожна гривня наближає чисте небо над Україною. Дякуємо за до…

❤4

7 Aug 2026, 19:44 UTC149 views2 reactionsread 8 August 2026

Почалась гра! Через 15 хвилин будемо дивитись, поки заходьте на стрім!

❤2

7 Aug 2026, 18:58 UTC167 views3 reactionsread 8 August 2026
Photo

Якщо комусь цікаво чому матч затримується. То ситуація в попередньому матчі на даний момент наступна:

❤3

7 Aug 2026, 07:52 UTC195 views2 reactionsread 8 August 2026
Photo

Друзі, сьогодні починаємо дивитись за плей-оф Asgard Championship Season 1 О ⌛️21:00 🇺🇦PuckChamp vs. 🇺🇦Team Lynx ℹ️Bo3 📺Стрім тут📺

❤2

6 Aug 2026, 06:31 UTC211 views6 reactionsread 8 August 2026
Photo

В доту додали Theasure of the Crimson Witness 2026 Як вам сети?

❤5🌚1

5 Aug 2026, 20:47 UTC138 views2 reactionsread 8 August 2026
Forwarded from @teamlynxuaPhoto

На жаль, завершуємо останню серію з рахунком 0-2 😔 За підсумками першого етапу 🏆ASGARD CHAMPIONSHIP посідаємо друге місце у групі B🔥 Дякуємо всім, хто підтримував нас протягом цих матчів. Далі буде ще більше Доти! Слідкуйте за анонсами 🐾 Побачимось вже у плей-оф. Ваші Team Lynx 🇺🇦💚 📸 Instagram | 📹 Youtube | 🕺 TikTok

❤2

5 Aug 2026, 19:59 UTC200 views1 reactionsread 8 August 2026
Photo

Програють Team Lynx першу мапу. Але на другій їм віддають Лд і гріх таким шансом на камбек не скористатись. Та ще й сігнатурний Сенд Кінг для Mellojul.

❤1

Showing the 12 most recent of 17 posts we hold for @balakaelnisa. 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.

Forward network

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.

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.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Балака Aelnis`а” (@balakaelnisa), 380 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/balakaelnisa.

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.