Telegram RegisterThe public register of Telegram

Channel

Легко БИМ(ТИМ)/LEGkO BIM

@legkobim

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

2,049subscribers

+11 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001502495356
TypeChannel
Username@legkobim
CreatedBetween 1 February 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/legkobim

Growth

2,0382,0492,043.57 August 2026 — 2,038 subscribers7 August 2026 — 2,038 subscribers10 August 2026 — 2,044 subscribers13 August 2026 — 2,049 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net +11. 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 2,036–2,051 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 06:542,049+5
10 Aug 2026, 07:142,044+6
7 Aug 2026, 13:112,038no change
7 Aug 2026, 11:022,038first reading

Engagement

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

ERR · 30 days
29.2%
avg views ÷ 2,049 subscribers
Avg views / post
598
5 posts measured
Reaction rate
1.97%
reactions ÷ views · ER floor
Posts in window
5
of 17 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 held17 (1 June 20267 August 2026)
Views total2,990
Reactions total59
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:06 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.

Reaction mix

190 reactions across 17 posts, in 3 distinct kinds. The most used accounts for 67.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 518822992559265876912967.9%
custom 51929943456990120344222.1%
1910.0%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

Measured over the 17 most recent posts we hold, published 1 June 2026 to 7 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.

Recent posts

7 Aug 2026, 14:00 UTC155 views8 reactionsread 7 August 2026
Photo

☕️Ждем вас завтра на завтраке на наших площадках: ✅ в Москве в МГСУ, Ярославское шоссе, д. 26 ✅ В Питере в СПбГАСУ, Набережная реки Фонтанки, 123-125 (Вход с Вознесенского проспекта) Схемы, как добраться к площадкам, приложили к посту⬆️ 11:00 - сбор гостей 11:30 - начало онлайн трансляции и первое выступление 🌟 Возьмите, пожалуйста, с собой паспорт! 🌟 #тимbimзавтрак

custom 51882299255926587698

7 Aug 2026, 07:01 UTC324 views12 reactionsread 7 August 2026

Всем привет! Уже завтра у нас состоится завтрак на тему управления проектами. Как мне кажется, это очень важная тема, которую стоит понимать каждому ТИМ/BIM-специалисту. Как правило, в нашей сфере больше технических людей. Навык грамотного управления проектом делает из вас ценного специалиста, потому что вы можете выдавать проекты в срок и, как сказал мой руководитель, без драмы😁 На практике часто встречаюсь со сп

12

3 Aug 2026, 10:27 UTC927 views10 reactionsread 7 August 2026
Photo

🔥 Анонс ТИМ/BIM завтрака 🔥 Тема месяца - ТИМ/BIM менеджмент и управление проектами ☕️📚 ✅ Дата 8 августа 11.00 ⚪️ Москва: Москва, МГСУ, Ярославское шоссе, д. 26 ⚪️ Санкт-Петербург: СПбГАСУ, Набережная реки Фонтанки, 123-125 (Вход с Вознесенского проспекта) ТИМ/BIM завтрак - это мероприятие, где собираются заинтересованные ТИМ/BIM специалисты. За чашечкой кофе можно послушать короткие лекции на выбранные темы и п

custom 518822992559265876910

29 Jul 2026, 07:39 UTC802 views17 reactionsread 7 August 2026

Всем привет! Мне пришел свеженький AEC Magazine, а это значит время для поста #СводкаПоГринвичу. Я уже рассказывала, что букву I в BIM начинают заменять на «Intelligence» интеллектуальный вместо «Information». Этот термин встречается все чаще. Автодеск вводит словосочетание интеллектуальный проект / «project intelligence». Это значит, что все решения, процессы, ошибки, знания аккумулируются в базу данных по конкре

custom 518822992559265876917

27 Jul 2026, 07:00 UTC782 views12 reactionsread 7 August 2026

Всем привет! Дорогие, мы переносим завтрак на 8 августа. Тема: "ТИМ/BIM менеджмент и управление проектами". Ищем спикеров, пишите в личку пожалуйста. 💚 legkobim.com #тимbimзавтрак

custom 519299434569901203412

