Telegram RegisterThe public register of Telegram

Channel

ScanFactory News

@scanfactory

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,554subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001517843869
TypeChannel
Username@scanfactory
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/scanfactory

Growth

1,5541,5551,554.57 August 2026 — 1,555 subscribers8 August 2026 — 1,555 subscribers11 August 2026 — 1,554 subscribers7 August 202611 August 2026
3 measurements spanning 4 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 1,554–1,555 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 09:031,554-1
8 Aug 2026, 01:371,555no change
7 Aug 2026, 03:031,555first reading

Engagement

13 posts held, back to 14 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
15.0%
avg views ÷ 1,554 subscribers
Avg views / post
233
1 post measured
Reaction rate
15.5%
reactions ÷ views · ER floor
Posts in window
1
of 13 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 held13 (14 January 20267 August 2026)
Views total233
Reactions total36
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 18:06 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.

What this channel posts

Video runtime
5s
Average length
5s

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

451 reactions across 13 posts, in 20 distinct kinds. The most used accounts for 32.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥14532.2%
7416.4%
👍5812.9%
🤣5712.6%
❤‍🔥194.21%
🍾194.21%
112.44%
🤔112.44%
👏102.22%
🤩92.00%
👀61.33%
💅61.33%
👻51.11%
🤯51.11%
🦄51.11%
🌚30.665%
🌭30.665%
🤝30.665%
🕊10.222%
🫡10.222%

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

Measured over the 13 most recent posts we hold, published 14 January 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, 07:00 UTC233 views36 reactionsread 7 August 2026
Photo

Вот и завершился наш корпоратив на Байкале Не верится, что нас уже 50 человек. Мы все такие разные: 20 городов, разные поколения, разный опыт — и именно это многообразие, любопытство, и любовь к новому, нас и объединяет. Каждый из нас искал и нашел этот путь - самоотверженно вкладывать себя в нечто большее. Встречаться с трудностями, с готовностью их решать, расти и развиваться. Мы рады делиться с другими ценность

🔥208🍾6🤔2

16 Jun 2026, 08:06 UTC≈1,000 views40 reactionsread 7 August 2026
Photo

Photo, posted without a caption

🤣24👀6💅62🤯2

11 Jun 2026, 11:23 UTC≈1,430 views83 reactionsread 7 August 2026
Photo

Сначала тебя не замечают, потом смеются над тобой, затем борются с тобой Сравните два интерфейса, и сделайте выводы самостоятельно Мы видим «визуальную схожесть», и считаем это официальным признанием нашего технологического лидерства на российском рынке 🍾 К счастью, 👉 Мозги не продаются: можно купить чужую команду и срисовать пиксели, но нельзя купить наш дух, культуру и скорость развития. 👉 Архитектуру не повтор

🤣33👍24🍾13🤔8👻5

9 Jun 2026, 13:51 UTC971 views32 reactionsread 7 August 2026
Photo

🤝 Beeline Cloud запустил сервис Cloud VM на базе ScanFactory У клиентов Beeline Cloud появилась возможность использовать технологии ScanFactory для непрерывного сканирования и управления уязвимостями в облачной и локальной ИТ-инфраструктуре. На базе нашей платформы запущен новый сервис Beeline Cloud VM, который помогает: ✓ непрерывно отслеживать состояние защищенности инфраструктуры; ✓ сканировать как публичные, та

🔥18❤‍🔥8👏4🌚1🤯1

3 Jun 2026, 17:57 UTC934 views21 reactionsread 7 August 2026
Photo

3–5 июня встречаемся в Завидово на Jet Security Conference 2026. Ждем вас на стенде ScanFactory: покажем продукт, расскажем про карту атаки, ИИ и другие тренды в управлении уязвимостями. А еще у нас будет мерч — приходите забирать. До встречи на JSC 2026! 🤗

❤‍🔥11🔥6👏4

28 Apr 2026, 13:03 UTC≈1,190 views34 reactionsread 7 August 2026
Photo

