Channel
@digital_construction_Svrd_region
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,099subscribers
+15 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001878296211 |
|---|---|
| Type | Channel |
| Username | @digital_construction_Svrd_region |
| Created | 28 October 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/digital_construction_Svrd_region |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 09:55 | 1,099 | +2 |
| 12 Sept 2026, 23:00 | 1,097 | +2 |
| 9 Sept 2026, 04:17 | 1,095 | +9 |
| 4 Sept 2026, 02:20 | 1,086 | -1 |
| 1 Sept 2026, 01:58 | 1,087 | -1 |
| 29 Aug 2026, 02:26 | 1,088 | +3 |
| 25 Aug 2026, 20:07 | 1,085 | +1 |
| 16 Aug 2026, 18:48 | 1,084 | +1 |
| 9 Aug 2026, 21:51 | 1,083 | -1 |
| 6 Aug 2026, 14:01 | 1,084 | no change |
| 6 Aug 2026, 13:53 | 1,084 | first reading |
20 posts held, back to 20 June 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 1 page 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
218 reactions across 20 posts, in 19 distinct kinds. The most used accounts for 24.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 54 | 24.8% | |
| 🔥 | 50 | 22.9% | |
| ❤ | 33 | 15.1% | |
| 🆒 | 14 | 6.42% | |
| 😁 | 12 | 5.50% | |
| ⚡ | 11 | 5.05% | |
| ❤🔥 | 9 | 4.13% | |
| 🤣 | 8 | 3.67% | |
| ✍ | 4 | 1.83% | |
| 👌 | 4 | 1.83% | |
| 👎 | 3 | 1.38% | |
| 🤝 | 3 | 1.38% | |
| 🥱 | 3 | 1.38% | |
| 🎉 | 2 | 0.917% | |
| 👏 | 2 | 0.917% | |
| 🙈 | 2 | 0.917% | |
| 🙏 | 2 | 0.917% | |
| 💊 | 1 | 0.459% | |
| 🤔 | 1 | 0.459% |
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 20 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 218 reactions 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 20 June 2026 to 6 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.
🏗 Накануне юбилейного, семидесятого Дня строителя в Правительстве Свердловской области чествовали тех, кто каждый день помогает развивать строительную отрасль региона. Среди награждённых – и цифровые спецназовцы нашего Минстроя. На фото (слева направо): заместитель начальника отдела ГИСОГД Эмилия Хрущелёва, главный специалист ТИМ-отдела Андрей Пруцков и главный специалист отдела ГИСОГД Татьяна Крутакова. 👏 Эмилия Р…
🆒6🎉2
Телеканал Россия 24 опубликовал тематический выпуск «Цифровизация в строительстве» в рамках цикла программ Есть решение. Почти половина жилья в России строится с использованием технологий информационного моделирования. Отрасль активно применяет искусственный интеллект. В реестре отечественного программного обеспечения больше 400 продуктов предназначено для стройкомплекса. Как новые технологии меняют процессы проекти…
👎3🥱3👌2⚡1💊1🤝1
Posted without readable text
🔥5❤2
Мы начали с того, что такое ТИМ, ЦИМ и ИМ в целом. Затем разобрались с дисциплинарными ЦИМ и их связью с разделами проектной документации 💪 Теперь спускаемся еще на уровень ниже и поговорим об элементах модели – о том, благодаря чему обычные линии на чертеже становятся для компьютера осмысленной конструкцией. Человек смотрит на план и сразу понимает: две параллельные линии рядом – это стена. Компьютер так не умеет. …
🔥4👌2🆒2❤1
Posted without readable text
👍6❤3
Автоматизированная проверка ЦИМ – цифровых информационных моделей – становится всё ближе. Анастасия Гусева (УКС Свердловской области) и Ольга Галитарова («Форум-групп») методично продолжают работать над тем, чтобы требования к объектам можно было проверять автоматически, без долгого ручного анализа – вот такой отличный пример B2G-взаимодействия. На сегодня они составили перечень требований к проектной документации …
👍8⚡3❤2
Posted without readable text
🔥9👍7
Месяц назад мы рассказывали, что сотрудники Минстроя Свердловской области и областного УКСа отправились изучать промпт-инжиниринг в строительстве. И вот обучение позади. Финальное тестирование сдали все: 14 из 14. Никто не сошёл с дистанции – уже хороший результат💪 Самое время рассказать, чему научились. За месяц участники прошли 7 модулей – от знакомства с тем, как вообще работают нейросети если честно, то с токен…
👍6⚡3🔥3
🤖 Стандарт как код: почему цифровая трансформация упирается не в XML, а в лингвистику Когда говорят о цифровизации стандартов, чаще всего всплывают форматы - XML, JSON, ReqIF. Мол, переложи текст в теги, и вопрос решён. Но презентация Сергея Трофимова (Российский институт стандартизации) вскрывает куда более глубокую проблему: главный враг машиночитаемости не бумага, а язык. 🔴Вот несколько неочевидных точек, котор…
🔥5
Ну что, пришло время раскрыть карты 👀 Спасибо всем, кто принял участие в опросе – как видите, мнения разделились, и это подтверждает, что рубрику Разъяснения мы запланировали не зря. Начнём с основ. ТИМ, ИМ и ЦИМ – это одно и то же? Звучат похоже, пишутся через запятую, а в документах и на совещаниях их то и дело подменяют друг другом. Проектировщик говорит одно, заказчик слышит другое, а в техническом задании в ит…
👍6🔥3🆒3❤2
Posted without readable text
❤7
Недавно один из наших самых неравнодушных читателей признался, что мысленно делит все публикации в канале на две категории: – всё понятно; – написано по-русски, а что хотел сказать автор – непонятно. Мы посмеялись… а потом поняли, что замечание-то справедливое. Поэтому решили уйти на базу снова обратить своё и ваше внимание на термины, нормативку и типовые ситуации, чтобы коллегам было проще разобраться в мире инфо…
⚡4❤4
Showing the 12 most recent of 20 posts we hold for @digital_construction_Svrd_region. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 6 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Свердловская область: цифровизуем строительство сообща и невзирая на! 📈” (@digital_construction_Svrd_region), 1,099 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/digital_construction_Svrd_region.
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.