Тепер я волаю
😁50🔥2🤯1

Channel
@AlexKovalchukTg
On this record: Growth · Engagement · Reactions · Advertising · Posts · Citations · Cite this entry
1,164subscribers
+10 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001870278321 |
|---|---|
| Type | Channel |
| Username | @AlexKovalchukTg |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/AlexKovalchukTg |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 08:15 | 1,164 | +2 |
| 2 Sept 2026, 17:34 | 1,162 | +1 |
| 30 Aug 2026, 19:57 | 1,161 | +2 |
| 27 Aug 2026, 22:02 | 1,159 | -2 |
| 25 Aug 2026, 02:36 | 1,161 | +3 |
| 21 Aug 2026, 09:14 | 1,158 | -2 |
| 18 Aug 2026, 06:02 | 1,160 | +3 |
| 9 Aug 2026, 10:52 | 1,157 | +4 |
| 6 Aug 2026, 19:42 | 1,153 | -1 |
| 6 Aug 2026, 18:15 | 1,154 | no change |
| 6 Aug 2026, 18:04 | 1,154 | first reading |
16 posts held, back to 13 June 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 16 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
717 reactions across 16 posts, in 9 distinct kinds. The most used accounts for 32.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 235 | 32.8% | |
| 🤬 | 131 | 18.3% | |
| 💯 | 127 | 17.7% | |
| 👍 | 84 | 11.7% | |
| 🔥 | 49 | 6.83% | |
| ❤ | 42 | 5.86% | |
| 🫡 | 29 | 4.04% | |
| 😢 | 13 | 1.81% | |
| 🤯 | 7 | 0.976% |
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 717 reactions 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 13 June 2026 to 3 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 16 most recent posts we hold, published 13 June 2026 to 3 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Тепер я волаю
😁50🔥2🤯1
Ось так гої звичайні люди бачать AI розробників (вони праві)
😁28
Зараз готую відео про NotPetya і хочу трохи поекспериментувати з форматом, щоб це був не просто переказ статей з інтернету, а історія від людей, які були там. Якщо ви відбивали атаку, піднімали інфраструктуру після неї, працювали в компанії, яка постраждала, або просто маєте цікаву історію про ті події, напишіть мені на [email protected]. Коротко напишіть: • ким тоді були; • як саме стикнулись з NotPet…
👍14🔥10
Тут мені скинули пост Трухи, і я трішки підофігів За роки війни волонтер Сергій Стерненко став мільйонером. Війна буквально його вигодувала. Ще у 2021 році його дохід становив лише 1 766 грн. Уже в 2022-му він задекларував понад 18 млн грн, а за роки війни тільки його сукупний офіційний дохід перевищує 105 млн грн. Майже 99% цих коштів він отримав після 24 лютого 2022 року. Вдумайтесь тільки в ці цифри. Стерненко…
💯65👍4🤯3❤1
Ми маємо чітко зрозуміти і зафіксувати: після того як військові публічно заговорили про неадекватне управління ЗСУ з боку Олександра Сирського, ми не маємо права зупинятися і дозволити цій темі затихнути. Сирський несе персональну відповідальність за систему, яку він будує в армії. Штурмові полки, ситуація у 425-му полку «Скеля», свідчення про небойові смерті, побиття, катування і незаконне утримання людей,замовне в…
🫡29👍18🔥1
Кожне наступне рішення степінь їбанутості збільшує і збільшує Вибачте я в ахуї
🤬40😢11❤2👍1🔥1😁1
Це якийсь пиздець. Я вже кілька тижнів напрацьовував матеріал для великого фундаментального курсу про кібербезпеку. Там іронічною ниткою йшла фраза Федорова: «Роль кібербезпеки переоцінена». Але то була легка іронія, розуміючи поточні дії й досягнення. Саме відключення Starlink для орків дуже, дуже, дуже сильно допомогло. Цифровізація, ставка на нестандартні ходи й дрони всіх типів. Це все і допомагало, і вселяло н…
🤬46👍29💯15❤1😁1
Питання "як перейти в MilTech?" я чую частіше, ніж "як увійти в айті?" Бо заробляти багато грошей це непогано, але і русня сама себе не знищить. І більшість людей уже трохи розбираються в програмуванні, тому доволі легко могли б світчнутись. Але часто їм не вистачає розуміння того, як програми будуть жити всередині дронів, роботів та іншого заліза. Тому мої знайомі з Growth Factory запускають 3,5 місячну програму …
❤10👍8
Русня підери Я назад спатки
💯41❤15😁3👍1
Маленький спойлер про відео яке уже готую знімати (думаю в кінці тижня випущу)
😁33🔥3
Схоже в ai моделей зявляється новий бенчмарк потужності 😅
😁40❤4
Офіс уже майже майже готовий, скоро буде відео не на будівництві
🔥27👍1
Showing the 12 most recent of 16 posts we hold for @AlexKovalchukTg. 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.
Named by 1 registered channel — 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.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Алекс про усе” (@AlexKovalchukTg), 1,164 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/AlexKovalchukTg.
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.