ScanFactory на CISO-форуме 👀 Сегодня мы на площадке — рассказываем про продукт, делимся свежим исследованием по уязвимостям и раздаем мерч. Если вы здесь — обязательно заходите на стенд, пообщаемся😀

👍12🔥12🤩5🤝32

27 Apr 2026, 07:02 UTC≈1,060 views25 reactionsread 7 August 2026
Video

Команда ScanFactory проанализировала 246 проектов по оценке защищенности 125 компаний из 18 отраслей за 2022–2025 годы. Что в отчёте: - сформирован топ из 94 критических уязвимостей, характерных для атаки на российские организации - 53% уязвимостей — критического и высокого уровня риска, позволяющие осуществить недопустимое событие - более 70% уязвимостей — типовые ошибки со стороны ИТ-разработки: слабые пароли, оши

🔥1265🤯2

22 Apr 2026, 13:46 UTC972 views32 reactionsread 7 August 2026
Photo

Новая фича в ScanFactory VM: Карта Атаки Атакующий с ИИ завтра атакует вашу компанию. Сегодня вы открываете VM, и видите список уязвимостей. Что патчить прямо сейчас, чтобы не допустить инцидент? Мы добавили в ScanFactory VM фичу «Карта Атаки», которая ▪️показывает реальные цепочки, по которым пойдут атакующие ▪️подсказывает, как их перекрыть Как это работает? После сканирования система: ▪️ выявляет критичные акт

🔥1510🦄5👏1🤔1

14 Apr 2026, 10:13 UTC≈1,050 views32 reactionsread 7 August 2026
Photo

ИИ меняет правила игры в VM/EASM Провести атаку с помощью ИИ уже сейчас могут люди, не понимающие в ИБ. Достаточно одного промпта. Anthropic (лидирующий мировой ИИ) предупреждает: в ближайшие 2 года кибербезопасность кардинально изменится. Ключевое: 1. ИИ уже реверсит патчи, и пишет эксплойты → «есть публичный эксплойт» больше не ориентир 2. Объем уязвимостей, которые необходимо будет устранять, вырастет на порядо

🔥1886

24 Mar 2026, 12:00 UTC≈1,190 views14 reactionsread 7 August 2026

🎉 Розыгрыш завершен! 🏆 Победители: 1. @iNeoo 2. @OlegFrontend 3. @BoykoDvach 4. @eshagashik 5. @mark_ae 🔍 Проверить результаты

9🔥5

17 Mar 2026, 12:00 UTC≈1,410 views34 reactionsread 7 August 2026
Photo

🤝 Первый розыгрыш в канале ScanFactory Нас уже 1000 подписчиков, и мы хотим отметить это вместе с вами. Разыгрываем 5 футболок ScanFactory среди наших подписчиков. Что нужно сделать: 1⃣ Быть подписанным на канал 2⃣ Нажать кнопку «Участвовать» Через неделю случайным образом выберем 5 победителей. Спасибо, что вы с нами 🖖

🔥197👍6👏1🕊1

23 Jan 2026, 12:03 UTC≈2,070 views32 reactionsread 7 August 2026
Photo

🖖Гайд для пентестеров: запускаем фишинговую рассылку через GoPhish Запустить реалистичную фишинговую рассылку с высоким Inbox Rate - задача не для новичков. Команда ScanFactory дружественным понятным языком написала статьи, чтобы даже начинающий пентестер смог разобраться настроить и запустить реалистичную фишинговую кампанию. 1⃣ Установка GoPhish на VPS 2⃣ Настройка почтового сервера и SPF/DKIM/DMARC 3⃣ Создани

13👍11🤩4🌚2🔥2

Showing the 12 most recent of 13 posts we hold for @scanfactory. 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 — 118,800 of 1,160,990entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 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.

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.

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

“ScanFactory News” (@scanfactory), 1,554 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/scanfactory.

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.