Telegram RegisterThe public register of Telegram

Channel

Солар

@solar_security

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

6,529subscribers

-2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001541351706
TypeChannel
Username@solar_security
Created25 February 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/solar_security

Growth

6,5276,5356,5316 August 2026 — 6,531 subscribers6 August 2026 — 6,535 subscribers9 August 2026 — 6,527 subscribers12 August 2026 — 6,529 subscribers6,5296 August 202612 August 2026
4 measurements spanning 6 days, net -2. 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 6,526–6,536 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 11:066,529+2
9 Aug 2026, 16:316,527-8
6 Aug 2026, 19:306,535+4
6 Aug 2026, 03:326,531first reading

Engagement

11 posts held, back to 14 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 9 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
16.6%
avg views ÷ 6,529 subscribers
Avg views / post
1,080
11 posts measured
Reaction rate
1.34%
reactions ÷ views · ER floor
Posts in window
11
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 11 August 2026
Posts held11 (14 July 202611 August 2026)
Views total11,912
Reactions total160
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:05 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
2m 06s
Average length
2m 06s

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

142 reactions across 10 posts, in 14 distinct kinds. The most used accounts for 29.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4229.6%
🔥2618.3%
👍1611.3%
custom 5195001937967200137149.86%
😎149.86%
👀85.63%
😐74.93%
😁42.82%
😈32.11%
21.41%
👌21.41%
👾21.41%
💯10.704%
🫡10.704%

Custom emoji. One 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 count beside it isTelegram’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 11 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 160reactions 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 14 July 2026 to 11 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

11 Aug 2026, 13:13 UTC421 views8 reactionsread 12 August 2026
Photo

👽 SIEM, который работает быстро: Solar SIEM 2026.2 Даже опытной команде SOC может не хватать времени и ресурсов на мониторинг инцидентов. Solar SIEM помогает снизить нагрузку на специалистов ИБ и кратно увеличить эффективность их работы. Решение автоматизирует до 90% рутинных задач: 1️⃣ Анализирует информацию о событиях информационной безопасности. 2️⃣ Выявляет инциденты. 3️⃣ Устраняет угрозы по заданному сценарию.

custom 519500193796720013751👍1🫡1

6 Aug 2026, 12:52 UTC861 views25 reactionsread 12 August 2026
Photo

💣 Хакеры пишут малвари с помощью ИИ Авторы стилера XillenStealer активно пользуются ИИ при разработке. Аналитики Solar 4RAYS нашли в коде вредоноса следы нейросети: недописанные функции, странные названия и фрагменты промптов. Найдите эти признаки самостоятельно — подсказки оставили в карточках 👀 А о том, как злоумышленники планируют атаки с ИИ, рассказали в полном материале.

👍10👀5😎53🔥2

5 Aug 2026, 10:51 UTC830 views26 reactionsread 12 August 2026
Photo

😳 Зачем нам фиды, если уже есть SIEM Даже самой мощной SIEM нужны актуальные данные об угрозах. Иначе событий много, а какие из них требуют внимания прямо сейчас, не всегда понятно. Solar TI Feeds усиливает SIEM: 1️⃣ предоставляет полную картину угрозы; 2️⃣ позволяет приоритизировать реагирование на события; 3️⃣ передает sigma-правила для обнаружения хакерских инструментов и аномалий. В сервис поступают данные Це

😎9😐65😈3👌2👀1

4 Aug 2026, 10:03 UTC830 views12 reactionsread 12 August 2026
Photo

✅ Защита нужна не только внутри компании, но и снаружи В 2025 году объем утечек данных из российских компаний вырос в 90 раз, а число фишинговых сайтов — в 1,5 раза. Злоумышленники продолжают усложнять схемы атак, в том числе с помощью ИИ. Самостоятельно противодействовать этому сложно: нужно вручную мониторить источники и блокировать фишинговые ресурсы. Solar AURA закрывает эти задачи. До 30 ноября действует спец

