Telegram RegisterThe public register of Telegram
Telegram profile photo for SGSCAN | Лазерное сканирование, BIM, геодезия

Channel

SGSCAN | Лазерное сканирование, BIM, геодезия

@sgscans

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

75subscribers

+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-1002694985770
TypeChannel
Username@sgscans
CreatedBetween 1 March 2025 and 7 June 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live13 October 2026
Measurements held3
Confirmed unchanged3 times, most recently 13 October 2026
On Telegramt.me/sgscans

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 28 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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

747574.57 August 2026 — 74 subscribers9 August 2026 — 74 subscribers19 September 2026 — 75 subscribers7 August 202619 September 2026
3 measurements spanning 43 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 74–75 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 15:4075+1
9 Aug 2026, 22:0174no change
7 Aug 2026, 16:0274first reading

Engagement

5 posts held, back to 7 June 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 5 posts for this entry, the most recent from 14 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
36s
Average length
36s

Measured directly from 1 video 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

45 reactions across 5 posts, in 7 distinct kinds. The most used accounts for 48.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2248.9%
❤1431.1%
👍48.89%
👌24.44%
⚡12.22%
🆒12.22%
👏12.22%

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

Measured over the 5 most recent posts we hold, published 7 June 2025 to 14 June 2025, 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

14 Jun 2025, 07:43 UTC448 views10 reactionsread 9 August 2026
Photo

🌉Обследование мостов и инженерных сооружений Мосты, путепроводы, эстакады — объекты, которые должны соответствовать всем нормам безопасности. Для продления срока службы или подготовки к капитальному ремонту важно иметь точную информацию о состоянии конструкций. Что получает заказчик после 3D-сканирования: 1️⃣ Цифровой паспорт сооружения 2️⃣ Основание для расчётов несущей способности 3️⃣ Подготовку к BIM-моделиро…

❤4👍4🔥2

12 Jun 2025, 08:08 UTC365 views10 reactionsread 9 August 2026
Photo

В прошлом посте мы показывали вам процесс лазерного сканирования квартиры в ЖК «Фестиваль Парк», г.Москва. ⬇️ Сегодня — смотрим результат работы. 🟢 Заказчик получил: — Облако точек — Обмерные чертежи всех поверхностей — BIM-модель квартиры в Revit для последующей работы дизайнера ↪️Связаться с нами 🫥🫥🫥🫥🫥🫥🫥🫥 🌐 Telegram 🌐 WhatsApp #SGScan #3Dсканирование #лазерноесканирование

❤5🔥4🆒1

11 Jun 2025, 08:21 UTC304 views8 reactionsread 9 August 2026
Video

🏙 Сканирование квартиры в ЖК «Фестиваль Парк», г.Москва Тип объекта: Жилая квартира Цель работ: Подготовка исходных данных для дизайн-проекта Срок выполнения: 3 рабочих дня (включая выезд) Точность: до 2 мм Оборудование: Trimble X7 ⭕️ Что делали: — Провели высокоточное лазерное сканирование квартиры — Построили точную 3D-модель квартиры в Autodesk Revit — На основе модели подготовили обмерные чертежи Работа вел…

🔥6❤2

9 Jun 2025, 12:53 UTC235 views8 reactionsread 9 August 2026
Photo

Блиц: 5 популярных вопросов о лазерном сканировании 1️⃣ Чем отличается наземное лазерное сканирование от воздушного? Наземное даёт высокую детализацию (до 1 мм), используется для фасадов и интерьеров. Воздушное — для больших площадей и труднодоступных участков. 2️⃣ Можно ли сканировать зимой? Можно сканировать круглый год, но при сканировании рельефа зимой нужно учитывать толщину снежного покрова, при сканировании …

🔥4⚡1❤1👌1👏1

7 Jun 2025, 06:24 UTC227 views9 reactionsread 9 August 2026
Photo

На электростанциях, подстанциях и ЛЭП необходимо регулярно проводить обследование конструкций, для чего лазерное сканирование становится всё более востребованным. ⏺Сканирование крупной подстанции (35/110 кВ) занимает до 8 часов, включая фотофиксацию и GPS-привязку. Все элементы фиксируются с точностью до ±3 мм. Результат: ✔️ Объективное техническое состояние ✔️ Подготовка к модернизации ✔️ Контроль геометрии и с…

🔥6❤2👌1

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

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

“SGSCAN | Лазерное сканирование, BIM, геодезия” (@sgscans), 75 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/sgscans.

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.