Telegram RegisterThe public register of Telegram
Telegram profile photo for НиколAI 1С: от джуна до мидла

Channel

НиколAI 1С: от джуна до мидла

@razrab1c

On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

10,485subscribers

-3,757 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-1001809770245
TypeChannel
Username@razrab1c
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live26 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/razrab1c

Topic

Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

10,48514,24212,363.56 August 2026 — 14,242 subscribers7 August 2026 — 14,235 subscribers8 August 2026 — 14,070 subscribers9 August 2026 — 14,052 subscribers10 August 2026 — 14,041 subscribers11 August 2026 — 13,860 subscribers12 August 2026 — 13,847 subscribers13 August 2026 — 13,840 subscribers14 August 2026 — 13,645 subscribers15 August 2026 — 13,630 subscribers17 August 2026 — 13,431 subscribers18 August 2026 — 13,423 subscribers19 August 2026 — 13,240 subscribers20 August 2026 — 13,213 subscribers22 August 2026 — 13,193 subscribers23 August 2026 — 12,959 subscribers25 August 2026 — 12,924 subscribers26 August 2026 — 12,725 subscribers27 August 2026 — 12,709 subscribers28 August 2026 — 12,704 subscribers29 August 2026 — 12,511 subscribers30 August 2026 — 12,497 subscribers31 August 2026 — 12,495 subscribers1 September 2026 — 12,305 subscribers2 September 2026 — 12,297 subscribers3 September 2026 — 12,085 subscribers5 September 2026 — 12,070 subscribers9 September 2026 — 11,834 subscribers11 September 2026 — 11,599 subscribers13 September 2026 — 11,363 subscribers15 September 2026 — 11,350 subscribers17 September 2026 — 11,119 subscribers19 September 2026 — 10,923 subscribers26 September 2026 — 10,485 subscribers6 August 202626 September 2026
34 measurements spanning 51 days, net -3,757. 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 9,921–14,806 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
26 Sept 2026, 20:0110,485-438
19 Sept 2026, 15:1910,923-196
17 Sept 2026, 01:5811,119-231
15 Sept 2026, 00:3711,350-13
13 Sept 2026, 08:5811,363-236
11 Sept 2026, 13:1811,599-235
9 Sept 2026, 00:2011,834-236
5 Sept 2026, 15:0212,070-15
3 Sept 2026, 18:1512,085-212
2 Sept 2026, 11:4712,297-8
1 Sept 2026, 09:5412,305-190
31 Aug 2026, 08:0312,495-2
30 Aug 2026, 07:5412,497-14
29 Aug 2026, 06:2712,511-193
28 Aug 2026, 03:5512,704-5
27 Aug 2026, 05:1512,709-16
26 Aug 2026, 02:3412,725-199
25 Aug 2026, 03:1412,924-35
23 Aug 2026, 20:5812,959-234
22 Aug 2026, 02:1813,193first reading

Engagement

23 posts held, back to 3 April 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 52 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.74%
avg views ÷ 10,485 subscribers
Avg views / post
707
2 posts measured
Reaction rate
5.02%
reactions ÷ views · ER floor
Posts in window
2
of 23 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 2 September 2026
Posts held23 (3 April 2026 – 2 September 2026)
Views total1,414
Reactions total71
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 22: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.

Reaction mix

1,179 reactions across 23 posts, in 22 distinct kinds. The most used accounts for 32.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥38032.2%
👍24520.8%
⚡20617.5%
❤947.97%
✍867.29%
🗿302.54%
👏231.95%
🍾221.87%
💯181.53%
🤣151.27%
🎉121.02%
😁90.763%
🤓80.679%
🆒50.424%
👌50.424%
🤝50.424%
❤‍🔥40.339%
🥰40.339%
🫡30.254%
👀20.17%
2 further kinds30.254%

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

Measured over the 23 most recent posts we hold, published 3 April 2026 to 2 September 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

2 Sept 2026, 13:15 UTC462 views24 reactionsread 2 September 2026

📣 Открыта запись на новый поток Базового цикла обучения 1С📣 🆘До старта осталось около двух недель. При этом те, кто уже записался, не ждут первого занятия и приступили к подготовке 😶 На БЦО мы не будем просто смотреть, как преподаватель пишет код, или бездумно повторять действия по методичке🙄 Будем учиться понимать, что мы делаем, зачем мы это делаем и как потом использовать эти знания в реальной работе. 🎯На заня…

👍12🔥6⚡3❤2✍1

31 Aug 2026, 21:01 UTC952 views47 reactionsread 2 September 2026

🔔1 сентября🔔

🍾22🎉12🤓7⚡2❤2👍2

30 Aug 2026, 07:10 UTC≈1,310 views28 reactionsread 2 September 2026
Photo

Photo, posted without a caption

🤣15😁9⚡2👍2

29 Aug 2026, 15:31 UTC≈1,300 views41 reactionsread 2 September 2026

