Telegram RegisterThe public register of Telegram
Telegram profile photo for Сергей Коврижных | BIM-консультант

Channel

Сергей Коврижных | BIM-консультант

@BIMKovr

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

489subscribers

-1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001681699474
TypeChannel
Username@BIMKovr
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/BIMKovr

Growth

489490489.57 August 2026 — 490 subscribers8 August 2026 — 490 subscribers15 August 2026 — 489 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, net -1. 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 489–490 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 14:18489-1
8 Aug 2026, 04:21490no change
7 Aug 2026, 12:56490first reading

Engagement

18 posts held, back to 26 September 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
17.8%
avg views ÷ 489 subscribers
Avg views / post
87.0
1 post measured
Reaction rate
14.9%
reactions ÷ views · ER floor
Posts in window
1
of 18 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 6 August 2026
Posts held18 (26 September 20256 August 2026)
Views total87
Reactions total13
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 04:21 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
2m 00s
Average length
30s

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

276 reactions across 18 posts, in 12 distinct kinds. The most used accounts for 32.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥9032.6%
👍8631.2%
5921.4%
👏134.71%
🙏134.71%
🤝51.81%
👎31.09%
💩20.725%
🤩20.725%
👾10.362%
🗿10.362%
🤔10.362%

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

Measured over the 18 most recent posts we hold, published 26 September 2025 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.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
2
of 18 we hold a reading for · 11%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @BIMKovr. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 18 most recent posts we hold for this entry, published 26 September 2025 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

6 Aug 2026, 07:51 UTC87 views13 reactionsread 8 August 2026

САМЫЙ СЛОЖНЫЙ ВЫЗОВ БИМЕРУ. ОБЗОР, МОЙ ОПЫТ + КЛЮЧИ К ПРЕОДОЛЕНИЮ Есть в нашей работе узкие места. А есть те, которые буквально сводят на нет все преимущества BIM! Спросите опытного бимера о самых «экстремально сложных вызовах работы», и большинство назовёт: 🟣загрузка файлов от смежников в Revit (*dwg, ifc, arhicad, tekla, sketchup, облака точек и т.д.) 🟣настройка видов, спецификаций, марок и параметров семейств 🟣р

👍7🔥42

29 Jun 2026, 10:36 UTC253 views21 reactionsread 8 August 2026
Video

Устал молчать... Почти три месяца я не делал посты. Наверное вы подумали, что я забыл про канал или ушел в найм) Но это не так! Просто мой старший сын покоряет шахматный мир и меня закружили его спортивные сборы к соревнованиям. Столько переживаний, новых людей и живых эмоций давно не случалось в моей жизни. Местами было драмматично, но в итоге Мирошка вошел в 9 лучших шахматистов региона! Это большая радость. Па

11👏7👍3

28 Mar 2026, 08:16 UTC426 views9 reactionsread 8 August 2026

Подкасты будут доступны! Сегодня собрал все эпизоды «Правильного BIM» в одном аудио и загрузил здесь! Вышло очень интересно и удобно. Пока ездил по делам слушал подкаст в машине. За эти 60 минут испытал эмоции разные, вспомнил как это было. 🟣Как структурировал весь свой опыт и знания 🟣Как придумывал идеи и темы 🟣Как дико волновался выкладывать готовые подкасты в канал! А потом с интересом ждал вашу обратную связь

👏3👍2🔥2💩1🤝1

26 Mar 2026, 12:01 UTC392 views11 reactionsread 8 August 2026

Аудит «под прикрытием» Опять выпал из канала из-за высокой загрузки по двум новым проектам. Кстати, в обоих случаях все началось с аудита по тем самым метрикам, о которых я писал здесь. И тут у многих возникал вопрос: Как я использовал их и что было дальше, после анализа метрик? Основной посыл - вы обращаете внимание на те вещи, которые раньше казались несущественными и ускользали из фокуса. Просто не было даже ор

4👍3🔥3🤔1

