Telegram RegisterThe public register of Telegram

Channel

Е.БУДНИ программиста 1С | Роман Чумадин

@e_budni_programmer

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

17,195subscribers

-10 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001709325263
TypeChannel
Username@e_budni_programmer
DescriptionЕжедневные будни программиста 1С - это канал с реальными задачами с работы, с собеседований, повседневные хитрости, подборки и гайды. Подойдет для начинающих и опытных Автор и вопросы по рекламе: @chum1roma
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held6
Confirmed unchanged2 times, most recently 13 August 2026
On Telegramt.me/e_budni_programmer

Growth

17,19517,20517,2006 August 2026 — 17,205 subscribers6 August 2026 — 17,202 subscribers7 August 2026 — 17,200 subscribers8 August 2026 — 17,197 subscribers11 August 2026 — 17,199 subscribers12 August 2026 — 17,195 subscribers6 August 202612 August 2026
6 measurements spanning 6 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 17,194–17,207 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 01:5217,195-4
11 Aug 2026, 05:1517,199+2
8 Aug 2026, 09:1517,197-3
7 Aug 2026, 12:1417,200-2
6 Aug 2026, 13:0617,202-3
6 Aug 2026, 05:4717,205first reading

Engagement

21 posts held, back to 2 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 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
9.76%
avg views ÷ 17,195 subscribers
Avg views / post
1,680
7 posts measured
Reaction rate
1.08%
reactions ÷ views · ER floor
Posts in window
7
of 21 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 6 August 2026
Posts held21 (2 June 20266 August 2026)
Views total11,749
Reactions total127
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 00:36 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
183
Videos
50
Links
300

Lifetime counters from Telegram’s own channel header, read 13 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.

Video runtime
28s
Average length
14s

Measured directly from 2 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

414 reactions across 20 posts, in 11 distinct kinds. The most used accounts for 65.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍27165.5%
🔥6014.5%
286.76%
💯194.59%
122.90%
🤡112.66%
🙈61.45%
👌30.725%
20.483%
🆒10.242%
😭10.242%

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

Measured over the 21 most recent posts we hold, published 2 June 2026 to 6 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 21 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 @e_budni_programmer. 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 21 most recent posts we hold for this entry, published 2 June 2026 to 6 August 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.

Advertising

Ad load
4.76%
1 of 21 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,740
over 1 measured post
Median views · rest
2,220
over 20 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqwUp3fx127 July 202627 July 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 21 most recent posts we hold, published 2 June 2026 to 6 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

6 Aug 2026, 14:15 UTC999 views10 reactionsread 13 August 2026

РУБРИКА «ЧёПоСтандартам» Открытие форм Стандарт про открытие форм, из него можно сделать вывод: Форма - это отдельный объект, который не должен изменяться извне и из неё некорректно получать результат работы напрямую (через обращение к реквизитам самой формы). Для передачи данных на форму используем параметры формы, а для результата обработчики событий. #std404 1. Для открытия форм следует применять метод глобальн

👍6🔥4

30 Jul 2026, 13:10 UTC≈1,580 views17 reactionsread 13 August 2026

РУБРИКА «ЧёПоСтандартам» Многократная запись регистров сведений и накопления Стандарт, с которым многие сталкиваются в начале своего пути, когда ещё только разбираются что такое МенеджерЗаписи, а что такое НаборЗаписей. И как раз этот стандарт может помочь новичкам более детально разобраться что и зачем, и почему в большинстве случаев надо использовать НаборЗаписей. #std792 1. Не рекомендуется записывать наборы за

👍14🔥3

27 Jul 2026, 09:59 UTC≈1,740 views23 reactionsread 13 August 2026
Advertisementerid 2VtzqwUp3fxVideo

Хочешь соединять мир бизнеса и цифровых технологий? 💻 Тогда направление «Бизнес-информатика на платформе 1С» в «Алабуга Политех» — для тебя! Здесь ты не просто читаешь учебники. Ты: ☺️ изучаешь IT-технологии и анализ данных ☺️ учишься управлять бизнес-процессами ☺️ участвуешь в реальных цифровых проектах компании Что ты получишь: • Зарплату от ☺️☺️ ☺️☺️☺️ рублей в месяц (растёт каждый год!) • Диплом государственног

🤡116👍32🆒1

24 Jul 2026, 14:31 UTC≈1,740 views39 reactionsread 13 August 2026

Запуск внешней обработки Вчерашний стандарт напомнил ещё одну историю, когда ты просто открываешь обработку, а она выполняет какие-то действия прям сразу... Да, возможно в каких-то случаях это нормально, но я считаю всё-таки нет)) и надо запускать действия только по кнопке. У меня это привело к привычке открывать любые обработки написанные не мной, а если мной, то тем более)), сначала в конфигураторе и смотреть/пров

👍23💯151

