Telegram RegisterThe public register of Telegram

Channel

Stroy.OS | Цифровизация стройки

@stroyOS

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

3,080subscribers

+14 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002669249947
TypeChannel
Username@stroyOS
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/stroyOS

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 86% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. They sit inside a group of 3 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@stroyOS/700 · this entry3 Aug 2026, 05:10 UTC@bukvamiocifre/97453 Aug 2026, 09:04 UTC1.003.9 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@bukvamiocifre5 (5/5 hand-verifiable sample passed)1.004.0 hours@bukvamiocifre (32)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 24 comparable posts for this entry, running 23 July 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 3, the earliest publisher we hold is @NextGenInfrastructure. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

3,0513,0803,065.56 August 2026 — 3,066 subscribers6 August 2026 — 3,051 subscribers10 August 2026 — 3,080 subscribers6 August 202610 August 2026
3 measurements spanning 4 days, net +14. 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 3,047–3,084 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 06:043,080+29
6 Aug 2026, 19:543,051-15
6 Aug 2026, 06:473,066first reading

Engagement

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

ERR · 30 days
16.6%
avg views ÷ 3,080 subscribers
Avg views / post
512
24 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
24
of 24 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 7 August 2026
Posts held24 (23 July 20267 August 2026)
Views total12,288
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:00 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

Video runtime
40s
Average length
40s

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.

Recent posts

7 Aug 2026, 09:12 UTC133 viewsread 8 August 2026
Forwarded from @bukvamiocifrePhoto

🔖 Новый уровень контроля: в Москве открылся Ситуационный центр Градкомплекса столицы В преддверии Дня строителя на 2-й Брестской улице начал работу Ситутационный центр Градкомплекса Москвы. Сергей Собянин лично проверил как устроен современейший центр. 🔴Что здесь происходит: - Круглосуточный мониторинг 1,7 тысяч объектов - Оперативное реагирование на нештатные ситуации - Координация городских служб 🔴Ключевые особе

7 Aug 2026, 05:05 UTC166 viewsread 8 August 2026

📌 В «СберСити» запускают пилотный проект с робособаками для патрулирования территории В смарт‑районе «СберСити» стартует тестирование патрульных робособак, об этом сообщил генеральный директор компании Андрей Лихачёв. Первым участком для испытаний станет речной парк. Продолжительность пилотного этапа составит несколько месяцев. По итогам тестирования планируется масштабировать решение на весь район. 🔴Робособака фу

6 Aug 2026, 11:14 UTC191 viewsread 8 August 2026
Forwarded from @bukvamiocifre

🔖Москва переходит на собственные стандарты цифрового строительства Федеральный закон № 299-ФЗ передал столице полномочия по регулированию подготовки проектной документации в форме информационной модели в рамках программ реновации и КРТ. 💡Теперь Москва самостоятельно определяет: — требования к составу информационной модели; — порядок проведения госэкспертизы проектной документации в цифровой форме; — особенности выд

6 Aug 2026, 08:11 UTC165 viewsread 8 August 2026
Forwarded from @CifroStroyEvent

🏗 Уже сегодня очередной вебинар от ДГП Москвы по АГР 📆 сегодня, 06 августа в 15:00 состоится 9-й консультационный онлайн-семинар по применению IFC на этапе АГР. 🔴Подключение к видеоконференции: 🔴 Вход по [ССЫЛКЕ] Получайте своевременные анонсы, программы мероприятий. Оставайтесь в курсе всех событий цифровой трансформации градостроительства! 🏗@CifroStroyEvent 📲MАХимально на связи🔴 #CSE_вебинар

6 Aug 2026, 05:08 UTC186 viewsread 8 August 2026

📌 Библиотека знаний для цифрового будущего строительства: «ДОМ.РФ Технологии» открывают доступ к экспертизе «ДОМ.РФ Технологии» запустил единую базу исследований, аналитики и методических материалов для всех участников жилищной сферы. Это открытый ресурс, где собрана ключевая информация для эффективного внедрения современных технологий . База знаний создана на основе наработок Центра компетенций Эксперт.дом.рф. В н

5 Aug 2026, 05:11 UTC≈1,270 viewsread 8 August 2026
File

