Telegram RegisterThe public register of Telegram
Telegram profile photo for Бизнес-процессы в Битрикс24

Channel

Бизнес-процессы в Битрикс24

@business_processes_b24

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Polls · Citations · Cite this entry

189subscribers

+10 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-1002448427559
TypeChannel
Username@business_processes_b24
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 September 2026
Last confirmed live13 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/business_processes_b24

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

179190184.57 August 2026 — 179 subscribers8 August 2026 — 180 subscribers15 August 2026 — 185 subscribers21 August 2026 — 187 subscribers28 August 2026 — 188 subscribers4 September 2026 — 190 subscribers9 September 2026 — 190 subscribers13 September 2026 — 189 subscribers1897 August 202613 September 2026
8 measurements spanning 37 days, net +10. 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 177–192 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 10:20189-1
9 Sept 2026, 00:22190no change
4 Sept 2026, 16:38190+2
28 Aug 2026, 13:06188+1
21 Aug 2026, 13:26187+2
15 Aug 2026, 01:13185+5
8 Aug 2026, 06:06180+1
7 Aug 2026, 18:41179first reading

Engagement

20 posts held, back to 29 July 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.

ERR · 30 days
46.2%
avg views ÷ 189 subscribers
Avg views / post
87.3
4 posts measured
Reaction rate
2.14%
reactions ÷ views · ER floor
Posts in window
4
of 20 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. It is computed over the 2 of 4 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 September 2026
Posts held20 (29 July 2026 – 7 September 2026)
Views total349
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Sept 2026, 00:22 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

47 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 38.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1838.3%
👍1531.9%
❤1123.4%
👌24.26%
🤝12.13%

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

Measured over the 20 most recent posts we hold, published 29 July 2026 to 7 September 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @business_processes_b24. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 29 July 2026 to 7 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

7 Sept 2026, 05:03 UTC60 viewsread 9 September 2026
Photo

Хранилища VS AI-анализ Что быстрее и эффективнее: сделать процесс через использование хранилищ или подключить AI-анализ? Смотрите запись по ссылкам: YouTube | Rutube | VK

4 Sept 2026, 05:04 UTC91 views2 reactionsread 9 September 2026

Хранение чувствительной информации в Битрикс24 Если вы активно пользуетесь Битрикс24, то все больше процессов перетекает туда. А за процессами тянутся и артефакты: документы, базы данных и пр. И тут возникает вопрос: а можно ли вообще хранить здесь такие данные? Технически - да, сложил и хранишь, никаких сложностей. Юридически - вроде да, есть соглашение о конфиденциальности информации, где Битрикс24 заверяет, что …

❤1👍1

2 Sept 2026, 05:04 UTC96 views2 reactionsread 9 September 2026

Вот и лето прошло, Шуфутинский уже выглядывает из-за угла, а нового редактора все ещё нет😒 Тем временем, Битрикс24 активно рекламирует Коворк, переводя пользователей все дальше от бога администрирования системы. Не буду говорить, что мы впервые сталкиваемся со срывом сроков, но так хотелось, чтобы эту дату выдержали🤞 Но обновления продолжают выходить, а я продолжу подогревать ваш интерес, выпуская новые ролики. Те…

👍2

31 Aug 2026, 05:00 UTC102 viewsread 9 September 2026
Photo

Запись стрима по новому редактору БП На минувших выходных в живом формате изучили, как работает новый редактор бизнес-процессов, посмотрели новые фишки. Всех, кто поучаствовал, благодарю за активность - вопросы были актуальными и интересными😊 Пожалуй, формат нужно будет повторять, хотя бы раз в месяц, так что ждите новых анонсов. Смотрите запись по ссылкам: YouTube | Rutube | VK

28 Aug 2026, 10:00 UTC108 views4 reactions1 Starread 9 September 2026

Новая дата стрима: воскресенье, 30.08.26 г. в 12:00 МСК. Увидимся на канале. Кто придет? 🔥

🔥4

26 Aug 2026, 07:01 UTC131 views7 reactionsread 9 September 2026

Не реви, если не получается! Всех в детстве воспитывали по-разному, особенно если учесть разницу поколений, и все мы по-разному реагируем на что-то новое, однако, регулярно проходим классический путь отрицание > гнев > торг > депрессия > принятие при столкновении с отрицательными факторами. Новые инструменты и функционал, который они привносят в рабочие процессы, могут не только облегчить ваши страдания, как админи…

👍6🔥1

21 Aug 2026, 05:53 UTC144 views5 reactionsread 9 September 2026

К сожалению, стрим в эту субботу вынужден перенести на другой день по личным обстоятельствам. О новой дате сообщу на следующей неделе. Всем добра😊

❤2👌2🤝1

19 Aug 2026, 07:02 UTC153 views5 reactionsread 9 September 2026

Читаете Битрикс24 changelog? Если нет, то стоило бы начать, хотя бы потому, что там можно отслеживать доработки, которые в обозримом будущем появятся на облаке или коробке, у тестовой группы порталом или у всех. Вчера, например, Битрикс24 выкатил доработки нового редактора БП, которые решают большинство из найденных нами проблем - это очень радует, поскольку видна работа с обратной связью. Обозримость будущего мож…

👍5

17 Aug 2026, 05:01 UTC150 viewsread 9 September 2026
Photo

Новый редактор бизнес-процессов в Битрикс24. Управление процессами и хранилищем Сегодня смотрим, какие инструменты доступны в редакторе на данный момент, и предполагаем, как их можно использовать. Пишите в комментариях свои идеи по использованию новых нод! Смотрите ролик по ссылкам: YouTube | Rutube | VK

14 Aug 2026, 05:00 UTC179 views11 reactionsread 9 September 2026

Стриму быть! Вы проголосовали, я вас услышал, и планирую провести стрим на пару часов, где постараюсь в живом формате показать интересные моменты нового редактора БП, обратить ваше внимание на отличия от старого, а также реализовать какие-то задачи, которые вы принесете с собой. Для меня это первый опыт проведения стримов, поэтому возьму недельку на подготовку, и встретимся с вами на YouTube-канале 22.08.2026 г. в …

🔥11

12 Aug 2026, 07:04 UTC143 views4 reactionsread 9 September 2026

Когда Фу превращается в Вау, а Вау превращается в Фу Это не китайская идиома, а реальность, с которой сталкивается практически любой пользователь практически любого продукта. Когда внедряется новая система, возьмём для примера Битрикс24 (а что же ещё), сотрудники вынуждены менять свои привычные подходы на новые ввиду того, что все системы разные. Отсюда у них возникает негативное отношение к продукту, потому что он…

❤3🔥1

10 Aug 2026, 04:59 UTC130 viewsread 9 September 2026
Photo

Новый редактор бизнес-процессов в Битрикс24. Триггеры Как запускаются новые бизнес-процессы. Смотрите ролик по ссылкам: YouTube | Rutube | VK

Showing the 12 most recent of 20 posts we hold for @business_processes_b24. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

7 Aug 2026, 14:07 UTCAnonymous Poll17 voters

Когда можете присутствовать?

  1. В выходные дни с 10 до 1965%
  2. В будние дни с 15 до 1941%

The shares total 106%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 29 July 2026 to 7 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Mentions

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

“Бизнес-процессы в Битрикс24” (@business_processes_b24), 189 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/business_processes_b24.

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.