Telegram RegisterThe public register of Telegram

Channel

wiki 1С + AI. База знаний, мысли и заметки.

@wiki1c

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

4,874subscribers

+2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001398861339
TypeChannel
Username@wiki1c
DescriptionНе только про 1С. Программирование и аналитика. Самообучение и развитие. Обратная связь @russian_linux
Created23 October 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/wiki1c

Growth

4,8724,8744,8736 August 2026 — 4,872 subscribers6 August 2026 — 4,872 subscribers10 August 2026 — 4,874 subscribers6 August 202610 August 2026
3 measurements spanning 4 days, net +2. 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,872–4,874 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 04:114,874+2
6 Aug 2026, 20:564,872no change
6 Aug 2026, 08:314,872first reading

Engagement

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

ERR · 30 days
33.4%
avg views ÷ 4,874 subscribers
Avg views / post
1,630
1 post measured
Reaction rate
0.245%
reactions ÷ views · ER floor
Posts in window
2
of 14 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 20 July 2026
Posts held14 (31 March 202620 July 2026)
Views total1,630
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 05:10 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
387
Videos
53
Links
776

Lifetime counters from Telegram’s own channel header, read 12 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
20s
Average length
20s

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

152 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 48.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😢7448.7%
🔥3523.0%
👍3019.7%
117.24%
👀10.658%
🤝10.658%

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

Measured over the 14 most recent posts we hold, published 31 March 2026 to 20 July 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

15 Jul 2026, 08:26 UTC≈1,630 views2 reactionsread 12 August 2026

http://t.me/rauitru_bot Регистрируйтесь на вебинар 17 июля по теме тормозов в базе и если готовитесь на эксперта. Разговор будет про индексы.

2

15 Jun 2026, 12:56 UTC≈2,550 views9 reactionsread 12 August 2026

Недавно Илья мне отправил свои книги с автографом. Обещал прочитать и отзыв оставить. Вот так скоротечна жизнь. Светлая память. Соболезнования родным, близким и коллегам.

😢9

15 Jun 2026, 12:55 UTC≈1,880 views44 reactionsread 12 August 2026
Forwarded from @cors_academyPhoto

С глубоким прискорбием сообщаем, что ушёл из жизни Илья Отькало — основатель и генеральный директор CORS Academy, преподаватель, автор образовательных программ и человек, благодаря которому академия стала тем местом, которое знают тысячи специалистов 1С по всей стране. Для нашей команды это огромная потеря. Более 20 лет Илья посвятил развитию сообщества 1С, обучению специалистов и созданию образовательных программ,

😢44

14 Jun 2026, 10:30 UTC≈1,480 views1 reactionsread 12 August 2026

Друзья сегодня будет короткий пост о ... Поддержке и помощи У Лены Дуюн (многие ее знают по классным выступлениям на Инфостарте и питерском клубе ИТ-директоров) сгорел позавчера дом. И если вдруг вам писали такой пост с аккаунта Екатерины Вешичковской - то ща, это Лена. Я с ней кратко говорил вчера и еще будем говорить через пару часов когда попаду в зону стабильной связи. Если вам достаточно моего поста - то я по

1

13 May 2026, 14:29 UTC≈1,940 views1 reactionsread 12 August 2026
Forwarded from @crocteamPhoto

😏 Полюбить внедрения 1С: миссия выполнима 28 мая проведем митап «Технологии управления 1С-проектами» — для тех, кто устал от хаоса в оценке и ручного управления процессами. Обсудим: 🟢как не проваливать оценку крупных внедрений 🟢зачем нужны СППР, план-факт и Vanessa 🟢как выстроить пайплайн и делегировать ИИ до 80% рутины Также вас ждут Q&A, нетворкинг и бонус: ❤️ ❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤

👍1

9 May 2026, 09:36 UTC≈2,010 views16 reactionsread 12 August 2026
Photo

С Днем Победы, коллеги! Мирного неба над головой

🔥132🤝1

20 Apr 2026, 11:18 UTC≈2,690 views26 reactionsread 12 August 2026
Forwarded from @razrab1cPhoto

Нашел классный ИИ-инструмент для разработки для 1С Конфигуратора 🛠 Сейчас даже срочном порядке добавляю его в курс по 1С и AI Confaster один из немногих, кто пытается это исправить. По сути это тот же Copilot, только для родного Конфигуратора. Не для EDT, не для VS Code, а именно для того самого окна, в котором большинство и работает каждый день. Что умеет: ➡️ Автодополнение кода прямо в редакторе ➡️ Ревью, исправл

👍18🔥7👀1

16 Apr 2026, 12:03 UTC≈1,700 views3 reactionsread 12 August 2026
Forwarded from @ozon_techPhoto

Ozon Tech Community 1C Meetup 23 апреля приглашаем аналитиков и разработчиков 1С узнать больше о нашей экспертизе и высоконагруженных решениях. Подготовили кейсы, выделили слоты для дискуссии и нетворка ➡️ встречаемся в 19:00 мск в лофте Casa Picassa и онлайн. О чём доклады 🔵Когда 1С перестаёт быть «просто 1С»: Инженерные практики Ozon — о пути развития проекта через CI/CD процессы. Виталий Онянов, тимлид разработ

👍21

6 Apr 2026, 17:37 UTC≈2,230 views27 reactionsread 12 August 2026

Уважаемые коллеги! Ваш админ - программист 1С и житель Махачкалы. Если лично меня стихия затронула несильно (протекла крыша и два дня света не было), то многие другие остались вообще без всего. Многие из вас были в Дагестане, можете связаться со своими знакомыми и помочь чем сможете пострадавшим. По поводу репоста с канала на благотворительный фонд выше - данный фонд связан с официальным Муфтиятом республики. P.S.

😢21👍6

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

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

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

“wiki 1С + AI. База знаний, мысли и заметки.” (@wiki1c), 4,874 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/wiki1c.

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.