📌 От котлована к сделке: как «Брусника» перевела 13 ЖК в единую цифровую среду Кейс: внедрение интерактивных цифровых двойников в экосистеме GRAFF.estate Запрос федерального девелопера - масштабирование системы цифровых продаж на 13 жилых комплексов в разных регионах с единым стандартом презентации. Цель — нивелировать разрыв между планировкой и восприятием покупателя, обеспечив эффективность сделок на этапе котлов

4 Aug 2026, 05:15 UTC192 viewsread 8 August 2026

📌 Как в ПИК трансформировали подход к интерфейсам BIM‑инструментов: опыт команды ПИК Digital На Хабре вышла статья Дмитрия Смагина, руководителя продукта информационного моделирования в ПИК Digital, о том, как в компании пересмотрели подход к проектированию интерфейсов для BIM‑инструментов. История не про «красивые картинки», а про то, как удобство работы напрямую влияет на продуктивность проектировщиков. 🔴Изначал

3 Aug 2026, 09:04 UTC330 viewsread 8 August 2026
Forwarded from @bukvamiocifrePhoto

🔖Эксперты раскрывают секреты управления жизненным циклом здания: вебинар 4 августа ⏰4 августа в 11:00 (мск) состоится вебинар, где эксперты разберут самые острые вопросы отрасли: 🔵 почему затраты на эксплуатацию нередко превышают стоимость строительства; 🔵 какие решения критически важно закладывать ещё на этапе проектирования; 🔵 как передавать объект между участниками процесса без потери данных; 🔵 что представляет с

3 Aug 2026, 05:10 UTC≈1,130 viewsread 8 August 2026
File

📌 Цифровой двойник как стандарт девелопмента: как «КОРТРОС» автоматизировал согласования и продажи в одном продукте Цифровизация в девелопменте — это не про красивую картинку. Это про скорость решений, прозрачность данных и исключение человеческого фактора. 🔴«КОРТРОС» запустил в Калининграде проект «ОКТАРИН» (114 000 кв. м, 260 номеров в гостиницах, два МФК) и с первого дня внедрил цифровой двойник как рабочий B2B-

31 Jul 2026, 09:08 UTC220 viewsread 8 August 2026
Forwarded from @NextGenInfrastructureFile

🤖 Дроны в России: 10,7 млрд рублей уже заработано Это не прогноз и не потенциал. Это фактические деньги, полученные от применения беспилотников в 2025 году. Рейтинг дронификации‑2026 впервые оценивал регионы не по обещаниям, а по реальным полётам и контрактам. 🔴Где дроны приносят прибыль прямо сейчас Почти 1,4 млрд рублей — в строительстве и землеустройстве. Самые денежные сценарии: · Сбор данных для карт и планов

31 Jul 2026, 05:27 UTC189 viewsread 8 August 2026
File

📌 Цифровой двойник как точка продаж: как LEGENDA превратила макет в управляемый data-интерфейс Проект «Северный Порт» номинирован на WOW Awards в категории «Digital - Цифровые технологии». Но за этой заявкой не демонстрация гаджетов, а интеграция цифрового моделирования в бизнес-процесс продаж. 🔴В офисе на Воздвиженке классический архитектурный макет работает как физический интерфейс к цифровому двойнику ЖК. Свето

30 Jul 2026, 11:42 UTC220 viewsread 8 August 2026
Forwarded from @bukvamiocifre

🔖Автоматизация в строительстве: где ИИ реально работает, а где — просто хайп? Канал @god_kod_agency поговорил с Игорем Рогачёвым о том, как автоматизация и ИИ меняют проектирование и стройку. Делимся главным из этого разговора. 💡О чём говорили: 🔺 Почему автоматизация буксует не из-за технологий, а из-за вопросов воли, ресурсов и процессов 🔺 Типовые неэффективности: та самая «Людочка с экселькой» и ручное календа

Showing the 12 most recent of 24 posts we hold for @stroyOS. 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 — 428,943 of 1,151,006entries 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

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 8 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.

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.

“Stroy.OS | Цифровизация стройки” (@stroyOS), 3,080 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/stroyOS.

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.