Telegram RegisterThe public register of Telegram
Telegram profile photo for АК-ВС 3 | Анализатор кода

Channel

АК-ВС 3 | Анализатор кода

@AK_BC_3

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

229subscribers

-1 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-1002588991523
TypeChannel
Username@AK_BC_3
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/AK_BC_3

Growth

229230229.57 August 2026 — 230 subscribers8 August 2026 — 230 subscribers22 August 2026 — 229 subscribers7 August 202622 August 2026
3 measurements spanning 15 days, net -1. 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 229–230 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 23:36229-1
8 Aug 2026, 10:15230no change
7 Aug 2026, 18:53230first reading

Engagement

11 posts held, back to 6 July 2026the 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.

ERR · 30 days
35.0%
avg views ÷ 229 subscribers
Avg views / post
80.3
4 posts measured
Reaction rate
8.72%
reactions ÷ views · ER floor
Posts in window
4
of 11 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held11 (6 July 20267 August 2026)
Views total321
Reactions total28
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 10:15 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

79 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 24.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54677396283478891301924.1%
custom 54653643138647064621822.8%
custom 54677973913630517621721.5%
custom 54677751906771010691620.3%
custom 546525641140132684867.59%
custom 546754434906983792033.80%

Custom emoji. Every row above is a 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 8 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 79reactions 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 6 July 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, 09:41 UTC46 views4 reactionsread 8 August 2026

Posted without readable text

custom 54677751906771010694

3 Aug 2026, 11:17 UTC77 views9 reactionsread 8 August 2026
Photo

➡️XSS в HTML-отчёте - это опасно? Обычно XSS ассоциируется с веб-сайтами. Но похожая проблема может появиться и в десктопном приложении, если оно формирует HTML-отчёт. Например, в отчёт попадают названия файлов, имена пользователей, комментарии или другие внешние данные. Если вставить их в HTML без экранирования, злоумышленник может подложить значение, которое станет не текстом, а исполняемым скриптом. Если отчёт

custom 54653643138647064624custom 54652564114013268483custom 54677396283478891302

31 Jul 2026, 09:23 UTC98 views2 reactionsread 8 August 2026

Posted without readable text

custom 54652564114013268482

29 Jul 2026, 11:10 UTC100 views13 reactionsread 8 August 2026
Photo

100 некритичных дефектов или один критичный?🤔 Когда в отчёте много найденных дефектов обычно складывается впечатление, что всё плохо Нашли 150 дефектов - продукт небезопасен. Нашли 5 дефектов - серьезных проблем нет. ✔️Но только количество само по себе мало что говорит. Представим два отчёта. В первом - 100 некритичных дефектов. Например, часть сообщений об ошибках сформулирована неудачно, а в отдельных местах со

custom 54677396283478891305custom 54677751906771010694custom 54675443490698379203custom 54653643138647064621

27 Jul 2026, 09:01 UTC≈1,180 views14 reactionsread 8 August 2026
Photo

Рады сообщить о выходе обновления CAT 1.0.2😎 В новой версии мы расширили функциональные возможности системы, а также повысили удобство и стабильность её работы. 🔥Ключевые изменения: 〰️улучшен механизм композиционного анализа; 〰️реализован итеративный анализ с возможностью повторной проверки SBOM-файла после обновления баз данных уязвимостей; 〰️добавлена автоматическая разметка срабатываний; 〰️расширены возможно

custom 54677396283478891306custom 54677751906771010694custom 54653643138647064623custom 54652564114013268481

20 Jul 2026, 10:49 UTC141 views11 reactionsread 8 August 2026
Photo

Одна строка - разные CWE?

custom 54677973913630517625custom 54677751906771010694custom 54653643138647064621custom 54677396283478891301

13 Jul 2026, 11:17 UTC156 views14 reactionsread 8 August 2026
Photo

✖️CWE добрался до AI AI/ML всё чаще становится частью ПО. Модель может распознавать изображение, генерировать текст, помогать пользователю, анализировать данные или участвовать в принятии решения. Теперь это появилось и в CWE. В версии CWE 4.20 добавили три элемента, связанные с AI/ML. 〰️CWE-1446 Категория недостатков, специфичных для AI/ML-технологий. В неё входят недостатки, которые возникают при интеграции AI

custom 54653643138647064626custom 54677396283478891305custom 54677973913630517623

6 Jul 2026, 10:58 UTC171 views12 reactionsread 8 August 2026
Photo

Почему временные файлы могут быть опасны?🤔

custom 54677973913630517629custom 54653643138647064623

Showing the 11 most recent of 11 posts we hold for @AK_BC_3. 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.

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

“АК-ВС 3 | Анализатор кода” (@AK_BC_3), 229 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/AK_BC_3.

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.