23 Jul 2026, 09:46 UTC≈1,880 views17 reactionsread 13 August 2026

РУБРИКА «ЧёПоСтандартам» Требования к проведению документов Кто бы мог подумать о том, что в стандартах можно ещё встретить ответ на вопрос, который встречается почти на каждом собесе, "зачем же нужны документы в 1С". Что ещё раз говорит о том, что регулярное чтение и изучение стандартов 1С поможет вам не только в текущей работе, но и при поиске новой работы) #std603 1. Документы предназначены для ввода первичной

👍124🔥1

16 Jul 2026, 13:16 UTC≈2,000 views13 reactionsread 13 August 2026

РУБРИКА «ЧёПоСтандартам» Обработчик события ОбработкаЗаполнения Не путать с обработчиком "ОбработкаПроверкиЗаполнения", о котором был пост на прошлой неделе. В этом стандарте речь про обработку заполнения, в том числе про ввод на основании. #std396 1. В случае если в силу каких-либо условий необходимо ограничивать ввод на основании по команде "Создать на основании", то такую проверку следует выполнять в обработчик

👍13

14 Jul 2026, 14:24 UTC≈1,810 views8 reactionsread 13 August 2026

Записи выступлений Итак, хорошие новости, подъехали записи моих выступлений. На Инфостарт плюсом ещё и в виде статьи, по возможности, накидайте плюсиков, говорят это поднимает что-то там) И отдельно ссылка на видео На ЕстьРесурс ERP AI Forum так же вышли записи, но пока актуальность сохраняется, они доступны платно. По цене чуть дешевле онлайн билета, если следите за актуальной информацией и пропустили конференцию

👍53

9 Jul 2026, 09:01 UTC≈2,480 views18 reactionsread 13 August 2026

РУБРИКА «ЧёПоСтандартам» Обработчик события ОбработкаПроверкиЗаполнения Если вы задавались вопросом как и где проверить корректность заполнения документа, то ответ есть в этом стандарте. #std463 1.1. В данном обработчике модуля объекта выполняются действия, связанные с проверкой правильности заполнения значений реквизитов объектов (измерений, ресурсов, реквизитов табличных частей и т.п., далее: просто "реквизиты")

👍135

6 Jul 2026, 10:44 UTC≈2,260 views25 reactionsread 13 August 2026
Photo

Check, никогда бы не подумал) Иной раз едешь на такси и видишь как горит чек, и думаешь, ну ведь что-то же не работает, почему не починить?!) И вот, уже несколько недель я езжу с check'ом на приборной панели своего авто) Проблема в ГБО (газ) установленном на авто, как оказалось довольно экономичная штука и удобная сейчас, пробки на заправках почти такие же как и были. Но после последнего ремонта плохо отрегулирова

👍11🔥8🙈6

2 Jul 2026, 14:13 UTC≈2,260 views22 reactionsread 13 August 2026

РУБРИКА «ЧёПоСтандартам» Обеспечение совместимости библиотек В основном стандарт рассчитан на тех, кто занимается разработкой своих библиотек, но ознакомиться с ним точно стоит с точки зрения понимания и БСП, как самого явного примера библиотек. #std644 1. При разработке библиотек необходимо обеспечивать обратную совместимость ... 1.5. В целях обеспечения совместимости следует - выделить программный интерфейс

👍15🔥7

30 Jun 2026, 15:59 UTC≈1,990 views6 reactionsread 13 August 2026

Стрим через 1 час — Разбор заметок + ответы на вопросы по 1С Содержание стрима: 🔸 Разбираем мои новые заметки за месяц, которые я сохраняю в отдельном канале Е.Б.LIST 🔸 Стандартный формат ответы на вопросы по сфере 1С (технические, по развитию и т.п.) ➡️ Ссылка на трансляцию в VK Live, а также в YouTube ⬅️ Когда: сегодня в 20:00. по МСК Продолжительность 10-60 минут, в зависимости от контента и количества ваших в

👍6

26 Jun 2026, 11:59 UTC≈2,390 views10 reactionsread 13 August 2026
Photo

Стрим в ближайший вторник — Разбор заметок + ответы на вопросы по 1С Содержание стрима: 🔸 Разбираем мои новые заметки за месяц, которые я сохраняю в отдельном канале Е.Б.LIST 🔸 Стандартный формат ответы на вопросы по сфере 1С (технические, по развитию и т.п.) ➡️ Ссылка на трансляцию в VK Live, а также в YouTube ⬅️ Расписание: один раз в месяц, во вторник в 20:00 по МСК. Когда: дата сообщается заранее. Ближайшая -

👍73

Showing the 12 most recent of 21 posts we hold for @e_budni_programmer. 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 — 340,450 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

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

Named by 6 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.

“Е.БУДНИ программиста 1С | Роман Чумадин” (@e_budni_programmer), 17,195 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/e_budni_programmer.

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.