4 measurements spanning 6 days, net +6. 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 4,652–4,660 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 07:23
4,659
+3
9 Aug 2026, 12:39
4,656
+3
6 Aug 2026, 11:21
4,653
no change
6 Aug 2026, 05:46
4,653
first reading
Engagement
18 posts held, back to 9 January 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 7 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
21.0%
avg views ÷ 4,659 subscribers
Avg views / post
979
1 post measured
Reaction rate
1.74%
reactions ÷ views · ER floor
Posts in window
1
of 18 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 10 August 2026
Posts held
18 (9 January 2026 – 10 August 2026)
Views total
979
Reactions total
17
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 05:39 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
26m 48s
Average length
8m 56s
Measured directly from 3 videos 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
311 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 45.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
140
45.0%
👍
126
40.5%
❤
16
5.14%
👎
8
2.57%
🎉
7
2.25%
🤝
5
1.61%
👌
4
1.29%
👏
3
0.965%
💯
1
0.322%
😭
1
0.322%
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 15 of the 18 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 311reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 9 January 2026 to 10 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.
Мы с Петром (https://t.me/yellow_ai_vibe) собрали штуку, после которой фраза «ИИ помогает программисту» кажется устаревшей.
Речь уже не о помощнике, который дописывает отдельные куски кода. Речь о полноценном агентском pipeline, который забирает задачу целиком на себя и пропускает ее через все этапы без участия человека:
✔️ анализирует постановку;
✔️ готовит проверяемый план;
✔️ обсуждает его с несколькими моделями…
⚡️ Вайбкодинг в EDT — разберём на «Жёлтом митапе»
20 марта выступаю на онлайн-митапе для разработчиков 1С. Покажу, как можно использовать AI в ежедневной разработке и встроить его в рабочий процесс.
На докладе разберём:
— постановку задачи и генерацию кода с помощью AI,
— итерации и доработку результата,
— работу с исходниками и EDT,
— финальную фиксацию изменений и коммит в репозиторий.
Доклад будет полезен тем, …
The shares total 189%, 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.
ИИ-разработка наглядно
Под этим постом вы просили показать пример разработки с ИИ агентами. Мой друг и коллега примерно в это же время записал стрим процесса как раз на том стеке.
Приятного просмотра:
#AIдля1С
Промты для 1С-кодинга. И мое мнение
По результатам конференции по вайбкодингу, вы просили выложить готовые промпты.
Я не большой сторонник давать готовые решения такого плана, поскольку всё очень меняется от проекта к проекту и от задачи к задаче.
Поэтому вместо готовой рыбы, я дам вам удочку, чтобы вы сами могли всё сделать под себя.
Итак, вот два готовых GPT-агента для генерации промптов:
1️⃣ Помощни…
🚀 27 мая состоится ЕСТЬРЕСУРС ERP AI FORUM — профессиональная конференция о практическом применении ИИ в автоматизации бизнеса на базе 1С и не только.
Билеты уже в продаже:
Узнать подробности и купить
Специально для подписчиков канала @OneSCast - скидка 10% по промокоду:
5RZAH
📍 Где: Конгресс-центр МГТУ им. Н.Э. Баумана (Москва).
Формат — не «про теорию», а про то, что действительно работает в бизнесе: доклады …
Первые два громких релиза года, и с разницей в несколько минут 🎉
Не мог об этом не написать, поскольку сам очень ждал.
GPT 5.3 Codex и Claude 4.6 Opus!
Красота последнего - в расширенном контексте в 1М токенов при той же цене 🔥
Можно пробовать на больших задачах в EDT с какой-нибудь ERP 😈
🟣 @OneSCast - здесь про 1С и AI
Воу! Воу! Воу!
Этот день точно войдет в наши календари надолго! 🥳
Ровно год назад Карпати впервые упомянул слово «вайбкодинг» в своем посте. Сегодня этот день назвали днём вайбкодинга. И что-то мне подсказывает, что это рождение нового профессионального дня 😁
Коллеги, я вас поздравляю!!! 💥
Еще год назад, получая новую задачу, я думал, какие модули я буду смотреть, какие архитектурные паттерны использовать. Сейчас …
OneSCast | 1С Предприятие pinned «Перезагрузка канала. 3, 2, 1… Мой канал притих, посты стали редкостью. Ведение канала и моя жизнь пошли разными путями… я выгорел. Но события последних месяцев стали выстраиваться удивительно положительно, уровень энергии пошел вверх. Я возвращаюсь в канал…»
#AIдля1С
Разработка в VSCode на выгруженной в файлы конфе.
Обещал рассказать, как работает Cloude на большом контексте. Рассказываю:
🛠 Что использвоал:
Выгрузил конфигурацию в файлы. Подключил каталог как проект в VSCode, с установленными расширениями Claude и ChatGPT.
Задачу взял выдуманную, но вполне подходящую под реальность: реализовать конструктор назначения платежа по шаблону и подключить к обработке банк-к…
👍17🔥10❤5👌4
Showing the 12 most recent of 18 posts we hold for @OneSCast. 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.
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.
The shares total 189%, 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 18 most recent posts we hold, published 9 January 2026 to 10 August 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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
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 12 August 2026 — this
entry's latest reading, not the date you are reading this.
“OneSCast | 1С Предприятие” (@OneSCast), 4,659 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/OneSCast.
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.