🎥 Новый урок: программно создаём реквизиты, команды, элементы формы в 🧑‍💻 В этом уроке форма перестаёт быть чем-то, что можно собирать только мышкой в конфигураторе. Мы прямо из кода добавим: ➖новый реквизит формы ➖поле, связанное с этим реквизитом ➖команду формы ➖кнопку, которая запускает клиентский обработчик Весь код пишем всегда в этом обработчике формы ПриСозданииНаСервере : &НаСервере Процедура ПриСозданииНа…

👍23❤7⚡5❤‍🔥4🤝2

27 Aug 2026, 11:54 UTC≈1,570 views36 reactionsread 2 September 2026

📚 Напоминаю: в эту субботу встречаемся в 13:00 по Москве. Будет два практических занятия: 🧩 1. Программное изменение форм в 1С ⚙️ 2. Динамическое изменение алгоритмов через Выполнить() Начинаем в субботу в 13:00 по Москве. Между двумя частями сделаем перерыв ☕️ Ну и немного про нашу площадку для обучения. Уже 187 регистраций🔥 Суммарно вы провели в обучении почти 93 часа 🤯 6️⃣ человек, которые прошли всё, что…

👍15🔥12⚡6🫡3

26 Aug 2026, 16:15 UTC≈1,520 views43 reactionsread 2 September 2026

Иногда люди довольно быстро приходят к выводу: «1С - это не моё» И я всё больше вижу, что очень часто проблема вообще не в 🧑‍💻 За время работы в одной компании я успел поработать в нескольких совершенно разных командах. Формально работодатель один и тот же, а ощущения от работы могли отличаться так, будто я полностью сменил компанию, расскажу про 3 команды 1️⃣ Первая команда, примерно 1 из 10 Там основная пробле…

💯18👍12❤11🆒2

26 Aug 2026, 08:28 UTC≈1,380 views42 reactionsread 2 September 2026
Photo

🔥 Отличное начало. У нас уже 119 регистраций, и суммарно в системе уже провели 42 часа 34 минуты. 🥇 И самое приятное — уже есть 2 человека, которые прошли всё, что сейчас доступно 👏 Так что двигаемся, очень хорошо!!! Если вы уже зарегистрировались, но ещё не начали или где-то остановились, самое время продолжать. А если ещё не регистрировались, присоединяйтесь🤌 На этой неделе я буду выкладывать новые задачи и нов…

👍20🔥12⚡5❤5

25 Aug 2026, 10:50 UTC≈1,560 views40 reactionsread 2 September 2026

👨‍🎓 Открываю новый набор на обучение по 🧑‍💻 Первая новая группа стартует уже примерно через 15 - 20 дней. Формат остаётся практическим: не просто посмотреть урок и забыть, а много писать код, делать домашние задания, разбирать ошибки и постепенно доходить до задач, которые реально встречаются в работе. Подробно программу, расписание и условия обучения тут 🔗 Подробности и запись А в эту субботу проведём сразу два …

🔥19✍9👏6👍4⚡2

24 Aug 2026, 13:22 UTC≈1,590 views122 reactionsread 2 September 2026

Posted without readable text

✍69🗿30🔥15⚡3❤3👏2

23 Aug 2026, 16:06 UTC≈1,810 views83 reactionsread 2 September 2026

Posted without readable text

🔥56❤13⚡4👍4🆒3👀2✍1

22 Aug 2026, 12:23 UTC≈1,990 views66 reactionsread 2 September 2026

Я вернулся) Завтра будут объяснения и где был, и что подготовил. Если есть какие-то вопросы, кому не ответил - пишите в ЛС @NikolayGabur

🔥33👍21❤7⚡3🙊2

29 Apr 2026, 05:49 UTC≈4,360 views28 reactionsread 2 September 2026

🔥 1С + AI — это уже не будущее. Это то, на чем сейчас зарабатывают. Сейчас на рынке происходит простая вещь: 👉 обычные 1С-разработчики делают задачи 👉 разработчики с AI делают в 2–3 раза больше за то же время И разрыв только растёт. Я собрал курс, где реально учимся работать с AI в 1С: ➖ как писать код быстрее ➖ как делать рефакторинг и ревью через AI ➖ как автоматизировать рутину ➖ как использовать Cursor, Cla…

🔥13👍8❤3🤝3🌚1

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

Posts edited after publishing

@razrab1c edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
1 September 2026
Most recent edit
1 September 2026

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Р1: Premium. Вакансии 1С для Синьоров
@joboneC · 19,977
Telegram ranks this channel #21 of 91 here — alongside 90 others — read 29 September 2026
1С Hacks | Бухгалтерия и Учёт
@secrets_1C · 45,901
Telegram ranks this channel #46 of 79 here — alongside 78 others — read 27 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“НиколAI 1С: от джуна до мидла” (@razrab1c), 10,485 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/razrab1c.

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.