24 Mar 2026, 12:03 UTC369 views17 reactionsread 8 August 2026

Суровая цифровая реальность! В связи с блокировкой Телеграма я создал дубль в MAX. Завтра здесь опубликую приглашение, чтобы нам всем не потеряться! PS: Друзья, мы прошли отметку 500 подписчиков! Я очень счастлив что канал стал одним из самых популярных в своей тематике. Давайте повторим это в MAX!

5👎3🤝3👍2🔥2💩1🗿1

17 Feb 2026, 14:14 UTC504 views15 reactionsread 8 August 2026
Forwarded from @nanosoft_newsVideo

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

👍74🔥4

4 Feb 2026, 12:07 UTC560 views16 reactionsread 8 August 2026

Любимая гремучая смесь↘️ Комбинация из метрик модели, скиллов BIM-отдела и вопросов к руководству — идеально покажет положение дел и ускользающие от вас закономерности. Особенно круто она работает когда ты расширяешь аудит до нескольких проектов [самых успешных или наоборот самых провальных] ✅Здоровье моделей Размер файла модели, время синхронизации, время обновления связанных файлов, ошибки, количество элементов и

🔥6🙏6👍21🤝1

4 Feb 2026, 12:07 UTC396 views12 reactionsread 8 August 2026
Photo

Продолжаю заполнять комментарии в таблице с метриками для аудита проектных бюро...

👍5🔥4👏3

28 Jan 2026, 08:22 UTC507 views35 reactions1 Starread 8 August 2026

И финально — я больше не хочу работать со слов клиентов. Вот так Аудит через метрики сейчас делает для меня то, что консультации-диагностики НИКОГДА бы не сделали! Хотя я умею их проводить. +5 часов свободного времени после аудита только за первую неделю. И сотрудники уже знают свои процессы и «зевки» намного лучше! Чего не успеешь рассказать на любой консультации. Это страшно большие цифры, честно. От оптимизации

🔥293👍3

21 Jan 2026, 03:40 UTC≈1,700 views22 reactionsread 8 August 2026

Чит-коды 2026. Продолжаем Расскажу историю, которая окончательно устаканилась в моей голове только в этом году. В октябре взял на сопровождение проект завода. С нуля собрал Revit-сервер, шаблоны и логику работы. Все объяснил команде и они начали моделить. Через пару недель открываю проект - картина сказочная! Файл открылся за полминуты. Синхрон меньше 5 секунд. И это при весе файла 370 мб! Я выдохнул и радостно з

👍9🔥8🙏31👾1

18 Jan 2026, 15:45 UTC626 views21 reactionsread 8 August 2026

Чит-коды 2026 Этот пост пишу на основе моих личных наблюдений и публикую исключительно как информационно-развлекательный контент без цели кого-либо оскорбить. Начну без прелюдий. САМОЕ главное осознание этого года крутится вокруг фразы: "Тебя чертовски злит, когда нельзя просчитать результат!" И главный чит-код, который я здесь вывел: «НЕ СТЕСНЯЙСЯ!». Не стесняйся измерять! Свою работу. Свои навыки. Этот совет по

🔥9👍75

14 Jan 2026, 05:36 UTC641 views13 reactions1 Starread 8 August 2026
Video

Поставил цель в 2026 — вырасти до 1K Да, мои подписчики, именно Вы даете мне уверенность и энергию для движения вперед🚀 Представьте если бы мы все собрались вместе, то нам понадобился бы зал в Экспоцентре или просторный ресторан! Заглянул в статистику канала и понял, что интерес ко мне как автору растет. Вы активно читаете и слушаете меня. В среднем на постах ~700-900 просмотров, а бывают и 3K охваты. Это не прост

👍6🔥5🤩2

Showing the 12 most recent of 18 posts we hold for @BIMKovr. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 1,404,945 of 1,481,502entries 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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“Сергей Коврижных | BIM-консультант” (@BIMKovr), 489 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/BIMKovr.

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.