Telegram RegisterThe public register of Telegram
Telegram profile photo for 1C Company

Channel

1C Company

@company1c

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cross-platform identity · Cite this entry

6,444subscribers

-4 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-1001112879932
TypeChannel
Username@company1c
Created6 September 2017measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live15 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/company1c

Topic

Technology — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

6,4366,4486,4426 August 2026 — 6,448 subscribers7 August 2026 — 6,447 subscribers10 August 2026 — 6,444 subscribers13 August 2026 — 6,437 subscribers17 August 2026 — 6,440 subscribers20 August 2026 — 6,445 subscribers23 August 2026 — 6,441 subscribers30 August 2026 — 6,436 subscribers2 September 2026 — 6,440 subscribers7 September 2026 — 6,439 subscribers11 September 2026 — 6,448 subscribers15 September 2026 — 6,444 subscribers6,4446 August 202615 September 2026
12 measurements spanning 40 days, net -4. 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 6,434–6,450 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 10:206,444-4
11 Sept 2026, 22:396,448+9
7 Sept 2026, 15:206,439-1
2 Sept 2026, 11:446,440+4
30 Aug 2026, 04:056,436-5
23 Aug 2026, 19:566,441-4
20 Aug 2026, 01:026,445+5
17 Aug 2026, 10:476,440+3
13 Aug 2026, 15:576,437-7
10 Aug 2026, 06:486,444-3
7 Aug 2026, 13:426,447-1
6 Aug 2026, 19:466,448first reading

Engagement

22 posts held, back to 30 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 9 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 22 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

198 reactions across 22 posts, in 10 distinct kinds. The most used accounts for 32.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥6432.3%
👍6030.3%
🐳4020.2%
2010.1%
😁42.02%
🤡42.02%
🕊21.01%
🗿21.01%
🤩10.505%
🤷‍♂10.505%

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 22 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 198 reactions 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 30 June 2026 to 11 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

11 Aug 2026, 06:51 UTC≈1,280 views7 reactionsread 12 August 2026

Напоминаем, что сегодня в 19:00 состоится вебинар «Парк аттракционов: интеграции и мобильные приложения». Будем разбирать интерфейс аутентификации в мобильном приложении: — реализуем получение и хранение токена на стороне мобильного приложения — подготовим инфраструктуру для фонового обмена данными Часть задач доверим 1С:Напарнику 🤖 Подключайтесь: https://1c.vkurse.ru/id/270432441 Ждем вас!

6🤩1

7 Aug 2026, 13:18 UTC≈2,090 views7 reactionsread 12 August 2026
Photo

Пятница! Не забывайте, что у вас есть шанс предложить идеи для улучшения платформы 1С:Предприятие и библиотек для прикладной разработки. Все предложения можно отправить на @platform_suggestions. Кстати, новые предложения уже переданы нашим разработчикам.

🐳7

6 Aug 2026, 08:50 UTC≈1,940 views5 reactionsread 12 August 2026

Приглашаем на вебинар «Парк аттракционов: интеграции и мобильные приложения». Будем разбирать интерфейс аутентификации в мобильном приложении: — реализуем получение и хранение токена на стороне мобильного приложения — подготовим инфраструктуру для фонового обмена данными Часть задач доверим 1С:Напарнику 🤖 🗓 11 августа, в 19:00 Подключайтесь: https://1c.vkurse.ru/id/270432441 Ждем вас!

🔥5

31 Jul 2026, 12:31 UTC≈2,710 views11 reactionsread 12 August 2026
Photo

Пятница! Не забывайте, что у вас есть шанс предложить идеи для улучшения платформы 1С:Предприятие и библиотек для прикладной разработки. Все предложения можно отправить на @platform_suggestions. Кстати, новые предложения уже переданы нашим разработчикам.

🐳7🕊21😁1

28 Jul 2026, 06:35 UTC≈2,960 views8 reactionsread 12 August 2026

