4 measurements spanning 38 days. 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 45–46 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
15 Sept 2026, 08:17
45
-1
7 Sept 2026, 19:41
46
+1
10 Aug 2026, 15:16
45
no change
7 Aug 2026, 23:05
45
first reading
Engagement
6 posts held, back to 20 January 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 6 posts for this entry, the most recent from 30 March 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
18 reactions across 4 posts, in 7 distinct kinds. The most used accounts for 38.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
7
38.9%
❤
3
16.7%
👍
3
16.7%
👏
2
11.1%
😍
1
5.56%
🤪
1
5.56%
🥰
1
5.56%
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 4 of the 6 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 20 January 2026 to 30 March 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.
В рубрике «Вопрос-ответ» на примере методики № 421/пр совместно с Главгосэкспертизой России рассказываем о том, как проходят пусконаладочные работы в школе.
▶️Особенности определения сметных затрат на пусконаладочные работы установлены главой VII Методики определения сметной стоимости строительства, реконструкции, капитального ремонта, сноса объектов капитального строительства, работ по сохранению объектов культурно…
Новые требования СПДС к проектам
❗️Приняты новые требования СПДС к проектной и рабочей документации.
Дата введения с 01.04.2026.
- ГОСТ Р 21.101-2026 "Система проектной документации для строительства. Основные требования к проектной и рабочей документации".
Сейчас действует ГОСТ Р 21.101-2020.
* Ожидаем официальную публикацию документа.
Продолжаем рассказывать о самом амбициозном проекте СССР — Дворце Советов.
Первая часть здесь.
И… будет ещё третья часть про стройку и почему не завершили проект.
Этот архитектурный проект называли самым грандиозным и утопическим в СССР.
Дворец Советов.
Он мог стать первым небоскребом Советского союза и самым высоким зданием в мире в свое время. Но проект так и не был осуществлен.
Сегодня расскажем, как возникла идея Дворца и как рождался его внешний облик, ну а завтра подробнее расскажем о конструктиве.
👍3🔥1😍1
Signed Мари 💃🏼
Showing the 6 most recent of 6 posts we hold for @proektirovaniezdaniy. 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
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.
Mentions
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.
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.
“Гражданское проектирование” (@proektirovaniezdaniy), 45 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/proektirovaniezdaniy.
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.
