Telegram RegisterThe public register of Telegram

Channel

NSR Specification - блог

@nsrspec

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

547subscribers

+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-1002124531614
TypeChannel
Username@nsrspec
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/nsrspec

Growth

5479 Aug 2026, 19:46 — 547 subscribers9 Aug 2026, 20:52 — 547 subscribers9 Aug 2026, 19:469 Aug 2026, 20:52
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 546–548 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 20:52547no change
9 Aug 2026, 19:46547first reading

Engagement

14 posts held, back to 11 December 2025the 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.

ERR · 30 days
34.8%
avg views ÷ 547 subscribers
Avg views / post
191
2 posts measured
Reaction rate
7.87%
reactions ÷ views · ER floor
Posts in window
2
of 14 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 29 July 2026
Posts held14 (11 December 202529 July 2026)
Views total381
Reactions total30
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 19:46 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
6m 29s
Average length
1m 05s

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

301 reactions across 14 posts, in 10 distinct kinds. The most used accounts for 47.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥14347.5%
8126.9%
👍3913.0%
🤝92.99%
🏆82.66%
👏82.66%
😁51.66%
🥰51.66%
😱20.664%
❤‍🔥10.332%

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

Measured over the 14 most recent posts we hold, published 11 December 2025 to 29 July 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

29 Jul 2026, 20:49 UTC203 views12 reactionsread 9 August 2026

Впервые вижу прям идеальное описание нашего функционала)

6🔥6

29 Jul 2026, 20:48 UTC178 views18 reactionsread 9 August 2026
Forwarded from @revit_bim_newsFile

Смотрим на NSR Specification — ИИ для работы с нормативами в проектировании Нанософт строит систему, которая уменьшает количество ошибок на этапе проектирования, связанных со сложностью поиска и анализа стандартов. Решение состоит из двух модулей: семантического поиска и семантического анализа. 🟩 Семантический поиск работает на базе продвинутой RAG-системы Пользователь задаёт вопрос на естественном языке — например

🔥114🥰3

29 May 2026, 14:03 UTC379 views14 reactionsread 9 August 2026
Forwarded from @nanosoft_news

19 мая на ЦИПР-2026 «Нанософт» представила ИИ-платформу для автоматизации проектирования NSR Specification О ее применении в проекте «Цифровая экспертиза», реализуемом институтом «Газпром проектирование», шла речь на панельной сессии конференции. Платформа NSR Specification помогает инженерам решать их задачи с помощью нейронных сетей и обеспечивает автоматизацию работы с нормативными требованиями на всех этапах: п

👍64🔥4

29 May 2026, 14:03 UTC312 views11 reactionsread 9 August 2026

Мы не пропали! Мы заработались! А еще vpn работает через раз...

🔥82🥰1

23 Mar 2026, 10:15 UTC670 views23 reactionsread 9 August 2026
Video

В тестовом интерфейсе NSR Модуль семантического поиска реализован экспериментальный функционал сравнения документов 📚 Мы уже демонстрируем его на обзорных презентациях для заказчиков, однако ранее не представили его здесь 🔗 👍 Исправляем это и показываем, как работает данный инструмент на практике. В ролике продемонстрированы основные этапы работы: ➡️ загрузка проектной документации ➡️ разбиение документов на фрагме

🔥114👍3👏2🤝2🥰1

27 Feb 2026, 12:07 UTC563 views27 reactionsread 9 August 2026
Video

Хотим похвастаться видео, где показана работа конвертера правил проверки ЦИМ для nanoCAD 🚀 Да, он не добавлен еще в интерфейс нашей системы разметки и существует как отдельный сервис, работающий через API. Но, он работает! 💡 И скоро обретет оболочку. И научится обрабатывать сложные требования. 🎈 Маленький шаг для разработчика - большой шаг в светлое будущее!

🔥14👍7👏6

12 Feb 2026, 08:34 UTC650 views27 reactionsread 9 August 2026
Video

Вдохновленные прожаркой мы решили применить наши технологии для автоматизации работы с текстом BIM-стандарта 🔥 ⭐️️️️ Команда NSR Specification интегрировала BIM-стандарт «Нанософт» в векторную базу NSR Модуля семантического поиска. Результат — виртуальный помощник, который отвечает на вопросы по BIM-стандарту и быстро выдаёт конкретные ответы 👌 Больше не нужно перечитывать документ и искать нужный пункт вручную.

🔥158🏆2😱2

12 Feb 2026, 08:33 UTC498 views12 reactionsread 9 August 2026
Forwarded from @nanosoft_newsVideo

🔥 Прожарка BIM-стандарта «Нанософт» состоялась В ходе открытого профессионального обсуждения проведен анализ практической применимости BIM-стандарта «Нанософт». Дискуссия позволила перейти от теоретического содержания документа к оценке его эффективности в реальных проектных задачах, выявить области для доработки и определить направления дальнейшего развития. Подробнее о Прожарке — на сайте nanocad.ru.

👍53🔥3🏆1

22 Jan 2026, 12:02 UTC504 views29 reactionsread 9 August 2026
Forwarded from @bukvamiocifre

🔖Уральские стройки под присмотром нейросети: в Свердловской области запустили ИИ‑контроль документации В Свердловской области стартовал необычный пилотный проект: контроль строительства социальных объектов теперь частично лежит на нейросети. Управление капитального строительства (УКС) региона внедряет отечественное ИИ‑решение NSR Specification — для проверки проектно‑сметной документации и информационных моделей объ

🔥15👍75🤝2

12 Jan 2026, 11:06 UTC762 views26 reactionsread 9 August 2026
Video

⚡️Эксклюзивно⚡️ Пока только для подписчиков нашего блога! 🔵🔵🔵 Тестовый доступ к ИИ-чату для анализа нормативных требований (NSR Модуль семантического поиска) Как получить доступ: 💕зарегистрируйтесь в личном кабинете на https://lk.nanocad.ru/ 💕получите тестовую лицензию NSR Модуль семантического поиска на 30 дней 💕активируйте лицензию 💕????? 💕можете пользоваться!

🔥129😁3🏆2

30 Dec 2025, 13:05 UTC651 views30 reactionsread 9 August 2026
Photo

Photo, posted without a caption

14🔥8👍6❤‍🔥1🏆1

26 Dec 2025, 10:29 UTC≈1,470 views30 reactionsread 9 August 2026
Video

Правила проверки ЦИМ теперь доступны в NSR Модуль требований! ❄️ ✅ Мы не только добавили в базу правила проверки ЦИМ созданные на основе семантического анализа требований, но и собрали их в отдельную категорию "Правила" Запросите лицензию на модуль требований в личном кабинете на https://lk.nanocad.ru/ и тестируйте прямо сейчас! 🎁

🔥158👍5🏆2

Showing the 12 most recent of 14 posts we hold for @nsrspec. 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,154,778 of 1,160,990entries 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 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.

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.

“NSR Specification - блог” (@nsrspec), 547 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/nsrspec.

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.