Telegram RegisterThe public register of Telegram
Telegram profile photo for МГК

Channel

МГК

@mgk_kas

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

107subscribers

+0 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-1001908014512
TypeChannel
Username@mgk_kas
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live8 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/mgk_kas

Topic

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

Growth

106107106.57 August 2026 — 107 subscribers9 August 2026 — 107 subscribers29 August 2026 — 106 subscribers8 October 2026 — 107 subscribers7 August 20268 October 2026
4 measurements spanning 61 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 106–107 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 06:19107+1
29 Aug 2026, 07:44106-1
9 Aug 2026, 08:17107no change
7 Aug 2026, 22:07107first reading

Engagement

7 posts held, back to 19 December 2025 — 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 7 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

46 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 41.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1941.3%
🔥1328.3%
❤1226.1%
👌24.35%

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

Measured over the 7 most recent posts we hold, published 19 December 2025 to 3 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
8
across the posts below
Posts paid on
3
of 7 we hold a reading for · 43%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mgk_kas. 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 7 most recent posts we hold for this entry, published 19 December 2025 to 3 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

3 Aug 2026, 13:24 UTC39 views6 reactions2 Starsread 9 August 2026
Photo

🏢 Цифровой двойник здания по данным лазерного сканирования Показываем один из наших реализованных проектов — создание фактической 3D-модели здания для проектирования и последующего монтажа фасадов. Главная задача заключалась в том, чтобы передать проектировщикам не условную геометрию из исходной документации, а реальное положение конструкций здания: стен, проёмов, перекрытий, выступов и других элементов фасада. Дл…

👍6

28 May 2026, 13:37 UTC109 viewsread 9 August 2026

Лазерное сканирование и фотограмметрия на объектах культурного наследия — это уже не просто «модные технологии», а необходимый инструмент современной реставрации. По облакам точек и ортофотопланам мы выполняем: — обмерные чертежи — фиксацию архитектурного декора — дефектовочные ведомости — анализ деформаций и повреждений Даже сложные элементы лепнины и исторического декора можно точно зафиксировать в 3D с миллиметр…

15 May 2026, 11:43 UTC≈1,190 views8 reactions1 Starread 9 August 2026
Photo

Анализ точности съемки SHARE S20 в Leica Cyclone Провел анализ облака точек в Leica Cyclone. На скриншоте видно распределение контрольных точек по объекту и значения 3D-отклонений. Съемка выполнялась сканером SHARE S20. Для привязки использовались 6 опорных точек, расположенных непосредственно на объекте: 4 точки — на стенах, 2 точки — на дорожках. Опорные и контрольные точки были сняты тахеометром Leica, что позволи…

👍6🔥2

22 Jan 2026, 22:52 UTC629 views7 reactionsread 9 August 2026
Photo

Краткий доклад Оценка точности облака точек SLAM-сканирования Исходные данные Объект: складское помещение Эталон: тахеометр EFT TS1 Данные: облако точек SLAM Share S20 Метод: сравнение в CloudCompare (отклонения по расстоянию) Результаты Диапазон отклонений: 0.002 – 0.066 м Основная масса точек: 0.02 – 0.04 м Процентное соотношение: ≈ 70–75 % точек — до ±3 см ≈ 90–95 % точек — до ±5 см ≤ 5–10 % — свыше 5…

👍6❤1

31 Dec 2025, 21:50 UTC264 views8 reactionsread 9 August 2026
Photo

🎄 С Новым годом! 🎄 Коллектив компании МГК от всей души поздравляет геодезистов, архитекторов, инженеров, маркшейдеров, специалистов по наземному лазерному сканированию, 3D-моделированию и всех, кто работает на стыке точности, технологий и реального пространства. Этот год был насыщен сложными объектами, нестандартными задачами, миллионами точек в облаках, моделями, чертежами и решениями, где цена ошибки — сантиметры…

❤8

19 Dec 2025, 19:28 UTC261 views10 reactions5 Starsread 9 August 2026
Photo

🏛 3D-сканирование и моделирование усадьбы 📡 Наша команда выполнила комплексное 3D-сканирование объекта 🧱 С последующим созданием точной цифровой модели здания 📐 Модель подготовлена для дальнейшего проектирования АР 🎨 А также для разработки дизайн-проектов интерьеров ⏱️ Работы выполнены в сжатые сроки, без потери точности 👥 Задача решалась командно — полевые и камеральные этапы 🧩 Проработаны сложная геометрия, купол…

🔥5❤3👌2

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

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.

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

“МГК” (@mgk_kas), 107 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/mgk_kas.

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.