13 Jul 2026, 07:01 UTC≈1,200 views12 reactionsread 7 August 2026
Photo

📚Материалы завтрака в июле Внедрение ТИМ/BIM в компании, как сделать так, чтобы ТИМ/BIM приносил прибыль компании Смотрим как это было в записи: ВКонтакте YouTube Презентации спикеров и фото: Смотреть Теперь все новости по завтракам и публикация материалов будут также в канале вк, ловите ссылки: ☕️ Группа ВК ☕️ Канал ВК Следующий завтрак пройдет 1 августа на тему "ТИМ/BIM менеджмент и управление проектами". Ищем

custom 518822992559265876912

4 Jul 2026, 08:17 UTC≈1,100 views3 reactionsread 7 August 2026

Всем привет! Мы скоро начинаем завтрак☕️ ➡️ ссылка на трансляцию #тимbimзавтрак

custom 51882299255926587693

3 Jul 2026, 07:02 UTC≈1,020 views5 reactionsread 7 August 2026
Photo

Доброе утро! ☕️ Ждем вас завтра на завтраке на наших площадках: ✅ в Москве в КРОК, Волочаевская улица, 5к1, 2 этаж ✅ В Питере в СПбГАСУ, Набережная реки Фонтанки, 123-125 (Вход с Вознесенского проспекта) Схемы, как добраться к площадкам, приложили к посту⬆️ 11:00 - сбор гостей 11:30 - начало онлайн трансляции и первое выступление 🌟 Возьмите, пожалуйста, с собой паспорт! 🌟 #тимbimзавтрак

custom 51929943456990120345

29 Jun 2026, 09:56 UTC≈1,250 views15 reactionsread 7 August 2026
Photo

🔥 Анонс ТИМ/BIM завтрака 🔥 Тема месяца - Внедрение ТИМ/BIM в компании, как сделать так, чтобы ТИМ/BIM приносил прибыль компании ☕️📚 ТИМ/BIM завтрак - это мероприятие, где собираются заинтересованные ТИМ/BIM специалисты. За чашечкой кофе можно послушать короткие лекции на выбранные темы и пообщаться с коллегами. Главная идея ТИМ/BIM завтраков - это офлайн общение специалистов, нетворкинг, обмен опытом и лучшими пра

custom 518822992559265876915

26 Jun 2026, 08:32 UTC949 views12 reactionsread 7 August 2026

Всем привет! Ищем спикеров на завтрак 4 июля на тему "Внедрение ТИМ/BIM в компании, как сделать так, чтобы ТИМ/BIM приносил прибыль компании". Пишите в личку пожалуйста. 💚 legkobim.com #тимbimзавтрак

custom 518822992559265876912

24 Jun 2026, 07:02 UTC≈1,020 views17 reactionsread 7 August 2026

Всем привет! В начале года я рассказывала, как ищу работу и хожу на собеседования #bykovainlondon. Весной приостановила эту активность, потому что не могла определиться с тем, чего я хочу, нужно ли менять работу, что с визой делать и всякими другими сомнениями. Сейчас я более или менее определилась. Моя виза заканчивается этой осенью, и это подходящий момент сменить работу, чтобы не заморачиваться с визой несколько

custom 519299434569901203417

22 Jun 2026, 07:00 UTC974 views20 reactionsread 7 August 2026
Photo

📚Материалы завтрака в июне Искусственный интеллект в ТИМ/BIM (AI / LLM / ML) Смотрим как это было в записи: ВКонтакте YouTube Презентации спикеров и фото: Смотреть Теперь все новости по завтракам и публикация материалов будут также в канале вк, ловите ссылки: ☕️ Группа ВК ☕️ Канал ВК Следующий завтрак пройдет 4 июля на тему "Внедрение ТИМ/BIM в компании, как сделать так, чтобы ТИМ/BIM приносил прибыль компании".

custom 518822992559265876920

Showing the 12 most recent of 17 posts we hold for @legkobim. 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 — 135,455 of 1,176,251entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 3 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Легко БИМ(ТИМ)/LEGkO BIM” (@legkobim), 2,049 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/legkobim.

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.