Telegram RegisterThe public register of Telegram

Channel

Мир 1С (Сергей Сыпачев)

@sergsyp

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

1,524subscribers

+6 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001796038825
TypeChannel
Username@sergsyp
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 live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/sergsyp

Growth

1,5171,5241,520.56 August 2026 — 1,518 subscribers6 August 2026 — 1,518 subscribers7 August 2026 — 1,517 subscribers10 August 2026 — 1,522 subscribers12 August 2026 — 1,524 subscribers6 August 202612 August 2026
5 measurements spanning 7 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 1,516–1,525 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 20:271,524+2
10 Aug 2026, 05:101,522+5
7 Aug 2026, 02:421,517-1
6 Aug 2026, 07:351,518no change
6 Aug 2026, 05:471,518first reading

Engagement

22 posts held, back to 1 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
40.9%
avg views ÷ 1,524 subscribers
Avg views / post
623
18 posts measured
Reaction rate
1.20%
reactions ÷ views · ER floor
Posts in window
18
of 22 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 11 of 18 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 August 2026
Posts held22 (1 July 20267 August 2026)
Views total11,218
Reactions total81
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 18:11 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

107 reactions across 13 posts, in 7 distinct kinds. The most used accounts for 56.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍6056.1%
🔥2927.1%
👎87.48%
👌43.74%
32.80%
💩21.87%
🤣10.935%

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

Measured over the 22 most recent posts we hold, published 1 July 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, 12:04 UTC220 viewsread 7 August 2026
File

Конец эпохи 1С? Один промт — и готовая конфигурация за вечер (2/2) Аудио версия

7 Aug 2026, 12:04 UTC265 views5 reactionsread 7 August 2026
Photo

Конец эпохи 1С? Один промт — и готовая конфигурация за вечер (1/2) В подкасте Иван Титов рассказывает о создании OneBase — open-source альтернативы 1С на Go, которая решает проблему громоздкости платформы для мелких задач. Делится своим путем в профессию, показывает, как с помощью ИИ можно за вечер переписать конфигурацию, и объясняет, почему агенты уже сами тестируют и исправляют код. Также упоминает забавный бан 🫢

👍2🔥21

5 Aug 2026, 15:47 UTC355 views5 reactionsread 7 August 2026

Друзья, спасибо за встречу! Было реально интересно — живое обсуждение, вопросы по делу, хороший обмен опытом. Именно ради таких встреч это и затевается. Да, столкнулись с техническими трудностями по ходу. Но оперативно разобрались. Спасибо, что не разошлись. Что дальше: 🛑Материалы встречи выложим совсем скоро. 🛑Продолжаем общение в закрытой группе — там будет всё: видео-записи, слайды, транскрипции. Вход в закрыт

👌4🔥1

5 Aug 2026, 14:20 UTC374 viewsread 7 August 2026

Новая ссылка https://telemost.yandex.ru/j/8789503443

5 Aug 2026, 13:45 UTC378 viewsread 7 August 2026

Начинаем через 15 минут, в 17:00 мск. Ссылка на встречу https://telemost.yandex.ru/j/8532296144

4 Aug 2026, 14:59 UTC415 views1 reactionsread 7 August 2026

🎤Напоминание про открытый микрофон! 📅Завтра, 5 августа в 17:00 мск поговорим об ИИ, в том числе о ИИ-агентах: где они уже помогают в работе, а где пока создают больше вопросов, чем ответов. Готовьте свои истории. Без магии — только реальный опыт 😉 Ссылку на Яндекс Телемост опубликуем перед стартом.

👍1

3 Aug 2026, 05:02 UTC486 views8 reactionsread 7 August 2026
Photo

🔥Дайджест новостей 1С за неделю В выпуске — производительность крупных баз, безопасная работа с данными, обновления инструментов разработки и здравый подход к корпоративному ИИ. 1⃣[Производительность] 13 причин медленной работы 1С Практический чек-лист по индексам, запросам в циклах, длинным транзакциям и клиент-серверным вызовам. Главный вывод: сначала измеряем проблемную операцию, затем выбираем способ оптимизаци

👍5🔥3

1 Aug 2026, 02:33 UTC558 views9 reactionsread 7 August 2026

