Telegram RegisterThe public register of Telegram
Telegram profile photo for Время 1С

Channel

Время 1С

@time_1c

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

113subscribers

+0 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003707074106
TypeChannel
Username@time_1c
DescriptionНовости, слухи, юмор из мира 1С
CreatedBetween 1 February 2026 and 16 February 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live17 August 2026
Measurements held2
On Telegramt.me/time_1c

Growth

1139 Aug 2026, 11:47 — 113 subscribers9 Aug 2026, 12:00 — 113 subscribers9 Aug 2026, 11:479 Aug 2026, 12:00
2 measurements taken within a single day. 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 112–114 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 12:00113no change
9 Aug 2026, 11:47113first reading

Engagement

20 posts held, back to 16 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 20 posts for this entry, the most recent from 6 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
25
Videos
6
Links
34

Lifetime counters from Telegram’s own channel header, read 9 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
10m 17s
Average length
2m 03s

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

94 reactions across 18 posts, in 13 distinct kinds. The most used accounts for 31.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁3031.9%
👍2728.7%
🔥1920.2%
66.38%
22.13%
👏22.13%
🤣22.13%
🏆11.06%
👌11.06%
💯11.06%
😢11.06%
🤔11.06%
🤡11.06%

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

Measured over the 20 most recent posts we hold, published 16 February 2026 to 6 May 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

6 May 2026, 05:59 UTC111 views5 reactionsread 9 August 2026
Photo

#вайб AppSec Solutions выпустила SAST-анализатор для вайб-кодинга https://www.cnews.ru/news/line/2026-05-05_appsec_solutions_vypustila_sast-analizator AppSec Solutions интегрировала свой инструмент для статического анализа AppSec.Wave с MCP-сервером, чтобы обеспечить легкое взаимодействие с Claude Code, Cursor и другими решениями для анализа уязвимостей в коде на самых ранних этапах разработки приложений. Об этом

🔥3👌1👍1

17 Apr 2026, 05:45 UTC180 views7 reactionsread 9 August 2026
Video

#пятница Утренняя гимнастика бухгалтеров 1С. 👉 Время 1С. Подписаться.

😁4🤣2🔥1

8 Apr 2026, 05:59 UTC227 views4 reactionsread 9 August 2026
Photo

#импортозамещение 1С ведет переговоры о покупке доли в разработчике легендарной отечественной ОС Astra Linux https://www.cnews.ru/news/top/2026-03-19_1s_mozhet_stat_aktsionerom Приобретение «1С» миноритарной доли «Астры» позволило бы «1С» получать дивиденды и встраиваться в ее бизнес, а обеим компаниям — проводить более глубокую работу над совместимостью ПО «1С» и «Астры» и решением различных проблем, которые возн

👍31

3 Apr 2026, 13:45 UTC≈1,040 views7 reactionsread 9 August 2026
Video

#пятница Интервью с экспертом по всем вопросам. Эпизод 1. 👉 Время 1С. Подписаться.

🔥3😁3👍1

1 Apr 2026, 10:03 UTC≈1,080 views8 reactionsread 9 August 2026
Video

#среда #первоеапреля Интервью с экспертом по всем вопросам. Эпизод 2. 👉 Время 1С. Подписаться.

😁3🔥2👍1👏1🤡1

31 Mar 2026, 09:00 UTC858 views7 reactionsread 9 August 2026
Video

#вторник Интервью с экспертом по всем вопросам. Эпизод 4. 👉 Время 1С. Подписаться.

😁3🔥2👍1👏1

27 Mar 2026, 13:33 UTC≈2,400 views15 reactionsread 9 August 2026
Video

#пятница Интервью с экспертом по всем вопросам. Эпизод 3. 👉 Время 1С. Подписаться.

😁9🔥6

13 Mar 2026, 15:09 UTC366 views8 reactionsread 9 August 2026
Photo

#новости #пятница Создана дешевая ИИ-система https://www.cnews.ru/news/top/2026-03-11_sozdana_nedorogaya_ii-sistema Ученые из Новосибирска создали недорогую нейросетевую систему полноценной видеоаналитики для ритейла. Ну наконец-то, наверное, пока собираешь товары в корзинку она уже готовит чек на кассе. Это не первая подобная разработка, но она позволяет в реальном времени получать информацию о поведении покупателе

👍43😁1

10 Mar 2026, 15:00 UTC312 views2 reactionsread 9 August 2026
Photo

⚡️#новости ГК «Силтэк» переходит на HR-link Недавно мы с вами обсуждали как НПФ "Профессиональный" заставляет ИИ разбирать почерк сотрудников. А вот нам подвезли пример эталонной оцифровки всего процесса. Решение об отказе от бумаги в HR-процедурах связано с масштабными процессами цифровизации внутри ГК «Силтэк». В двух компаниях, входящих в группу (ООО «Силтэк» и ООО «Альфа-Силтэк»), суммарно работают более 300 ч

💯1🔥1

8 Mar 2026, 04:47 UTC244 views2 reactionsread 9 August 2026
Photo

С праздником, дорогие, милые

2

6 Mar 2026, 05:50 UTC243 views4 reactionsread 9 August 2026
Photo

⚡️#новости #пятница 1С-Рарус Лидирует https://rarus.ru/news/20260304-1c-rarus-lidiruet-v-reytingakh-luchshie-produkty-1c-sovmestno-2025-811673/ По результатам голосования пользователей 8 типовых решений разработки компании «1С‑Рарус» признаны «Лучшими продуктами 1С-Совместно 2025». Шесть решений вошли в топ-10 массовых продуктов, а два — в корпоративный рейтинг. Дмитрий Казачков часто меняет свой вес, но в одном

👍4

4 Mar 2026, 10:03 UTC212 views2 reactionsread 9 August 2026
Photo

⚡️#новости ИИ в эНПеФе https://www.cnews.ru/news/line/2026-03-04_npf_professionalnyj_vnedril Внедрение ИИ-платформы GPTZATOR в НПФ «Профессиональный» стало ответом на вызовы, с которыми сталкиваются многие компании при работе с документами. Заявки в НПФ поступают не только в печатном, но также и в рукописном виде. Ранее, до старта проекта, операторы вручную просматривали сканы и переносили данные в «1С:Бухгалтерия».

😁2

Showing the 12 most recent of 20 posts we hold for @time_1c. 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 — 1,113,876 of 1,480,975entries 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

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.

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

“Время 1С” (@time_1c), 113 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/time_1c.

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.