4 measurements spanning 21 days. 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 711–712 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
28 Aug 2026, 06:13
711
-1
21 Aug 2026, 01:03
712
+1
8 Aug 2026, 02:17
711
no change
7 Aug 2026, 11:38
711
first reading
Engagement
20 posts held, back to 18 June 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
15.5%
avg views ÷ 711 subscribers
Avg views / post
110
1 post measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 5 August 2026
Posts held
20 (18 June 2026 – 5 August 2026)
Views total
110
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 02:17 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
1m 29s
Average length
1m 29s
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
6 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
3
50.0%
❤
2
33.3%
🔥
1
16.7%
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 6 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 6reactions 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 18 June 2026 to 5 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.
Добрый день! В рабочем отпуске до 17 августа. Пока работаю на удаленке. На связи по телефону и поддержке на сайте.
Глобальных изменений нет. Разработки сейчас на исторически стабильном уровне). За последний месяц из 350 активных пользователей обратилось 5 пользователей по небольшим вопросам. Приеду будем продолжать решать разные задачи.
В связи с непростой экономической ситуацией в стране сделал понижение цены на Ме…
Выйдет УТ 11.6. Мне уже сообщили о некоторых изменениях по ценообразованию. Изменения будут глобальные. И возможно не только связанные с поверхностным описанием новой редакции....
Когда такая цифра в версии программы, обычно означает очень серьезные изменения.
Тут случай. Была серьезная доработка которую запросил заказчик.
И я даже создал кейс - множественные артикулы товаров (аналоги объединение).
При загрузке прайсов заказчик объединяет все в один товар в базе (не разбивает элементы).
И в связи с этим возник новый вариант поиска. А профилей у него много (это самый крупный по загрузкам прайсов пользователей - 150 прайсов в день).
Так вот он запроси чтобы в профиле можно …
Что планируется с помощью ИИ. Активно смотрим ИИ что работают с 1С, Битрикс и не только. Задач на самом деле много, но не все прям бах и появилось. Хотя получение заказов ускоряет.
Есть задачи где можно что то обработать вне 1С, внешние компоненты, агенты, библиотеки и прочее.
Задач нагенерировать можно много. С самим кодом в 1С проблем нет. А вот вне 1С они могут быть.
Обработка картинок, распознавание документов, …
Разбитые артикулы.
Распознаватель позволяет генерировать распознавание артикулов, состоящих из раздельных букв и цифр в наименовании (разделенных пробелами).
Даже начинающихся с 1 раздельной буквы. Могут быть артикулы состоящие из трех разделенных элементов.
Можно даже учитывать цвет.
Можно учитывать и ошибки в таких артикулах.
Друзья! Я сейчас занимаюсь стадией загрузки. Но дальше пройдет работа в сопоставлениях. С техникой - все более менее понятно! И это новый уровень. Но есть еще много других специфик товаров. Где люди буквально руками сопоставляют страшные названия без артикулов.
И я начну там использовать то на чем сейчас набиваю руку. А это значит что само сопоставление будет переработано. Так как тут результат меня просто поразил. …
Слева навигация по загружаемому прайсу. Без нее вообще нереально прочитать прайс поставщика - так чтобы полностью
понять что в нем. Листать такие объемы нереально. Навигация - просто чудо в загрузке.
Особенно оказалась полезна именно в этой задаче - где распознаватель из наименований получил и производителей и артикулы.
Signed Eugeneer
Showing the 12 most recent of 20 posts we hold for @subsystemsru. 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 28 August 2026 — this
entry's latest reading, not the date you are reading this.
“МЕГАПРАЙС - Разработки для 1С” (@subsystemsru), 711 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/subsystemsru.
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.