На открытом микрофоне поговорим об искусственном интеллекте По итогам голосования победила тема искусственного интеллекта 🥳 Я сам сейчас активно использую ИИ-агентов: пробую разные варианты, сравниваю подходы и на практике оцениваю границы их применимости. Так что будет о чём поговорить — без магии и с реальным опытом. Приходите обсудить, где ИИ уже помогает в работе, а где пока создаёт больше вопросов, чем ответо

👍7🔥2

31 Jul 2026, 11:45 UTC599 views20 reactionsread 7 August 2026
Photo

Друзья, я создал канал «Мир 1С» в MAX Основную часть постов из Telegram уже перенёс — можно читать и подписываться: 🔗https://max.ru/se13299262_biz Буду рад видеть вас и там.

👍10👎8💩2

28 Jul 2026, 04:44 UTC≈1,020 views12 reactionsread 7 August 2026
Photo

▶️Записал подкаст с Иваном Титовым — разработчиком open-source-платформы OneBase. Поговорили о его пути в 1С, о том, как появилась идея OneBase и почему сегодня бизнес-приложения можно создавать с помощью ИИ-агентов практически без ручного написания кода. Разобрали, как устроена его платформа, для каких задач она подходит и почему скорость разработки сейчас зависит не столько от знания конкретного стека, сколько от

🔥11🤣1

27 Jul 2026, 05:01 UTC712 views3 reactionsread 7 August 2026
Photo

🔥Дайджест новостей 1С за неделю На этой неделе — усиление интеграционного контура, новый способ входа в 1С, важный сигнал для владельцев систем на 7.7 и практические обновления корпоративных решений. 1⃣[Интеграции] Вышла «1С:Интеграция КОРП» 1.0.5 Внутренний транспортный контур получил TLS и фильтрацию по IP, а список поддерживаемых ОС пополнили Astra Linux 1.8, РЕД ОС 7.3/8 и Rocky Linux 8.10. Также появились новы

👍3

26 Jul 2026, 06:43 UTC649 viewsread 7 August 2026
Poll

Базовые треки на выбор

  1. 🤖 ИИ в 1С: реальные кейсы автоматизации разработки, а не хайп.65%
  2. 💼 Карьера: позиционирование и поиск работы на поляризованном рынке.31%
  3. ⚡️Архитектура: боевые кейсы оптимизации высоконагруженных баз.42%
  4. 🔄 Переход на ERP: неочевидные грабли миграции и управление рисками.18%
  5. 🪄DevOps в 1С: Git, CI/CD и автотесты без лишней бюрократии.47%

The shares total 203%, 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.

Showing the 12 most recent of 22 posts we hold for @sergsyp. 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 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

26 Jul 2026, 06:43 UTCFinal Results96 voters

Базовые треки на выбор

  1. 🤖 ИИ в 1С: реальные кейсы автоматизации разработки, а не хайп.65%
  2. 💼 Карьера: позиционирование и поиск работы на поляризованном рынке.31%
  3. ⚡️Архитектура: боевые кейсы оптимизации высоконагруженных баз.42%
  4. 🔄 Переход на ERP: неочевидные грабли миграции и управление рисками.18%
  5. 🪄DevOps в 1С: Git, CI/CD и автотесты без лишней бюрократии.47%

The shares total 203%, 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.

15 Jul 2026, 15:29 UTCAnonymous Poll27 voters

Как оцените глубину доклада?

  1. 🎯 Глубоко и по делу26%
  2. 👍 Хорошо, но местами поверхностно19%
  3. 👎 Слишком базово11%
  4. 😴 Не зашло44%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

15 Jul 2026, 15:27 UTCAnonymous Poll33 voters

Сколько идей вы заберете со встречи "психология и программирования" в работу?

  1. 🔥 3+ готовых решений15%
  2. 💡 1-2 идеи для внедрения21%
  3. 📚 Только теория27%
  4. 🤷 Ничего нового36%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is 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 22 most recent posts we hold, published 1 July 2026 to 7 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.

Citation-graph rank

Citation-graph rank — 24,917 of 1,336,469entries 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

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 5 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.

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.

“Мир 1С (Сергей Сыпачев)” (@sergsyp), 1,524 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/sergsyp.

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.