Telegram RegisterThe public register of Telegram

Channel

Luxms BI | Платформа бизнес-аналитики

@luxmsbi

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

224subscribers

+0 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-1002144014360
TypeChannel
Username@luxmsbi
DescriptionLuxms BI — платформа бизнес-аналитики. Рассказываем о главных новостях, обновлениях системы и делимся интересным. Комьюнити Luxms BI - https://t.me/luxms_community
CreatedBetween 1 December 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/luxmsbi

Growth

2247 Aug 2026, 12:38 — 224 subscribers8 Aug 2026, 10:31 — 224 subscribers7 Aug 2026, 12:388 Aug 2026, 10:31
2 measurements taken within a single day. 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 223–225 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 10:31224no change
7 Aug 2026, 12:38224first reading

Engagement

9 posts held, back to 19 June 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
67.4%
avg views ÷ 224 subscribers
Avg views / post
151
4 posts measured
Reaction rate
5.79%
reactions ÷ views · ER floor
Posts in window
4
of 9 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 held9 (19 June 20267 August 2026)
Views total604
Reactions total35
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 10:31 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

Photos
345
Videos
6
Links
224

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

90 reactions across 9 posts, in 9 distinct kinds. The most used accounts for 48.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4448.9%
👍2426.7%
66.67%
👾66.67%
33.33%
👏22.22%
🤩22.22%
🥰22.22%
😍11.11%

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

Measured over the 9 most recent posts we hold, published 19 June 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:34 UTC122 views11 reactionsread 8 August 2026
Photo

📍 Работаем на форуме «Цифровая эволюция» в Калуге Команда ГК Luxms совместно с Arenadata участвует в VII Всероссийском форуме «Цифровая эволюция», одной из ключевых площадок, где обсуждаются цифровая трансформация государственного управления, развитие платформенных и облачных решений и применение искусственного интеллекта в государственном секторе. На совместном стенде с компанией Arenadata показываем полный россий

🔥7👍2👾2

6 Aug 2026, 09:54 UTC129 views10 reactionsread 8 August 2026
Photo

⚡️В новой версии Luxms BI database (pg) 12.0.1 расширен набор функций LPE для работы с датой и временем Одним из ключевых нововведений стала функция dateTimeShift. Она позволяет смещать дату, время или целый временной интервал на заданное количество секунд, минут, часов, дней, недель, месяцев, кварталов или лет. Например, с ее помощью можно анализировать продажи по часам, выявляя пиковую активность, например с 18:0

🔥5👍3🤩2

28 Jul 2026, 11:08 UTC175 views5 reactionsread 8 August 2026
Photo

🚀Новая статья в нашем блоге на Хабре: White Label и OEM: чему корпоративное ПО может научиться у автомобильной промышленности Что ценнее: купить готовый программный продукт, технологическое ядро или сразу получить собственный «завод» по выпуску ПО? Разбираемся, чем отличаются White Label и OEM, почему сегодня необязательно разрабатывать сложные технологии полностью с нуля и какие инженерные задачи скрываются за зрел

👍3👏1🔥1

23 Jul 2026, 08:21 UTC178 views9 reactionsread 8 August 2026
Photo

Закупки в крупных компаниях — это не только процессы и регламенты, но и работа с огромным количеством данных, взаимосвязей и рисков. Чтобы принимать действительно надежные решения, бизнесу нужна единая и прозрачная картина по контрагентам. Совместно с ИТ-холдингом Т1 для ПАО «Газпром» был реализован «Сканер контрагентов» — интеллектуальная система, объединившая графовую аналитику, ETL/ELT и встроенную BI-аналитику н

🔥6👍2👏1

16 Jul 2026, 10:26 UTC229 views8 reactionsread 8 August 2026
Photo

🔐 Что на самом деле проверяет ФСТЭК, когда выдает сертификат по 4 уровню доверия? Это не только защитные механизмы продукта. Сертификация становится проверкой всей цепочки создания ПО — от архитектурных решений и используемых компонентов до процессов разработки и контроля качества. В статье для TAdviser эксперты ГК Luxms разбирают, почему 4 уровень доверия ФСТЭК — это показатель зрелости не только продукта, но и са

🔥4👍2👾2

9 Jul 2026, 09:13 UTC213 views11 reactionsread 8 August 2026
Photo

Делимся записью вебинара "Информационная безопасность корпоративных систем: практика, требования ФСТЭК и опыт Luxms BI" 2 июля 2026 года эксперты Техконсур, Группы Астра, ГИС, Аренадата и Luxms BI обсудили современные угрозы для корпоративных систем, практику применения уровней доверия ФСТЭК и подходы к разработке и эксплуатации защищенного программного обеспечения. Для удобства разделили вебинар на отдельные блоки

👍4🔥4👾21

6 Jul 2026, 08:19 UTC218 views5 reactionsread 8 August 2026
Photo

Всем отличного начала рабочей недели! Рассказываем самое интересное за июнь ⬇️ Время дайджеста 🤩 🏆 Рейтинги и аналитика ▫️Luxms BI — в ТОП-3 российских BI-платформ по версии CNews. Рейтинг учитывает функциональные возможности, архитектурные подходы и развитие экосистем. ▫️В рамках обзора рынка эксперты ГК Luxms также дали комментарии о том, как меняются требования к BI-системам и куда движется отрасль. Читать зде

🔥3👍1😍1

22 Jun 2026, 09:52 UTC335 views12 reactionsread 8 August 2026
Photo

Большинство инцидентов в корпоративных системах связано не с экзотическими сценариями атак, а с вполне известными проблемами: ошибками в процессах разработки, недостаточным контролем доступа, уязвимостями приложений и человеческим фактором. 📍На вебинаре 2 июля вместе с экспертами Техконсур, ГИС, Аренадата, РОССИННО обсудим, как сегодня выстраивается информационная безопасность корпоративных систем и какую роль в эт

🔥63👍3

19 Jun 2026, 09:41 UTC357 views19 reactionsread 8 August 2026
Photo

⚡️Новая версия Luxms BI 12.0.1! Персонализация, шаблоны отчетов, удобное администрирование и улучшенный интерфейс - все в новом релизе. Коротко о новой версии - в карточках, листайте!➡️ Подробную новость про версию 12.0.1 читайте на нашем сайте. А #releasenotes со ссылками, а также обновления в документации смотрите здесь!

🔥85👍4🥰2

Showing the 9 most recent of 9 posts we hold for @luxmsbi. 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 — 422,800 of 1,478,351entries 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.

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

“Luxms BI | Платформа бизнес-аналитики” (@luxmsbi), 224 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/luxmsbi.

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.