7👀2👍2😐1

30 Jul 2026, 13:06 UTC≈1,180 views5 reactionsread 12 August 2026
Photo

✅ Аттестация по приказу № 117: как пройти проверку и не потерять бюджет С 1 марта 2026 года действует приказ ФСТЭК № 117. Он требует контролировать, как в компании передаются данные ограниченного доступа — в том числе с помощью DLP-систем. Пункты 30а и 40 говорят прямо: нужно исключить любую незаконную передачу информации — через почту, мессенджеры, флешки, облака и другие каналы. На аттестации проверяют не докумен

👍3🔥1😁1

29 Jul 2026, 16:01 UTC≈1,230 views4 reactionsread 12 August 2026
Video

💣 Ваша ИБ-команда тонет в алертах, а SOC перегружен расследованиями? Solar DNS RADAR анализирует весь DNS‑трафик, распознаёт фишинг, видит связи с вредоносными доменами, C2‑серверами и блокирует опасные запросы. В видео рассказываем, как решение встраивается в вашу архитектуру, какие сценарии закрывает и как помогает снизить нагрузку на SOC и MSSP.

4

22 Jul 2026, 12:31 UTC≈1,570 views14 reactionsread 12 August 2026
Photo

Мы вовсю исследуем ИИ-угрозы, пока роботы за нас сочиняют симфонии ❤️ В этот раз вместе с УЦСБ выяснили, как часто в российских компаниях фиксируют ИИ-утечки. А главное — чего не хватает бизнесу для безопасной работы с ИИ. Собрали главное в карточках. А полную версию исследования читайте тут.

7🔥4custom 51950019379672001373

20 Jul 2026, 13:52 UTC≈1,280 views27 reactionsread 10 August 2026
Video

Кто на самом деле стоит за кибератакой Часто это конкретная группировка со своими инструментами и историей атак. Например, эксперты в Solar 4RAYS исследуют активность Shedding Zmiy. Данные по кибератакам помогают аналитикам быстрее отличать ложные тревоги от реальных угроз. Solar TI Feeds сокращает этот путь Истории об угрозах ежедневно загружаются в системы защиты. Если событие связано с опасным индикатором, анал

🔥118custom 51950019379672001376👾2

17 Jul 2026, 09:35 UTC≈1,390 views13 reactionsread 10 August 2026
Photo

Воркслоп — новая проблема эпохи ИИ Это контент, который сгенерировал ИИ: выглядит убедительно, но не решает задачу. Отчеты без выводов, презентации без смысла, код без контекста. 👀 По данным Harvard Business Review, 40% сотрудников получают такой контент от коллег. На его разбор уходит почти два часа. Есть и другая проблема. Чтобы получить ответ от нейросети, сотрудники загружают в нее договоры, клиентские данные,

🔥7😁32💯1

16 Jul 2026, 14:45 UTC≈1,270 views8 reactionsread 10 August 2026
Photo

Логин и пароль сотрудника утекли в сеть. Нас теперь взломают, да?.. Нет, если вы вовремя заметите злоумышленника. В Solar inRights 3.11 для этого появилась интеграция с Solar AURA. В карточках показываем, как работает DRP-интеграция и что еще нового в Solar inRights.

52🔥1

14 Jul 2026, 14:40 UTC≈1,050 views18 reactionsread 6 August 2026
Photo

Разбудите их среди ночи — и они расскажут все про автоматизацию безопасной разработки и ее эффект для бизнеса. Это мы про наших коллег из Hexway ASOC (входит в ГК «Солар»). Передаем микрофон им! А пока признавайтесь. Как у вас дела с разработкой? 🔥 — Я вижу огни. Так горят дедлайны по проектам. ❤️ — Все успеваем, даже ни разу не переносили сроки! 👍 — Какой разработкой?...

Showing the 11 most recent of 11 posts we hold for @solar_security. 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 — 126,294 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 3 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.

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

“Солар” (@solar_security), 6,529 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/solar_security.

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.