❗️Сегодня в 19:00 состоится вебинар "Парк аттракционов. Интеграции и мобильные приложения. Часть 2"! ➡️ Встречаемся по ссылке: https://1c.vkurse.ru/id/223542960 На втором вебинаре: - Реализуем аутентификацию с помощью JWT - Подготовим инфраструктуру двухстороннего обмена через Планы обмена Часть задач доверим 1С:Напарнику 🤖 Ждем вас!

🔥6🐳2

24 Jul 2026, 12:59 UTC≈3,230 views10 reactionsread 12 August 2026
Photo

Пятница! Не забывайте, что у вас есть шанс предложить идеи для улучшения платформы 1С:Предприятие и библиотек для прикладной разработки. Все предложения можно отправить на @platform_suggestions. Кстати, новые предложения уже переданы нашим разработчикам.

🐳9👍1

23 Jul 2026, 07:42 UTC≈2,820 views1 reactionsread 12 August 2026

📣 Напоминаем, что сегодня в 19:00 состоится вебинар «1С:Корпоративное хранилище данных – консолидация данных из 1С для управленческой аналитики». Ведущие: Иван Кучин, Влад Дмитриев ➡️ Вебинар будет проходить по ссылке: https://1c.vkurse.ru/id/252353334 ✅ Ждём вас!

👍1

22 Jul 2026, 13:27 UTC≈2,570 views7 reactionsread 12 August 2026

❗️Приглашаем вас на вебинар "Парк аттракционов. Интеграции и мобильные приложения. Часть 2"! 📅 28 июля в 19:00 (время московское) Серия вебинаров "Парк аттракционов" создана для тех, кто хочет изучить платформу 1С:Предприятие. В сезоне "Интеграции и мобильные приложения" мы погружаемся в мобильную разработку. ➡️ Встречаемся по ссылке: https://1c.vkurse.ru/id/223542960 На втором вебинаре: - Реализуем аутентификаци

👍3🔥31

21 Jul 2026, 08:26 UTC≈2,560 views25 reactionsread 12 August 2026

Администрирование активных сессий

👍18🔥4🤡2🤷‍♂1

Signed Никита Старичков

17 Jul 2026, 13:12 UTC≈2,990 views7 reactionsread 12 August 2026
Photo

Пятница! Не забывайте, что у вас есть шанс предложить идеи для улучшения платформы 1С:Предприятие и библиотек для прикладной разработки. Все предложения можно отправить на @platform_suggestions. Кстати, новые предложения уже переданы нашим разработчикам.

🐳6👍1

16 Jul 2026, 10:38 UTC≈2,990 views5 reactionsread 12 August 2026

📣 Приглашаем на вебинар «1С:Корпоративное хранилище данных – консолидация данных из 1С для управленческой аналитики»! 📅 23 июля в 19:00 (время московское) На вебинаре разберём: 🔸 Для чего строят корпоративные хранилища данных. Единая версия «правды», что происходит в компании для анализа и управленческой аналитики. Консолидация данных из множества источников 1С (включая, УТ, ERP, БП, ЗУП и др.). 🔸 Общую архитектуру

3🤡2

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

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С
@buhru · 35,379
Telegram ranks this channel #24 of 95 here — alongside 94 others — read 2 September 2026
1С Hacks | Бухгалтерия и Учёт
@secrets_1C · 45,901
Telegram ranks this channel #38 of 79 here — alongside 78 others — read 27 August 2026
Бухэксперт
@buhexpert8 · 75,798
Telegram ranks this channel #44 of 94 here — alongside 93 others — read 19 August 2026

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

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q77202 on Wikidata, read 13 September 2026
Label1C Company
DescriptionRussian computer software developer
X / Twitter@1c_company
YouTubeUCGHJ8aGLX_dIntGLWr1vm8w
Official sitehttp://1c.ru

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

“1C Company” (@company1c), 6,444 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/company1c.

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.